# deepadb DeepADB — full-featured Android Debug Bridge MCP server. 209 tools across 49 modules for device inspection from UI to baseband. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.1.4 - **Author:** io.github.fullread - **License:** Apache-2.0 - **npm:** deepadb - **Source:** https://github.com/fullread/DeepADB - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-01T05:02:17.226Z - **Version scanned:** 1.1.4 - **CVEs:** none found by OSV at scan time ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `adb_a11y_audit` — Run an automated accessibility audit on the current screen. Checks for: missing labels on interactive elements, undersized touch targets (<48dp), images without - `adb_a11y_touch_targets` — List all interactive elements with their touch target dimensions in dp. Highlights elements below the 48dp minimum. Useful for quickly identifying cramped UI la - `adb_a11y_tree` — Dump the accessibility-focused view of the UI hierarchy. Shows only elements relevant to screen readers: their roles, labels, states, and navigation order. Filt - `adb_app_route_context` — Show the effective Android routing context for one installed app by correlating its UID with ip rules, route tables, network policy, VPN, and default-network st - `adb_shannon_session` — Preflight a Samsung Shannon/Exynos modem session by checking the chipset, root access, known AT ports, and a benign AT handshake together. Optionally sends ATI - `adb_at_detect` — Auto-detect the modem AT command device node. Identifies the chipset family (Shannon, Qualcomm, MediaTek, Unisoc) and probes known device node paths. Requires r - `adb_at_send` — Send a single AT command to the modem and capture the response. Requires root. Use adb_at_detect to find the correct port, or specify it manually. - `adb_at_batch` — Send multiple AT commands sequentially and capture all responses. Useful for running a diagnostic sequence. Requires root. - `adb_at_probe` — Run a standard AT diagnostic probe: modem identification, signal quality, network registration, SIM status, and supported bands. Requires root. - `adb_at_cross_validate` — Cross-validate baseband firmware by comparing AT command responses (direct modem interrogation) against Android system properties (getprop). Discrepancies may i - `adb_baseband_info` — Get comprehensive modem/baseband identification: firmware version, RIL implementation, chipset, IMEI, SIM state, and radio capabilities. - `adb_cell_identity` — Extract detailed cell identity information: Cell ID (CID), TAC/LAC, EARFCN/ARFCN, Physical Cell ID (PCI), PLMN, and network type. Parses structured data from du - `adb_signal_detail` — Get detailed signal strength measurements: RSRP, RSRQ, SINR, RSSI, timing advance, and signal bars. Provides raw radio measurements for signal analysis and anom - `adb_neighboring_cells` — List all visible cells beyond the serving cell: neighboring LTE/5G/WCDMA/GSM cells with their identities and signal strengths. Useful for cellular network surve - `adb_carrier_config` — Dump carrier configuration values. Useful for verifying carrier settings, detecting configuration anomalies, and inspecting APN configurations. - `adb_modem_logs` — Capture modem/baseband-related logs from multiple sources: RIL (Radio Interface Layer) logcat, telephony framework logs, and kernel modem messages via dmesg (ro - `adb_gradle` — Run a Gradle task in an Android project directory - `adb_build_and_install` — Build a debug APK and install it on the connected device (convenience wrapper) - `adb_ci_wait_boot` — Wait for a device or emulator to fully boot. Polls sys.boot_completed and waits for the launcher to be ready. Essential for CI pipelines. - `adb_ci_device_ready` — Comprehensive CI readiness check. Verifies: device online, booted, package manager ready, screen unlocked, network available. Returns structured pass/fail resul - `adb_ci_run_tests` — Run Android instrumented tests (androidTest) via `am instrument` and capture results. Returns structured pass/fail output. - `adb_airplane_mode` — Toggle airplane mode on/off. Useful for resetting cellular registration during radio testing. - `adb_wifi` — Enable or disable WiFi - `adb_mobile_data` — Enable or disable mobile data - `adb_location` — Enable or disable location services - `adb_screen` — Control screen state: wake, sleep, toggle, lock, or unlock. Lock and unlock verify actual keyguard state via dumpsys window. Unlock uses wm dismiss-keyguard (wo - `adb_airplane_cycle` — Cycle airplane mode on then off after a delay. Forces cellular re-registration — useful for radio diagnostics and network testing. - `adb_settings_get` — Read an Android settings value from any namespace (system, secure, global) - `adb_settings_put` — Write an Android settings value to any namespace (system, secure, global) - `adb_reboot` — Reboot the device. Supports normal, recovery, and bootloader modes. - `adb_sqlite_inspect` — Safely inspect a Room or SQLite database inside an installed app. Lists package databases, shows schema, or executes one validated read-only query. Requires a d - `adb_farm_run` — Run tests on Firebase Test Lab. Uploads an APK and test APK, executes instrumented tests across specified device models and API levels. Requires gcloud CLI auth - `adb_farm_results` — Retrieve results from the most recent Firebase Test Lab run, or a specific test matrix ID. Shows pass/fail status, device results, and links to logs and artifac - `adb_farm_matrix` — List available device models and API levels on Firebase Test Lab. Use to plan test matrices. - `adb_profile_detect` — Auto-detect and build a device profile from the connected device. Captures hardware identification, chipset family, modem info, root status, and matches against - `adb_profile_save` — Save a device profile to the profiles library. Use after adb_profile_detect to persist the profile, or create a manual profile with custom quirks and notes. - `adb_profile_list` — List all device profiles: built-in library entries and user-saved profiles. - `adb_devices` — List all connected Android devices with their state, model, and product info - `adb_device_info` — Get detailed properties for a connected device (model, OS version, build, etc.) - `adb_getprop` — Get a specific Android system property, or all properties if no key given ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"deepadb\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"deepadb\"\n ]\n }\n }\n}" ``` ## Blast radius Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine. - Floor 30, ceiling 54 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/deepadb - Install plan: https://forgeregistry.com/api/v1/packages/deepadb/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/deepadb - HTML page: https://forgeregistry.com/registry/deepadb - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.