Mobilebox: Cloud phones for your agents MCP server
dev.mobilebox/mobileboxmobilebox.devstreamable-httpv1.0.7Scanned
A mobile sandbox for every agent: cloud Android phones over MCP, ready in ~20 s, $0.01/min.
12 tools: 2 can delete or cancel things, 6 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Mobilebox: Cloud phones for your agents MCP server can do
The Mobilebox: Cloud phones for your agents MCP server is published by mobilebox.dev, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (2 tools: delete_phone and uninstall_app) and create or change data (6 tools: create_phone, start_phone, park_phone, set_device and 2 more). 4 tools only read.
1 tool can send data out of your system (install_app).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 4, 2026, version 1.0.7.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 2Claude Code: deny
delete_phoneDelete a phone and everything on it.No findings
Why it is in this group
- The name "delete_phone" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a phone and everything on it. Prefer park_phone.
uninstall_appUninstall an app and delete its data.No findings
Why it is in this group
- The name "uninstall_app" says "uninstall": a word for removing or ending something.
Description, as the server wrote it Uninstall an app and delete its data.
Changes things 6Claude Code: ask
actRun 1–20 actions in order, stop at the first failure, return results and the new screen.No findings
Why it is in this group
- The description's first verb is "run": a word for a change.
Description, as the server wrote it 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}.
create_phoneCreate a phone, wait until it is ready and return its first screen.No findings
Why it is in this group
- The name "create_phone" says "create": a word for a change.
Description, as the server wrote it Create a phone, wait until it is ready and return its first screen. Give each task or end user its own phone.
install_appInstall 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).Can send data outNo findings
Why it is in this group
- The name "install_app" says "install": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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":…}.
park_phonePark a phone: shuts it down and stops billing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Park a phone: shuts it down and stops billing. Apps, data and logins stay; apps start fresh after start_phone (like after a reboot). Always park when done.
set_deviceSet 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).No findings
Why it is in this group
- The name "set_device" says "set": a word for a change.
Description, as the server wrote it 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).
start_phoneResume a parked phone.No findings
Why it is in this group
- The name "start_phone" says "start": a word for a change.
Description, as the server wrote it Resume a parked phone. Its apps and logins are kept.
Only reads 4Show 4 read-only tools
list_appsApps the user installed on this phone.No findings
Why it is in this group
- The name "list_apps" says "list": a word for reading.
Description, as the server wrote it Apps the user installed on this phone.
list_phonesList this project's phones and their status.No findings
Why it is in this group
- The name "list_phones" says "list": a word for reading.
Description, as the server wrote it List this project's phones and their status.
observeRead the current screen as a numbered element list.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it Read the current screen as a numbered element list.
screenshotPNG of the screen, for content the element list cannot show (images, maps, games).No findings
Why it is in this group
- The name "screenshot" says "screenshot": a word for reading.
Description, as the server wrote it PNG of the screen, for content the element list cannot show (images, maps, games).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata
- https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mobilebox.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 12, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://mobilebox.dev
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 7 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://mobilebox.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://mobilebox.dev
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 1.0.7. Values in angle brackets are yours to fill in.
claude mcp add --transport http mobilebox https://mobilebox.dev/mcpclaude mcp add --transport http mobilebox https://mobilebox.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__mobilebox__list_phones",
"mcp__mobilebox__list_apps",
"mcp__mobilebox__observe",
"mcp__mobilebox__screenshot"
],
"ask": [
"mcp__mobilebox__create_phone",
"mcp__mobilebox__start_phone",
"mcp__mobilebox__park_phone",
"mcp__mobilebox__set_device",
"mcp__mobilebox__install_app",
"mcp__mobilebox__act"
],
"deny": [
"mcp__mobilebox__delete_phone",
"mcp__mobilebox__uninstall_app"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mobilebox. Review it before you use it.
Capability tags behind 1 rule
- mcp__mobilebox__install_app outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.mobilebox/mobilebox/verify?hash=cb29d108e3aa38d03da6604353e03f9e1577b7faad6953f6ed9ff6de4849b4b9" | jq -e '.changed == false'Pinned hash cb29d108e3aa, from Nov 4, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.mobilebox/mobilebox/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.mobilebox/mobilebox)Source: MCP Registry · repository. Synced Nov 19, 2026, 19:17 UTC.
Mobilebox: Cloud phones for your agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Mobilebox: Cloud phones for your agents MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Mobilebox: Cloud phones for your agents MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: delete_phone and uninstall_app.
Can the Mobilebox: Cloud phones for your agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Mobilebox: Cloud phones for your agents MCP server have?
- 12 tools: 2 destructive, 6 write, 4 read. delete_phone, uninstall_app, create_phone, start_phone, park_phone, set_device, install_app, act and 4 more.
Does the Mobilebox: Cloud phones for your agents MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the Mobilebox: Cloud phones for your agents MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): install_app.
Has the Mobilebox: Cloud phones for your agents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 4, 2026.