LeashIndex Get the report

Index / storage

AndroidMCP Framework

io-github-kshivam1177-androidmcp-framework declares 30 capabilities across 30 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-10-27 from tools/list answered by the npm package androidmcp-framework@0.1.12 (published to npm as androidmcp-framework, listed in the official MCP registry as io.github.kshivam1177/androidmcp-framework 0.1.12), 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 30 tools

30 of 30 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 · irreversible-uncapped · 6 of 30 tools

6 tools are classified as irreversible or destructive and declare no limit. 4 of them are counted only because the server annotated them destructiveHint. 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 30 tools

30 of 30 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 30 tools

30 of 30 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 · 15 of 30 tools

15 tools can modify data and declare no limit.

low · uncapped-read · 9 of 30 tools

9 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
list_devicesread declared
build_devicewrite assumed
build_run_devicewrite assumed
install_app_devicewrite assumed
launch_app_devicewrite assumed
stop_app_devicedestructive declared
uninstall_app_devicedestructive declared
clear_app_data_devicedestructive declared
test_devicewrite assumed
push_file_devicewrite inferred
pull_file_deviceread declared
snapshot_uiread declared
tapwrite assumed
long_presswrite assumed
swipewrite assumed
dragread inferred
type_textwrite assumed
key_presssend inferred
buttonwrite assumed
gesturewrite assumed
screenshotread declared
wait_for_uiread declared
batchwrite assumed
touchsend inferred
session_show_defaultsread declared
session_set_defaultswrite inferred
session_clear_defaultsdestructive declared
session_use_defaults_profilewrite assumed
doctorread declared
manage_workflowsread inferred
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.