Xcode Pilot MCP Server
xcode-pilot-mcp
npm
v1.1.0
Published by sitharaj88 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for iOS/macOS development with Xcode, Simulator, and device management
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 5
high Shell/command execution in server code (build/executor.js)MTC-SRC-002
In the server's implementation (`build/executor.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ile, spawn } from "node:child_process"; const DEFAULT_TIMEOUT = 120_000; const DEFAULT_MAX_BUFFER = 10 * 1024 * 1024; ex
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/executor.js
high Shell/command execution in server code (build/tools/app/launch.js)MTC-SRC-002
In the server's implementation (`build/tools/app/launch.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { executeCommand } from "../../executor.js"; import { textResponse, error
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/tools/app/launch.js
high Shell/command execution in server code (build/tools/debug/log-stream.js)MTC-SRC-002
In the server's implementation (`build/tools/debug/log-stream.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { textResponse, errorResponse } from "../../utils/response.js"; export as
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/tools/debug/log-stream.js
high Shell/command execution in server code (build/tools/debug/screen-record.js)MTC-SRC-002
In the server's implementation (`build/tools/debug/screen-record.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { statSync } from "node:fs"; import { textResponse, errorResponse } from
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/tools/debug/screen-record.js
high Shell/command execution in server code (build/tools/device/console.js)MTC-SRC-002
In the server's implementation (`build/tools/device/console.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { textResponse, errorResponse } from "../../utils/response.js"; import {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/tools/device/console.js
Tools 65
Each tool and what it can reach — statically extracted from the published source.
app_get_containerno sensitive capabilityapp_installno sensitive capabilityapp_launchno sensitive capabilityapp_listno sensitive capabilityapp_open_urlno sensitive capabilityapp_privacyno sensitive capabilityapp_terminateno sensitive capabilityapp_uninstallno sensitive capabilitybinary_sizeno sensitive capabilitybuild_warningsno sensitive capability
Show 55 more tools ↓
device_appearanceno sensitive capabilitydiagnosticsno sensitive capabilitydsym_verifyno sensitive capabilityentitlements_checkno sensitive capabilityipa_analyzeno sensitive capabilityipa_permissionsno sensitive capabilitykeychain_listno sensitive capabilitylocation_clearno sensitive capabilitylocation_setno sensitive capabilitylog_collectno sensitive capabilitylog_streamno sensitive capabilityphysical_device_consoleno sensitive capabilityphysical_device_installno sensitive capabilityphysical_device_launchno sensitive capabilityphysical_device_listno sensitive capabilitypod_installno sensitive capabilitypod_outdatedno sensitive capabilitypod_updateno sensitive capabilityprofile_inspectno sensitive capabilityproject_createno sensitive capabilityprovisioning_profilesno sensitive capabilitypush_notificationno sensitive capabilityscaffold_coredata_modelno sensitive capabilityscaffold_viewno sensitive capabilityscaffold_viewmodelno sensitive capabilityscaffold_widgetno sensitive capabilityscreen_recordno sensitive capabilityscreenshotno sensitive capabilitysigning_identitiesno sensitive capabilitysimulator_bootno sensitive capabilitysimulator_cloneno sensitive capabilitysimulator_createno sensitive capabilitysimulator_deleteno sensitive capabilitysimulator_eraseno sensitive capabilitysimulator_listno sensitive capabilitysimulator_list_device_typesno sensitive capabilitysimulator_list_runtimesno sensitive capabilitysimulator_openno sensitive capabilitysimulator_shutdownno sensitive capabilityspm_resolveno sensitive capabilityspm_show_dependenciesno sensitive capabilityspm_updateno sensitive capabilitystatus_bar_clearno sensitive capabilitystatus_bar_overrideno sensitive capabilityswift_format_runno sensitive capabilityswiftlint_fixno sensitive capabilityswiftlint_runno sensitive capabilityxcode_archiveno sensitive capabilityxcode_buildno sensitive capabilityxcode_build_settingsno sensitive capabilityxcode_cleanno sensitive capabilityxcode_exportno sensitive capabilityxcode_listno sensitive capabilityxcode_testno sensitive capabilityxcode_test_without_buildingno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (65 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.0 latest |
A 93/100 | 5 | 1.13.0 | 2026-09-09 |
v1.0.0 |
A 93/100 | 4 | 1.12.1 | 2026-08-16 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan xcode-pilot-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.