@abhinavyadav/adb-mcp-server
npm
v1.0.1
Published by @abhinavyadav — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Android Debug Bridge (ADB) — manage connected devices, run shell commands, view logcats, query SQLite databases and more.
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 − 8 = 92. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
Tools that read sensitive data ([query_sqlite, dump_ui_hierarchy, get_app_memory, get_logcat]) and tools that can send data out ([execute_shell_command]) are exposed together. An agent can move private data to the sink.
Evidence: sources [query_sqlite, dump_ui_hierarchy, get_app_memory, get_logcat] → sinks [execute_shell_command]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow query_sqlite → execute_shell_command
Tool "execute_shell_command" appears to run shell commands or evaluate code (keyword "execute shell" in tool name, parameter "command"). 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 execute_shell_command
In the server's implementation (`dist/adb-utils.js:28`): 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: ponse; } }); const _child_process = require("child_process"); const _util = require("util"); const execFileAsync = (
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-utils.js
Tool "execute_shell_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool execute_shell_command · inputSchema.properties.command
Tool "execute_shell_command" 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 execute_shell_command
Each tool and what it can reach — statically extracted from the published source.
dump_ui_hierarchyreads sensitive dataexecute_shell_commandruns code / shellget_app_memoryreads sensitive dataget_logcatreads sensitive dataquery_sqlitereads sensitive dataclear_app_datano sensitive capabilityclear_logcatno sensitive capabilityconnect_deviceno sensitive capabilitydisconnect_deviceno sensitive capabilityexecute_raw_adbno sensitive capabilityforce_stop_appno sensitive capabilityforward_portno sensitive capabilityget_app_usageno sensitive capabilityget_cpu_usageno sensitive capabilityget_dbinfono sensitive capabilityget_device_stateno sensitive capabilityget_dumpsysno sensitive capabilityget_propertiesno sensitive capabilityget_shared_preferencesno sensitive capabilitygrant_permissionno sensitive capabilityinstall_appno sensitive capabilitylist_devicesno sensitive capabilitylist_forwardsno sensitive capabilitylist_packagesno sensitive capabilitylist_reversesno sensitive capabilitylist_shared_preferencesno sensitive capabilitypull_fileno sensitive capabilitypush_fileno sensitive capabilityreboot_deviceno sensitive capabilityrecord_screenno sensitive capabilityreverse_portno sensitive capabilityrevoke_permissionno sensitive capabilityroot_deviceno sensitive capabilitysend_keyeventno sensitive capabilityset_mock_locationno sensitive capabilitystart_app_activityno sensitive capabilityswipe_screenno sensitive capabilitytake_screenshotno sensitive capabilitytap_screenno sensitive capabilitytype_textno sensitive capabilityuninstall_appno sensitive capabilityunroot_deviceno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.0.1 latest |
A 92/100 | 5 | 1.13.0 | 2026-09-07 |
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.
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 @abhinavyadav/adb-mcp-server --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server for Android Debug Bridge (ADB) interactions in TypeScript
Remote-network ADB MCP server. Drive Android devices over the network from any MCP-compatible agent (OpenClaw, Hermes, Claude Desktop, Claude Code, Cursor, Codex). Built for headless setups — droplets, CI, home labs, Tailscale meshes.
MCP server for controlling Android devices and emulators via ADB
A server implementation for handling ADB (Android Debug Bridge) communications using the Message Control Protocol (MCP)
Security scan results for the Adb (npm) MCP server.
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.