Mobilebox
REMOTE · MOBILEBOX.DEV
Cloud Android phones for AI agents: read the screen, tap, type, install APKs, park and resume.
Available components
Last scanned (4 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 963 tokens (~80/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_phone" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_phone” rewrote its description, which is the text the model reads security
- Tool “delete_phone” rewrote its description, which is the text the model reads security
- Tool “park_phone” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 80 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 1.0.0 functional
- “create_phone” added an optional parameter “device” cosmetic
- “create_phone” added an optional parameter “platform” cosmetic
- 4 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mobilebox.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mobilebox.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| mobilebox.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mobilebox.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mobilebox.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
act ~123
Run 1–20 actions in order, stop at the first failure, return results and the new screen. Types: tap, long_press, swipe, scroll, scroll_to {text}, type, key, back, home, open_app, close_app (force-stop), wait, wait_for. Target: {"text":"OK"} | {"ref":3} | {"id":"…"} | {"desc":"…"} | {"x":540,"y":1200}.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
create_phone ~219
Create a phone, wait until it is ready and return its first screen. Give each task or end user its own phone. Phones are cloud Android; iOS and real devices are early access.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter code, e.g. DE: sets a matching timezone, locale and GPS location |
| device | string | – | cloud (default). real is early access: you get a cloud phone now, and this account joins the list |
| idempotency_key | string | – | Any unique value, e.g. a UUID. Retrying with the same key and options returns the same phone instead of a second one (24 h). |
| idle_timeout | integer | – | Seconds without calls before it parks itself (default 300) |
| max_duration | integer | – | Longest session in seconds (default 900) |
| name | string | – | – |
| platform | string | – | android (default). ios is in early access: answered with early_access and a link to book an onboarding call; this account joins the list |
No output schema declared.
No examples provided.
delete_phone ~38
Delete a phone and everything on it. Do this when done with a disposable phone.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
install_app ~119
Install or update an app from a public download URL: an APK (arm64-v8a or universal) or a split bundle (.apks/.xapk; the splits this phone needs are picked). Then open it with act {"type":"open_app","package":…}.
| Name | Type | Req | Description |
|---|---|---|---|
| grant_permissions | boolean | – | Grant all runtime permissions up front instead of answering the dialogs |
| phone_id | string | yes | Phone id, ph_… |
| url | string | yes | Direct https link to the .apk, .apks or .xapk file |
No output schema declared.
No examples provided.
list_apps ~29
Apps the user installed on this phone.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
list_phones ~17
List this project's phones and their status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
observe ~30
Read the current screen as a numbered element list.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
park_phone ~60
Park a phone: shuts it down and stops billing. Apps, data and logins stay; apps start fresh after start_phone (like after a reboot). Park only a phone you will resume.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
screenshot ~39
PNG of the screen, for content the element list cannot show (images, maps, games).
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
set_device ~110
Set where the phone is: timezone (IANA), locale (BCP-47), GPS location, and proxy (socks5://user:pass@host:port; all traffic leaves through it, null = direct). Kept across park/start. Changing the locale restarts the UI (~15 s).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| location | object | – | – |
| phone_id | string | yes | Phone id, ph_… |
| proxy | – | – | – |
| timezone | string | – | – |
No output schema declared.
No examples provided.
start_phone ~34
Resume a parked phone. Its apps and logins are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
uninstall_app ~37
Uninstall an app and delete its data.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | – |
| phone_id | string | yes | Phone id, ph_… |
No output schema declared.
No examples provided.
How do I install the Mobilebox MCP server?
Mobilebox is a hosted endpoint at https://mobilebox.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mobilebox.dev
claude mcp add --transport http dev-mobilebox-mobilebox 'https://mobilebox.dev/mcp'
What is the Mobilebox MCP server?
Mobilebox is an MCP server listed in the public MCP registry as dev.mobilebox/mobilebox. Cloud Android phones for AI agents: read the screen, tap, type, install APKs, park and resume. This page covers its hosted endpoint (https://mobilebox.dev/mcp).
Is the Mobilebox MCP server safe to use?
Mobilebox scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mobilebox MCP server expose?
Mobilebox exposes 12 tools: list_phones, create_phone, start_phone, park_phone, delete_phone, and 7 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.
Does the Mobilebox MCP server require authentication?
Yes. Mobilebox asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Mobilebox MCP server still maintained?
Mobilebox is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.