LeashIndex Get the report

Index / data

io.github.mobile-next/mobile-mcp

io-github-mobile-next-mobile-mcp declares 35 capabilities across 35 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

88/100 exposureHigh exposure

Manifest recorded 2026-11-03 from tools/list answered by the npm package @mobilenext/mobile-mcp@1.0.16 (published to npm as @mobilenext/mobile-mcp, listed in the official MCP registry as io.github.mobile-next/mobile-mcp 1.0.16), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 35 tools

35 of 35 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · destructive-uncapped · 4 of 35 tools

4 tools are annotated by the server as destructive (destructiveHint) and declare no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

high · no-expiry · All 35 tools

35 of 35 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 35 tools

35 of 35 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 18 of 35 tools

18 tools can modify data and declare no limit.

low · uncapped-read · 13 of 35 tools

13 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
get_more_toolsread declared
mobile_list_available_devicesread declared
mobile_login_to_cloud_providerwrite assumed
mobile_list_remote_devicesread declared
mobile_allocate_remote_devicewrite assumed
mobile_release_remote_devicedestructive declared
mobile_list_appsread declared
mobile_get_foreground_appread declared
mobile_launch_appwrite assumed
mobile_terminate_appwrite assumed
mobile_clear_app_datadestructive declared
mobile_install_appwrite assumed
mobile_uninstall_appdestructive declared
mobile_get_screen_sizeread declared
mobile_click_on_screen_at_coordinateswrite assumed
mobile_double_tap_on_screenwrite assumed
mobile_long_press_on_screen_at_coordinateswrite assumed
mobile_list_elements_on_screenread declared
mobile_press_buttonwrite assumed
mobile_open_urlwrite assumed
mobile_swipe_on_screenwrite assumed
mobile_type_keyswrite assumed
mobile_save_screenshotwrite assumed
mobile_take_screenshotread declared
mobile_set_orientationwrite inferred
mobile_fold_devicewrite assumed
mobile_set_locationwrite inferred
mobile_clipboardread inferred
mobile_get_device_logsread declared
mobile_get_orientationread declared
mobile_start_screen_recordingwrite assumed
mobile_stop_screen_recordingwrite assumed
mobile_list_crashesread declared
mobile_get_crashread declared
mobile_batch_commandsdestructive declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-11-0288 tools/list answered by the npm package @mobilenext/mobile-mcp@1.0.15 (published to npm as @mobilenext/mobile-mcp, listed in the official MCP registry as io.github.mobile-next/mobile-mcp 1.0.15), run in an isolated container with no network access and no credentials
2026-10-2986 tools/list answered by the npm package @mobilenext/mobile-mcp@1.0.14 (published to npm as @mobilenext/mobile-mcp, listed in the official MCP registry as io.github.mobile-next/mobile-mcp 1.0.14), run in an isolated container with no network access and no credentials
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.