xc-mcp (ericvoltolin/xc-mcp) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

C
Caution
60/100

xc-mcp

XC-MCP delivers an intelligent MCP server for Xcode tooling with progressive disclosure and caching to prevent token overflow. It speeds workflows and boosts reliability in development 🐙

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ericvoltolin

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes18 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

xcodebuild-version

⚡ **Prefer this over 'xcodebuild -version'** - Gets Xcode version info with structured output and caching. Advantages over direct CLI: • Returns structured JSON (vs parsing version strings) • Cached results for faster subsequent queries • Validates Xcode installation first • Consistent response for

xcodebuild-list

⚡ **Prefer this over 'xcodebuild -list'** - Gets structured project information with intelligent caching. Advantages over direct CLI: • Returns clean JSON (vs parsing raw xcodebuild output) • 1-hour intelligent caching prevents expensive re-runs • Validates Xcode installation and provides clear err

xcodebuild-showsdks

⚡ **Prefer this over 'xcodebuild -showsdks'** - Gets available SDKs with intelligent caching and structured output. Advantages over direct CLI: • Returns structured JSON data (vs parsing raw CLI text) • Smart caching prevents redundant SDK queries • Consistent error handling and validation • Clean,

xcodebuild-build

⚡ **Prefer this over raw 'xcodebuild'** - Intelligent building with learning, caching, and performance tracking. Why use this instead of direct xcodebuild: • 🧠 **Learns from your builds** - Remembers successful configurations per project • 🚀 **Smart defaults** - Auto-suggests optimal simulators b

xcodebuild-clean

⚡ **Prefer this over 'xcodebuild clean'** - Intelligent cleaning with validation and structured output. Advantages over direct CLI: • Pre-validates project exists and Xcode is installed • Structured JSON responses (vs parsing CLI output) • Better error messages and troubleshooting context • Consist

xcodebuild-get-details

Get detailed information from cached build results

simctl-list

🚨 **CRITICAL: Use this instead of 'xcrun simctl list'** - Prevents token overflow with intelligent progressive disclosure! Why this is essential over direct CLI: • 🔥 **Prevents token overflow** - Raw simctl output can be 10,000+ tokens, breaking conversations • 🎯 **Progressive disclosure** - Ret

simctl-get-details

Get detailed simulator information from cached simctl-list results with progressive disclosure

simctl-boot

⚡ **Prefer this over 'xcrun simctl boot'** - Intelligent boot with performance tracking and learning. Advantages over direct CLI: • 📊 **Performance tracking** - Records boot times for optimization insights • 🧠 **Learning system** - Tracks which devices work best for your projects • 🎯 **Smart rec

simctl-shutdown

⚡ **Prefer this over 'xcrun simctl shutdown'** - Intelligent shutdown with better device management. Advantages over direct CLI: • 🎯 **Smart device targeting** - "booted" and "all" options vs complex CLI syntax • 🛡️ **Better error handling** - Clear feedback when devices can't be shut down • 📊 *

list-cached-responses

List recent cached build/test results for progressive disclosure

cache-get-stats

Get comprehensive statistics about all cache systems (simulator, project, response). Shows cache hit rates, expiry times, storage usage, and performance metrics across all caching layers. Useful for: - Monitoring cache effectiveness - Debugging performance issues - Understanding usage patterns - C

cache-get-config

Get current cache configuration settings

cache-set-config

🎛️ **Cache Optimization** - Fine-tune XC-MCP's intelligent caching for your workflow. Why manage caching: • ⚡ **Performance tuning** - Longer caches = faster repeated operations • 🔄 **Fresh data control** - Shorter caches = more up-to-date information • 💾 **Memory management** - Balance speed

cache-clear

Clear cached data to force fresh data retrieval

persistence-enable

🔒 **Enable Opt-in Persistent State Management** - File-based persistence for cache data across server restarts. **Privacy First**: Disabled by default. Only usage patterns, build preferences, and performance metrics are stored. No source code, credentials, or personal information is persisted. Ke

persistence-disable

🔒 **Disable Persistent State Management** - Return to in-memory caching only. Safely disables file-based persistence and optionally clears existing cache data. After disabling, XC-MCP will operate with in-memory caching only, losing state on server restart. Use this when: • Privacy requirements c

persistence-status

🔒 **Get Persistence System Status** - Detailed information about persistent state management. Provides comprehensive status including: • Current enable/disable state • Cache directory location and permissions • Disk usage and file counts • Last save timestamps • Storage recommendations and health

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.17.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configXC_MCP_CACHE_DIR
configXDG_CACHE_HOME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

18/18 tools missing one or more hints — xcodebuild-version (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); xcodebuild-list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); xcodebuild-showsdks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

11/18 tools referenced in tests (61%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 calls in production code run through a shell (src/utils/command.ts:60, src/utils/validation.ts:7)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.17.1 (high), @modelcontextprotocol/sdk@1.17.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ericvoltolin/xc-mcp?variant=verified)](https://m8ven.ai/mcp/ericvoltolin/xc-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 84ccaf0f2bc15dc8bbde009d7396d1da86a9d5b6
code hash: 2ccb4906118065392a96b31de9ffeff2079f137873c85622980753dd48e86e6f
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client