Android (martingeidobler) MCP Server
android-mcp-server
npm
v1.3.0
Published by martingeidobler — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for controlling Android emulators via ADB
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 4
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([get_logs]) and tools that can send data out ([adb_shell]) are exposed together. An agent can move private data to the sink.
Evidence: sources [get_logs] → sinks [adb_shell]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow get_logs → adb_shell
high Tool "adb_shell" exposes command/code executionMTC-CAP-001
Tool "adb_shell" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool adb_shell
high Shell/command execution in server code (dist/adb.js)MTC-SRC-002
In the server's implementation (`dist/adb.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ile, spawn } from "node:child_process"; import { promisify } from "node:util"; import { existsSync } from "node:fs"; imp
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/adb.js
low Mutating tool "adb_shell" declares no destructiveHintMTC-CAP-005
Tool "adb_shell" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool adb_shell
Tools 25
Each tool and what it can reach — statically extracted from the published source.
adb_shellruns code / shellget_logsreads sensitive dataclear_logsno sensitive capabilitydouble_tapno sensitive capabilityget_current_activityno sensitive capabilityget_device_infono sensitive capabilityget_ui_treeno sensitive capabilityinstall_apkno sensitive capabilitylaunch_appno sensitive capabilitylist_avdsno sensitive capability
Show 15 more tools ↓
list_devicesno sensitive capabilitylong_pressno sensitive capabilitymulti_tapno sensitive capabilitypress_keyno sensitive capabilitypull_fileno sensitive capabilityscreenshotno sensitive capabilityscroll_to_elementno sensitive capabilitystart_emulatorno sensitive capabilityswipeno sensitive capabilitytapno sensitive capabilitytap_and_waitno sensitive capabilitytap_elementno sensitive capabilitytap_sequenceno sensitive capabilitytype_textno sensitive capabilitywait_for_elementno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (25 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.0 latest |
A 93/100 | 4 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan android-mcp-server --onlineOther implementations of Android 6
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
Android MCP server - ADB-based device management, UI automation, logcat, emulator control, and more
MCP server exposing Gbox Android control tools via Model Context Protocol
Android MCP Server for automated app control using uiautomator2
Lightweight MCP Server for Android Operating System
MCP Server for Android device control via ADB and scrcpy
MCP server exposing Android Debug Bridge (ADB) to AI assistants
More in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.