mobile-mcp (mobile-next/mobile-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.
A Model Context Protocol server that enables scalable mobile automation through a platform-agnostic interface for iOS and Android devices, allowing agents and LLMs to interact with mobile applications using accessibility snapshots or coordinate-based interactions.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
mobile-next
Source: modelscope · also listed on mcp.so
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
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set
ANDROID_HOMEGO_IOS_PATHLOG_FILEMOBILECLI_PATHMOBILEMCP_ALLOW_UNSAFE_URLSAllow mobile_open_url to open non-standard URL schemes (blocked by default). MOBILEMCP_ALLOW_UNSAFE_URLS=1MOBILEMCP_AUTHTo require Bearer token authorization on the SSE server, set the environment variable:MOBILEMCP_DISABLE_TELEMETRYDisable anonymous usage telemetry. MOBILEMCP_DISABLE_TELEMETRY=1MOBILEMCP_LEGACY_ROBOTUse the legacy platform-specific robots for Android devices and physical iOS devices. iOS simulators continue to use mobilecli. MOBILEMCP_LEGACY_ROBOT=1platform🧠 No expertise required: no XCUITest, no Espresso, no per-platform glue — describe the goal and the agent does it.Dependencies
26 dependencies, 1 flagged: @playwright/test
All four hints declared on every tool
1/1 tools missing one or more hints — mobile_take_screenshot (missing: destructiveHint, idempotentHint, openWorldHint). 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.
Tool test coverage
Only 0/1 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Shell command execution
25 child_process/subprocess calls in production code — runs shell commands (src/android.ts:81, src/android.ts:88, src/android.ts:542)
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Domain consistency
npm scope @mobilenext doesn't match GitHub owner mobile-next
Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.
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.
[](https://m8ven.ai/mcp/mobile-next-mobile-mcp-1gnc74)?variant=verified to the badge URL.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