Open Mobile MCP Server
open-mobile-mcp
npm
v1.1.3
Published by xzaleksey — 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 Android and iOS mobile automation — control devices, read logs, and test React Native / Expo apps with LLMs.
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 13
high Tool "manage_bundler" exposes command/code executionMTC-CAP-001
Tool "manage_bundler" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool manage_bundler
high Shell/command execution in server code (build/environment/doctor.js)MTC-SRC-002
In the server's implementation (`build/environment/doctor.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: import { exec } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); export asyn
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/environment/doctor.js
high Shell/command execution in server code (build/environment/lifecycle.js)MTC-SRC-002
In the server's implementation (`build/environment/lifecycle.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: import { exec } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); export asyn
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/environment/lifecycle.js
high Shell/command execution in server code (build/environment/metro.js)MTC-SRC-002
In the server's implementation (`build/environment/metro.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: t { exec, spawn } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); let metroPr
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/environment/metro.js
high Shell/command execution in server code (build/index.js)MTC-SRC-002
In the server's implementation (`build/index.js:17`): 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 { exec } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); const serve
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/index.js
high Shell/command execution in server code (build/interaction/input.js)MTC-SRC-002
In the server's implementation (`build/interaction/input.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: t { exec, spawn } from "child_process"; import { promisify } from "util"; import { runMaestroFlow } from "./maestro.js";
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/interaction/input.js
high Shell/command execution in server code (build/interaction/maestro.js)MTC-SRC-002
In the server's implementation (`build/interaction/maestro.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: import { exec } from "child_process"; import fs from "fs/promises"; import os from "os"; import path from "path"; impo
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/interaction/maestro.js
high Shell/command execution in server code (build/interaction/navigation.js)MTC-SRC-002
In the server's implementation (`build/interaction/navigation.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: import { exec } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); export asyn
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/interaction/navigation.js
high Shell/command execution in server code (build/perception/device.js)MTC-SRC-002
In the server's implementation (`build/perception/device.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: import { exec } from "child_process"; import { promisify } from "util"; const execAsync = promisify(exec); export asyn
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/perception/device.js
high Shell/command execution in server code (build/perception/element.js)MTC-SRC-002
In the server's implementation (`build/perception/element.js:122`): 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: exec } = await import("child_process"); const { promisify } = await import("util"); const execA
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/perception/element.js
high Shell/command execution in server code (build/perception/hierarchy.js)MTC-SRC-002
In the server's implementation (`build/perception/hierarchy.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: import { exec } from "child_process"; import { promisify } from "util"; import * as xml2js from "xml2js"; const execAs
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/perception/hierarchy.js
medium Unconstrained command parameter "command" on "manage_bundler"MTC-CAP-006
Tool "manage_bundler" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool manage_bundler · inputSchema.properties.command
low Mutating tool "manage_bundler" declares no destructiveHintMTC-CAP-005
Tool "manage_bundler" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool manage_bundler
Tools 32
Each tool and what it can reach — statically extracted from the published source.
manage_bundlerruns code / shellanalyze_layout_healthno sensitive capabilitycapture_diffno sensitive capabilityclear_app_datano sensitive capabilityconfigure_ocrno sensitive capabilitydevice_listno sensitive capabilitydevice_pinchno sensitive capabilitydevice_press_keyno sensitive capabilitydevice_rotate_gestureno sensitive capabilitydevice_swipeno sensitive capability
Show 22 more tools ↓
device_tapno sensitive capabilitydevice_typeno sensitive capabilityfind_elementno sensitive capabilityget_app_infono sensitive capabilityget_bundler_logsno sensitive capabilityget_element_imageno sensitive capabilityget_network_logsno sensitive capabilityget_screen_textno sensitive capabilityget_semantic_hierarchyno sensitive capabilityget_viewportno sensitive capabilityinstall_depsno sensitive capabilitymanage_app_lifecycleno sensitive capabilitymanage_platform_logsno sensitive capabilityopen_deep_linkno sensitive capabilityrun_doctorno sensitive capabilityrun_maestro_flowno sensitive capabilitystart_recordingno sensitive capabilitystop_recordingno sensitive capabilitystream_errorsno sensitive capabilitytap_on_elementno sensitive capabilitywait_for_elementno sensitive capabilitywait_for_logno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (32 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.1.3 latest |
A 93/100 | 13 | 1.13.0 | 2026-09-07 |
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 open-mobile-mcp --onlineMore in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.