xc-mcp
npm
v4.0.1
Published by conorluddy — 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.
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.
In the server's implementation (`dist/tools/diagnostics/hang/tools.js:2`): 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: import { spawn } from 'child_process'; import { McpError, ErrorCode } from '@modelcontextprotocol/sdk/types.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 dist/tools/diagnostics/hang/tools.js
In the server's implementation (`dist/utils/command.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: execSync, spawn } from 'child_process'; import { promisify } from 'util'; import { McpError, ErrorCode } from '@modelcon
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 dist/utils/command.js
In the server's implementation (`dist/utils/validation.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: port { execSync } from 'child_process'; import { access, constants, stat } from 'fs/promises'; import { McpError, ErrorC
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 dist/utils/validation.js
Each tool and what it can reach — statically extracted from the published source.
accessibility-auditno sensitive capabilityaccessibility-quality-checkno sensitive capabilitycache-clearno sensitive capabilitycache-get-configno sensitive capabilitycache-get-statsno sensitive capabilitycache-set-configno sensitive capabilityhang-get-detailsno sensitive capabilityhang-listno sensitive capabilityhang-startno sensitive capabilityhang-stopno sensitive capabilityidb-installno sensitive capabilityidb-launchno sensitive capabilityidb-list-appsno sensitive capabilityidb-targetsno sensitive capabilityidb-terminateno sensitive capabilityidb-ui-describeno sensitive capabilityidb-ui-find-elementno sensitive capabilityidb-ui-gestureno sensitive capabilityidb-ui-inputno sensitive capabilityidb-ui-tapno sensitive capabilityidb-uninstallno sensitive capabilitylocalization-auditno sensitive capabilitypersistence-disableno sensitive capabilitypersistence-enableno sensitive capabilitypersistence-statusno sensitive capabilityrtfmno sensitive capabilityscreenshotno sensitive capabilitysimctl-addmediano sensitive capabilitysimctl-appearanceno sensitive capabilitysimctl-bootno sensitive capabilitysimctl-cloneno sensitive capabilitysimctl-containerno sensitive capabilitysimctl-createno sensitive capabilitysimctl-deleteno sensitive capabilitysimctl-eraseno sensitive capabilitysimctl-get-app-containerno sensitive capabilitysimctl-get-detailsno sensitive capabilitysimctl-health-checkno sensitive capabilitysimctl-installno sensitive capabilitysimctl-iono sensitive capabilitysimctl-launchno sensitive capabilitysimctl-listno sensitive capabilitysimctl-locationno sensitive capabilitysimctl-openurlno sensitive capabilitysimctl-pbcopyno sensitive capabilitysimctl-privacyno sensitive capabilitysimctl-pushno sensitive capabilitysimctl-renameno sensitive capabilitysimctl-shutdownno sensitive capabilitysimctl-status-barno sensitive capabilitysimctl-stream-logsno sensitive capabilitysimctl-suggestno sensitive capabilitysimctl-terminateno sensitive capabilitysimctl-uninstallno sensitive capabilitytest-record-reportno sensitive capabilitytest-record-stepno sensitive capabilityvisual-diffno sensitive capabilityworkflow-build-and-runno sensitive capabilityworkflow-fresh-installno sensitive capabilityworkflow-tap-elementno sensitive capabilityxcode-model-inspectno sensitive capabilityxcodebuild-buildno sensitive capabilityxcodebuild-cleanno sensitive capabilityxcodebuild-get-detailsno sensitive capabilityxcodebuild-inspect-schemeno sensitive capabilityxcodebuild-listno sensitive capabilityxcodebuild-showsdksno sensitive capabilityxcodebuild-testno sensitive capabilityxcodebuild-validate-capabilitiesno sensitive capabilityxcodebuild-versionno sensitive capabilityScan 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 |
|---|---|---|---|---|
v4.0.1 latest |
A 93/100 | 3 | 1.9.0 | 2026-07-24 |
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.
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 xc-mcp --online
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.