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.

C
Emerging
74/100
16 days ago

mobile-mcp

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

Code Verified⚡ Live Monitored: not connected

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

Is this your MCP?

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.

// key findings
1 tools verified — handlers match their declared behaviour
1 read-only tool verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// known CVEs in dependencies1 low

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

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configANDROID_HOME
configGO_IOS_PATH
configLOG_FILE
configMOBILECLI_PATH
configMOBILEMCP_ALLOW_UNSAFE_URLSAllow mobile_open_url to open non-standard URL schemes (blocked by default). MOBILEMCP_ALLOW_UNSAFE_URLS=1
configMOBILEMCP_AUTHTo require Bearer token authorization on the SSE server, set the environment variable:
configMOBILEMCP_DISABLE_TELEMETRYDisable anonymous usage telemetry. MOBILEMCP_DISABLE_TELEMETRY=1
configMOBILEMCP_LEGACY_ROBOTUse the legacy platform-specific robots for Android devices and physical iOS devices. iOS simulators continue to use mobilecli. MOBILEMCP_LEGACY_ROBOT=1
configplatform🧠 No expertise required: no XCUITest, no Espresso, no per-platform glue — describe the goal and the agent does it.
// quality suggestions

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mobile-next-mobile-mcp-1gnc74)](https://m8ven.ai/mcp/mobile-next-mobile-mcp-1gnc74)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 48250f81a9e6df8a1f0960185eb7fd7abba886c8
code hash: 401b67e178c39f2b74ceb787e41230a48985aa0bd9401e8a4f78630715b1b632
verified: 8/13/2026, 8:55:27 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client