io.github.martingeidobler/android
NPM · ANDROID-MCP-SERVER · SCANNED SEP 25
Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.33.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 125 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 190 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1256 tokens (~59/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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.martingeidobler/android MCP server?
io.github.martingeidobler/android runs locally as an npm package, launched with npx -y android-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · android-mcp-server
claude mcp add martingeidobler-android -- npx -y android-mcp-server
{
"mcpServers": {
"martingeidobler-android": {
"command": "npx",
"args": [
"-y",
"android-mcp-server"
]
}
}
} {
"servers": {
"martingeidobler-android": {
"command": "npx",
"args": [
"-y",
"android-mcp-server"
]
}
}
} codex mcp add martingeidobler-android -- npx -y android-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"martingeidobler-android": {
"type": "local",
"command": [
"npx",
"-y",
"android-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add martingeidobler-android --command npx --arg -y --arg android-mcp-server
mcp_servers:
martingeidobler-android:
command: "npx"
args: ["-y", "android-mcp-server"] {
"McpServers": {
"martingeidobler-android": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"android-mcp-server"
]
}
}
} assistant mcp add martingeidobler-android -t stdio -c npx -a -y android-mcp-server
{
"mcpServers": {
"martingeidobler-android": {
"command": "npx",
"args": [
"-y",
"android-mcp-server"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 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.
- 19 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
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 25 Sept 2026 · Analysed npm/android-mcp-server@1.2.1
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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 125 packages
| Packages resolved | 125 |
|---|---|
| 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_shell ~46
Run an arbitrary ADB shell command
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command to execute on the device |
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
clear_logs ~42
Clear the logcat buffer. Call this before reproducing a bug to get clean logs.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
get_current_activity ~33
Get the currently displayed app and activity
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
get_device_info ~45
Get device details: model, manufacturer, Android version, API level, screen size, and DPI.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
get_logs ~149
Get device logcat output. Use to find crashes, exceptions, and errors after reproducing a bug.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| level | string | – | Minimum log level: V(erbose), D(ebug), I(nfo), W(arn), E(rror), F(atal) |
| lines | number | – | Number of recent log lines to return (default 200) |
| package_name | string | – | Filter logs by app package name (e.g., com.example.app) |
| since | string | – | Show logs since timestamp (e.g., '2024-01-15 10:30:00.000') |
No output schema declared.
No examples provided.
get_ui_tree ~58
Get the UI element hierarchy of the current screen. Returns interactive elements with their bounds, text, resource IDs, and state. Use this to find elements before tapping.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
install_apk ~47
Install an APK file on the device
| Name | Type | Req | Description |
|---|---|---|---|
| apk_path | string | yes | Local path to the APK file |
| device_id | string | – | Device ID (optional if only one device) |
No output schema declared.
No examples provided.
launch_app ~67
Launch an Android app by package name
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Activity to launch (optional - launches default if omitted) |
| device_id | string | – | Device ID (optional if only one device) |
| package_name | string | yes | App package name (e.g., com.android.settings) |
No output schema declared.
No examples provided.
list_avds ~15
List available Android Virtual Devices
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_devices ~16
List connected Android devices and emulators
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
press_key ~40
Press a hardware/software key
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| key | string | yes | Key to press |
No output schema declared.
No examples provided.
pull_file ~74
Pull a file from the Android device to the local filesystem.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| local_path | string | yes | Local path to save the file to |
| remote_path | string | yes | Path on the device (e.g., /sdcard/somefile.txt) |
No output schema declared.
No examples provided.
screenshot ~64
Take a screenshot of the Android device. Returns the image for visual analysis. Optionally saves to a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| save_path | string | – | Local file path to save the screenshot PNG (optional) |
No output schema declared.
No examples provided.
scroll_to_element ~76
Scroll down repeatedly until an element matching the given criteria is visible
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | How to find the element |
| device_id | string | – | Device ID (optional if only one device) |
| max_scrolls | number | – | Maximum scroll attempts (default 10) |
| value | string | yes | Value to match |
No output schema declared.
No examples provided.
start_emulator ~48
Start an Android emulator. Waits up to 60s for it to come online.
| Name | Type | Req | Description |
|---|---|---|---|
| avd_name | string | yes | Name of the AVD to start (from list_avds) |
No output schema declared.
No examples provided.
swipe ~91
Perform a swipe gesture on the screen
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| duration_ms | number | – | Swipe duration in ms (default 300) |
| end_x | number | yes | End X coordinate |
| end_y | number | yes | End Y coordinate |
| start_x | number | yes | Start X coordinate |
| start_y | number | yes | Start Y coordinate |
No output schema declared.
No examples provided.
tap ~47
Tap at specific screen coordinates
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| x | number | yes | X coordinate |
| y | number | yes | Y coordinate |
No output schema declared.
No examples provided.
tap_and_wait ~102
Tap element then wait for UI to settle and return the new UI tree. Combines tap + wait + get_ui_tree into a single fast operation.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | How to find the element to tap |
| device_id | string | – | Device ID (optional if only one device) |
| value | string | yes | Value to match |
| wait_ms | number | – | Time to wait for UI to settle after tap (default 1000ms) |
No output schema declared.
No examples provided.
tap_element ~73
Tap a UI element by its resource-id, text, or content-desc. Finds the element in the UI tree and taps its center.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | How to find the element |
| device_id | string | – | Device ID (optional if only one device) |
| value | string | yes | Value to match |
No output schema declared.
No examples provided.
type_text ~43
Type text into the currently focused input field
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID (optional if only one device) |
| text | string | yes | Text to type |
No output schema declared.
No examples provided.
wait_for_element ~80
Wait for a UI element to appear on screen. Polls every 500ms.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | How to find the element |
| device_id | string | – | Device ID (optional if only one device) |
| timeout_ms | number | – | Timeout in ms (default 10000) |
| value | string | yes | Value to match |
No output schema declared.
No examples provided.
What is the io.github.martingeidobler/android MCP server?
io.github.martingeidobler/android is an MCP server listed in the public MCP registry as io.github.martingeidobler/android. Control Android devices and emulators via ADB, screenshots, UI automation, and logcat. This page covers its npm package (android-mcp-server).
Is the io.github.martingeidobler/android MCP server safe to use?
io.github.martingeidobler/android scores 76 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 25 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.martingeidobler/android MCP server expose?
io.github.martingeidobler/android exposes 21 tools: list_devices, list_avds, start_emulator, screenshot, get_ui_tree, and 16 more. Their descriptions and schemas cost roughly 1,256 tokens of context every time the server is loaded.
Is the io.github.martingeidobler/android MCP server still maintained?
io.github.martingeidobler/android is still listed as active in the MCP registry. We last reached this channel on 25 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.martingeidobler/android MCP server under?
io.github.martingeidobler/android declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.