Abhinavyadav Adb MCP Server

@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.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

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:

PointsAdoption-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.

Findings 5

high Sensitive-source and external-sink co-existMTC-FLOW-004

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

high Tool "execute_shell_command" exposes command/code executionMTC-CAP-001

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

high Shell/command execution in server code (dist/adb-utils.js)MTC-SRC-002

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

medium Unconstrained command parameter "command" on "execute_shell_command"MTC-CAP-006

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

low Mutating tool "execute_shell_command" declares no destructiveHintMTC-CAP-005

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

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • dump_ui_hierarchyreads sensitive data
  • execute_shell_commandruns code / shell
  • get_app_memoryreads sensitive data
  • get_logcatreads sensitive data
  • query_sqlitereads sensitive data
  • clear_app_datano sensitive capability
  • clear_logcatno sensitive capability
  • connect_deviceno sensitive capability
  • disconnect_deviceno sensitive capability
  • execute_raw_adbno sensitive capability
Show 32 more tools ↓
  • force_stop_appno sensitive capability
  • forward_portno sensitive capability
  • get_app_usageno sensitive capability
  • get_cpu_usageno sensitive capability
  • get_dbinfono sensitive capability
  • get_device_stateno sensitive capability
  • get_dumpsysno sensitive capability
  • get_propertiesno sensitive capability
  • get_shared_preferencesno sensitive capability
  • grant_permissionno sensitive capability
  • install_appno sensitive capability
  • list_devicesno sensitive capability
  • list_forwardsno sensitive capability
  • list_packagesno sensitive capability
  • list_reversesno sensitive capability
  • list_shared_preferencesno sensitive capability
  • pull_fileno sensitive capability
  • push_fileno sensitive capability
  • reboot_deviceno sensitive capability
  • record_screenno sensitive capability
  • reverse_portno sensitive capability
  • revoke_permissionno sensitive capability
  • root_deviceno sensitive capability
  • send_keyeventno sensitive capability
  • set_mock_locationno sensitive capability
  • start_app_activityno sensitive capability
  • swipe_screenno sensitive capability
  • take_screenshotno sensitive capability
  • tap_screenno sensitive capability
  • type_textno sensitive capability
  • uninstall_appno sensitive capability
  • unroot_deviceno 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

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.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 92/100 5 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.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/abhinavyadav-adb-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/abhinavyadav-adb-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/abhinavyadav-adb-mcp-server"><img src="https://mcptrustchecker.com/registry/abhinavyadav-adb-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/abhinavyadav-adb-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

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 @abhinavyadav/adb-mcp-server --online

Use the free API → How scoring works

Other implementations of Abhinavyadav Adb 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Developer Tools