Mobile MCP (mobile-next)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Transport (tested 2026-10-29): stdio
Score 70/100 · Tools 34 · Token cost ~5,785 · Compare · Last tested 2026-10-29 · Version tested 1.0.14 · Package @mobilenext/mobile-mcp · Repo mobile-next/mobile-mcp
Summary: Mobile MCP (mobile-next) completed an MCP handshake without credentials and exposed 34 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 34
- Context cost
- 5,785 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 796 tokens; raw tools/list total 6,581. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key to connect (handshake passed)
- Tested
- 2026-10-29
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @mobilenext/mobile-mcp (Node 20, Linux) succeeded in 5s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 34 tools listed in 5.2s. |
| maintenance | pass | 25 | Repo pushed 2 days before test; 10,110 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Schema context cost: ~5,785 tokens for 34 tools (26,631 bytes) · about 71% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-10-29
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 34 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-29 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
3348a7005cc1: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@mobilenext/mobile-mcp",
"version": "1.0.14",
"registry": "npm",
"status": "working",
"tested": "2026-10-29",
"tools_count": 34,
"tools_schema_tokens_est": 5785,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @mobilenext/mobile-mcp` (Node 20, Linux) succeeded in 5s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 34 tools listed in 5.2s."
],
"maintenance": [
"pass",
25,
"Repo pushed 2 days before test; 10,110 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
npx -y @mobilenext/mobile-mcp
Tools listed
get_more_tools, mobile_list_available_devices, mobile_login_to_cloud_provider, mobile_list_remote_devices, mobile_allocate_remote_device, mobile_release_remote_device, mobile_list_apps, mobile_get_foreground_app, mobile_launch_app, mobile_terminate_app, mobile_install_app, mobile_uninstall_app, mobile_get_screen_size, mobile_click_on_screen_at_coordinates, mobile_double_tap_on_screen, mobile_long_press_on_screen_at_coordinates, mobile_list_elements_on_screen, mobile_press_button, mobile_open_url, mobile_swipe_on_screen, mobile_type_keys, mobile_save_screenshot, mobile_take_screenshot, mobile_set_orientation, mobile_fold_device, mobile_set_location, mobile_clipboard, mobile_get_device_logs, mobile_get_orientation, mobile_start_screen_recording, mobile_stop_screen_recording, mobile_list_crashes, mobile_get_crash, mobile_batch_commands
Quick config
{
"mcpServers": {
"mobile-mcp-mobile-next": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @mobilenext/mobile-mcp(Node 20). This is the exact command we ran on 2026-10-29. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (34 in our test).
{
"mcpServers": {
"mobile-mcp-mobile-next": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is Mobile MCP (mobile-next) deprecated?
No. @mobilenext/mobile-mcp was not deprecated or archived when we last tested it on 2026-10-29.
What replaces Mobile MCP (mobile-next)?
Nothing; Mobile MCP (mobile-next) is not deprecated as of 2026-10-29.
Does Mobile MCP (mobile-next) need an API key?
No. It completed an MCP handshake with no credentials and listed 34 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.