Ios Simulator (yaelg) MCP Server
@yaelg/ios-simulator-mcp
npm
v1.0.19
Published by @yaelg — 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.
Findings 1
high Shell/command execution in server code (dist/index.js)MTC-SRC-002
In the server's implementation (`dist/index.js:9`): 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"; import { promisify } from "node:util"; //#region src/lib/paths.ts /** Expands a
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/index.js
Tools 39
Each tool and what it can reach — statically extracted from the published source.
app_logsno sensitive capabilityboot_simno sensitive capabilitycleanup_sessionno sensitive capabilitydoctorno sensitive capabilityexpo_launchno sensitive capabilityget_booted_sim_idno sensitive capabilityinstall_appno sensitive capabilitylaunch_appno sensitive capabilitylist_appsno sensitive capabilitylist_simsno sensitive capability
Show 29 more tools ↓
open_urlno sensitive capabilitypush_notificationno sensitive capabilityrecord_videono sensitive capabilityreset_appno sensitive capabilityscreenshotno sensitive capabilityselect_default_deviceno sensitive capabilityset_appearanceno sensitive capabilityset_locationno sensitive capabilityset_orientationno sensitive capabilityset_permissionsno sensitive capabilityshutdown_simno sensitive capabilitystatus_barno sensitive capabilitystop_recordingno sensitive capabilityterminate_appno sensitive capabilityui_describe_pointno sensitive capabilityui_double_tapno sensitive capabilityui_inspectno sensitive capabilityui_keyno sensitive capabilityui_panno sensitive capabilityui_pinchno sensitive capabilityui_pressno sensitive capabilityui_scrollno sensitive capabilityui_snapshotno sensitive capabilityui_swipeno sensitive capabilityui_tapno sensitive capabilityui_typeno sensitive capabilityui_viewno sensitive capabilityuninstall_appno sensitive capabilitywait_for_elementno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (39 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 1
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.0.19 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
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 @yaelg/ios-simulator-mcp --onlineOther implementations of Ios Simulator 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
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.