io.github.fullread/deepadb
NPM · DEEPADB · SCANNED SEP 22
Full-featured ADB MCP server — 209 tools across 49 modules, from UI to baseband.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 19701 tokens (~93/item across 210 items; 209 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "adb_shell" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 210 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.fullread/deepadb MCP server?
io.github.fullread/deepadb runs locally as an npm package, launched with npx -y deepadb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · deepadb
claude mcp add fullread-deepadb -- npx -y deepadb
{
"mcpServers": {
"fullread-deepadb": {
"command": "npx",
"args": [
"-y",
"deepadb"
]
}
}
} {
"servers": {
"fullread-deepadb": {
"command": "npx",
"args": [
"-y",
"deepadb"
]
}
}
} codex mcp add fullread-deepadb -- npx -y deepadb
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fullread-deepadb": {
"type": "local",
"command": [
"npx",
"-y",
"deepadb"
],
"enabled": true
}
}
} openclaw mcp add fullread-deepadb --command npx --arg -y --arg deepadb
mcp_servers:
fullread-deepadb:
command: "npx"
args: ["-y", "deepadb"] {
"McpServers": {
"fullread-deepadb": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"deepadb"
]
}
}
} assistant mcp add fullread-deepadb -t stdio -c npx -a -y deepadb
{
"mcpServers": {
"fullread-deepadb": {
"command": "npx",
"args": [
"-y",
"deepadb"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/deepadb@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
adb_uninstall ~60
Uninstall a package from the device
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device serial |
| keepData | boolean | – | Keep app data and cache (-k flag) |
| packageName | string | yes | Package name (e.g., 'com.example.app') |
No output schema declared.
No examples provided.
adb_wait_element ~178
Wait for a UI element to appear or disappear. Polls the UI hierarchy at regular intervals until the condition is met or timeout expires. Useful for waiting after navigation, animations, or async content loading.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | Wait for element to 'appear' (default) or 'disappear' |
| contentDesc | string | – | Match elements with this content-description (partial, case-insensitive) |
| device | string | – | Device serial |
| pollMs | integer | – | Polling interval in ms (200-5000, default 500) |
| resourceId | string | – | Match elements with this resource-id (partial match) |
| text | string | – | Match elements containing this text (case-insensitive) |
| timeoutMs | integer | – | Maximum wait time in ms (1s-60s, default 10s) |
No output schema declared.
No examples provided.
adb_wait_stable ~127
Wait for the UI to stabilize. Polls the UI hierarchy and waits until consecutive dumps produce the same element count and structure. Useful after screen transitions, animations, or content loading before interacting with elements.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device serial |
| pollMs | integer | – | Polling interval in ms (200-5000, default 500) |
| stableCount | integer | – | Number of consecutive identical dumps required (2-10, default 2) |
| timeoutMs | integer | – | Maximum wait time in ms (1s-60s, default 10s) |
No output schema declared.
No examples provided.
adb_wear_datalayer_preflight ~125
Run a read-only Wear OS Data Layer preflight across a connected phone and watch. Checks device roles, Google Play services, Bluetooth, optional app packages, companion association presence, and Data Layer service signals without exposing pairing identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| phoneDevice | string | – | Phone device serial; auto-detected when omitted |
| phonePackage | string | – | Optional companion app package expected on the phone |
| wearDevice | string | – | Wear device serial; auto-detected when omitted |
| wearPackage | string | – | Optional Wear app package expected on the watch |
No output schema declared.
No examples provided.
adb_wifi ~39
Enable or disable WiFi
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device serial |
| enabled | boolean | yes | true = enable WiFi, false = disable |
No output schema declared.
No examples provided.
adb_wifi_firmware ~143
WiFi chipset and firmware identification. Reports WiFi driver version, firmware version, chipset/hardware info, supported bands and standards, interface details, and dumpsys excerpts. BH7 fix: dumpsys truncation now configurable via maxLines. connection state. MAC address is opt-in only (permanent hardware identifier).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device serial |
| includeMac | boolean | – | Include WiFi MAC address (permanent hardware identifier — opt-in only) |
| maxLines | integer | – | Lines of dumpsys output to inspect (50-2000, default 200). Raise for verbose vendor builds where firmware info appears late in dumpsys output. |
No output schema declared.
No examples provided.
adb_workflow_list ~19
List saved workflow files in the workflows directory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adb_workflow_run ~123
Execute a workflow — a JSON-defined sequence of device operations with variable substitution, conditional steps, and loop support. Supported actions: shell, root_shell, install, screenshot, logcat, getprop, sleep. Pass the workflow as a JSON string or provide a saved workflow name.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device serial |
| dryRun | boolean | – | Validate and show execution plan without running |
| variables | object | – | Override workflow variables (merged with defaults) |
| workflow | string | yes | Workflow JSON string, or the name of a saved workflow file |
No output schema declared.
No examples provided.
adb_workflow_validate ~40
Validate a workflow JSON definition without executing it. Reports structural errors and shows the execution plan.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow | string | yes | Workflow JSON string to validate |
No output schema declared.
No examples provided.
What is the io.github.fullread/deepadb MCP server?
io.github.fullread/deepadb is an MCP server listed in the public MCP registry as io.github.fullread/deepadb. Full-featured ADB MCP server, 209 tools across 49 modules, from UI to baseband. This page covers its npm package (deepadb).
Is the io.github.fullread/deepadb MCP server safe to use?
io.github.fullread/deepadb scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.fullread/deepadb MCP server expose?
io.github.fullread/deepadb exposes 209 tools: adb_devices, adb_device_info, adb_getprop, adb_shell, adb_root_shell, and 204 more. Their descriptions and schemas cost roughly 19,689 tokens of context every time the server is loaded.
Is the io.github.fullread/deepadb MCP server still maintained?
io.github.fullread/deepadb is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.fullread/deepadb MCP server under?
io.github.fullread/deepadb declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.