Agent Droid Bridge
PYPI · AGENT-DROID-BRIDGE · SCANNED SEP 21
MCP server giving AI agents eyes and hands inside Android devices via ADB
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 15 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 (MIT).Pass
- Actively maintained (last published 158 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3352 tokens (~239/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_adb_command" 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 15 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 Agent Droid Bridge MCP server?
Agent Droid Bridge runs locally as a PyPI package, launched with uvx agent-droid-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agent-droid-bridge
claude mcp add neverlow512-agent-droid-bridge -- uvx agent-droid-bridge
{
"mcpServers": {
"neverlow512-agent-droid-bridge": {
"command": "uvx",
"args": [
"agent-droid-bridge"
]
}
}
} {
"servers": {
"neverlow512-agent-droid-bridge": {
"command": "uvx",
"args": [
"agent-droid-bridge"
]
}
}
} codex mcp add neverlow512-agent-droid-bridge -- uvx agent-droid-bridge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neverlow512-agent-droid-bridge": {
"type": "local",
"command": [
"uvx",
"agent-droid-bridge"
],
"enabled": true
}
}
} openclaw mcp add neverlow512-agent-droid-bridge --command uvx --arg agent-droid-bridge
mcp_servers:
neverlow512-agent-droid-bridge:
command: "uvx"
args: ["agent-droid-bridge"] {
"McpServers": {
"neverlow512-agent-droid-bridge": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agent-droid-bridge"
]
}
}
} assistant mcp add neverlow512-agent-droid-bridge -t stdio -c uvx -a agent-droid-bridge
{
"mcpServers": {
"neverlow512-agent-droid-bridge": {
"command": "uvx",
"args": [
"agent-droid-bridge"
]
}
}
} 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.
- 21 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.77 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed pypi/agent-droid-bridge@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| 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 →
check_device_capabilities ~344
Device capabilities and hardware profile for the connected Android device. Use 'identity' to establish what device you are working with before starting a session. Use 'security' when a task requires root permissions or you need to confirm privilege level. Use 'hardware' when you need screen dimensions or memory constraints for layout decisions. Use 'all' only when you need a complete profile and latency is not a concern.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| mode | string | yes | 'identity': manufacturer, model, Android version, API level, device type, emulator status, CPU ABI, hardware identifiers, build fingerprint, build tags, kernel version, and SELinux status. 'security'… |
| Name | Type | Req | Description |
|---|---|---|---|
| adb_is_root | – | – | – |
| android_version | – | – | – |
| android_version_codename | – | – | – |
| api_level | – | – | – |
| board | – | – | – |
| build_fingerprint | – | – | – |
| build_tags | – | – | – |
| build_type | – | – | – |
| codename | – | – | – |
| cpu_abi | – | – | – |
| cpu_abi2 | – | – | – |
| cpu_cores | – | – | – |
| device_type | – | – | – |
| dm_verity | – | – | – |
| encryption_state | – | – | – |
| gpu | – | – | – |
| hardware | – | – | – |
| is_emulator | – | – | – |
| kernel_version | – | – | – |
| manufacturer | – | – | – |
| mode | string | yes | – |
| model | – | – | – |
| ro_debuggable | – | – | – |
| ro_secure | – | – | – |
| root_available | – | – | – |
| screen_density | – | – | – |
| screen_resolution | – | – | – |
| selinux_status | – | – | – |
| storage_total_gb | – | – | – |
| supported_abis | – | – | – |
| total_ram_mb | – | – | – |
| usb_config | – | – | – |
| verified_boot_state | – | – | – |
No examples provided.
detect_ui_change ~368
Polls the UI hierarchy after an action and returns when the screen content changes or the timeout is reached. Returns changed status and elapsed time. By default, omits the XML hierarchy for efficiency — set return_hierarchy=True to receive the full hierarchy. For efficient change detection: call snapshot_ui before the action, perform the action, then call detect_ui_change with baseline_token. Only use without baseline_token when you need to wait for a slow transition (loading screens, animations). Do not use to read the current screen state — use get_ui_hierarchy for that.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_token | – | – | Token returned by snapshot_ui, captured before the action. When provided, compares current UI against that snapshot — use this for reliable change detection without loading XML into context. When omi… |
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| return_hierarchy | boolean | – | When False (default), returns only changed and elapsed_seconds — no XML. Set to True to include the full UI hierarchy in the response. Only set True when you need to read element data immediately aft… |
| timeout_seconds | integer | – | Maximum seconds to poll for a UI change. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | – |
| elapsed_seconds | number | yes | – |
| hierarchy | – | – | – |
No examples provided.
execute_adb_command ~216
The output of an ADB command. Parsed safely via shlex and never passed to a system shell.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | ADB command to execute. Parsed safely — no shell injection possible. |
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| use_shell | boolean | – | When True, runs as an Android shell command (adb shell ...). When False, runs as a top-level ADB command (adb devices, adb install, etc.). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_screen_elements ~391
Structured list of UI elements currently visible on the Android screen. Returns elements filtered and shaped by the chosen mode. Prefer 'tappable' for navigation and 'interactive' when you need XPath or bounds for ADB commands. Only use 'all' as a last resort — it returns every node and can be large.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| mode | string | – | Controls which elements are returned and how much detail each carries. 'tappable' (default): only clickable, focusable, or scrollable elements with minimal fields (resource ID, text, content descript… |
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | – |
| mode | string | yes | – |
| total | integer | yes | – |
No examples provided.
get_screen_text ~180
Returns all visible text on the current Android screen, sorted top-to-bottom. Use this when you need to read what is on screen. Does not include coordinates or element info — for tapping or interacting, use `get_screen_elements`.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| Name | Type | Req | Description |
|---|---|---|---|
| plain | string | yes | – |
| total | integer | yes | – |
No examples provided.
get_ui_hierarchy ~212
Returns the current Android screen as an XML UI hierarchy. Use this when you need to locate element coordinates, read text, or find resource IDs to interact with. Do not call this after every action — only call it when you actually need to read screen content. To check if the screen changed after an action, use snapshot_ui before the action and detect_ui_change after.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
launch_app ~169
An Android app launched by its component name (package/activity).
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Android component in 'package/activity' format, e.g. 'com.android.settings/.Settings'. |
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_devices ~29
All Android devices currently visible to ADB, with their serial numbers, connection state, and model names.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
press_key ~186
A key event sent to the Android device using the given keycode integer.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| keycode | integer | yes | Android keycode integer. Common: BACK=4, HOME=3, ENTER=66, RECENTS=187, TAB=61, DEL=67. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
snapshot_ui ~230
Takes a lightweight snapshot of the current UI state and returns a short token. Use this before performing an action (tap, swipe, launch, key press) when you only need to confirm the screen changed afterward — not read its content. Pass the returned token to detect_ui_change as baseline_token. This avoids loading the full XML hierarchy into context unnecessarily. Do not use this when you need to read or interact with screen elements — use get_ui_hierarchy for that.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
swipe_screen ~214
A swipe gesture on the Android screen from (x1,y1) to (x2,y2) over the given duration.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| duration_ms | integer | – | Swipe duration in milliseconds |
| x1 | integer | yes | Start X coordinate |
| x2 | integer | yes | End X coordinate |
| y1 | integer | yes | Start Y coordinate |
| y2 | integer | yes | End Y coordinate |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
take_screenshot ~155
A PNG screenshot of the current Android device screen with width, height, and base64-encoded image data.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| height | integer | yes | – |
| image | string | yes | – |
| width | integer | yes | – |
No examples provided.
tap_screen ~169
A tap gesture at the given pixel coordinates on the Android screen.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| x | integer | yes | X coordinate in screen pixels |
| y | integer | yes | Y coordinate in screen pixels |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
type_text ~162
Text input into the currently focused Android input field. Spaces are encoded automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| device_serial | – | – | Target device serial — pass as device_serial=<serial>. Android device serial (e.g. 'emulator-5554' or '192.168.1.10:5555'). Omit only when a single device is connected. If the tool returns a multi-de… |
| text | string | yes | Text to type into the focused input field. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Agent Droid Bridge MCP server?
Agent Droid Bridge is an MCP server listed in the public MCP registry as io.github.Neverlow512/agent-droid-bridge. MCP server giving AI agents eyes and hands inside Android devices via ADB. This page covers its PyPI package (agent-droid-bridge).
Is the Agent Droid Bridge MCP server safe to use?
Agent Droid Bridge scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Agent Droid Bridge MCP server expose?
Agent Droid Bridge exposes 14 tools: get_ui_hierarchy, tap_screen, swipe_screen, type_text, press_key, and 9 more. Their descriptions and schemas cost roughly 3,025 tokens of context every time the server is loaded.
Is the Agent Droid Bridge MCP server still maintained?
Agent Droid Bridge is still listed as active in the MCP registry. We last reached this channel on 21 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 Agent Droid Bridge MCP server under?
Agent Droid Bridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.