Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Expo Android MCP

NPM · @FNDCHAGAS/EXPO-ANDROID · SCANNED SEP 21

MCP server for Android emulator automation via ADB.

0 this week 88 Trust /100
Trust breakdown (7 categories)

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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to frndchagas/expo-android). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1005 tokens (~59/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 1% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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
Install

How do I install the Expo Android MCP server?

Expo Android MCP runs locally as an npm package, launched with npx -y @fndchagas/expo-android. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @fndchagas/expo-android

# add to Claude Code
claude mcp add frndchagas-expo-android -- npx -y @fndchagas/expo-android
// .cursor/mcp.json
{
  "mcpServers": {
    "frndchagas-expo-android": {
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "frndchagas-expo-android": {
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add frndchagas-expo-android -- npx -y @fndchagas/expo-android
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "frndchagas-expo-android": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fndchagas/expo-android"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add frndchagas-expo-android --command npx --arg -y --arg @fndchagas/expo-android
# ~/.hermes/config.yaml
mcp_servers:
  frndchagas-expo-android:
    command: "npx"
    args: ["-y", "@fndchagas/expo-android"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "frndchagas-expo-android": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@fndchagas/expo-android"
      ]
    }
  }
}
# add to Vellum
assistant mcp add frndchagas-expo-android -t stdio -c npx -a -y @fndchagas/expo-android
// mcp.json
{
  "mcpServers": {
    "frndchagas-expo-android": {
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ]
    }
  }
}
Changelog

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
    • Security disclosure: unverified → fail functional
  • 20 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 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.

  • 12 Sept 26 0
    • Package version: 0.5.0 → 0.5.2 functional
Diagnostics

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 npm/@fndchagas/expo-android@0.5.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo frndchagas/expo-android
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/frndchagas/expo-android/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2579313070
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d6ae2794e61212e75c604bf0d3418a7fdae6fd312461e2ab4952cd0b0877c0c2b47610064687cd377dff33f46acfa899891db989b2d5e68a90303a80a

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~1,005 tokens

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 →

Tool Tokens
assertElement ~128

Assert element presence and state.

NameTypeReqDescription
caseInsensitiveboolean
classstring
contentDescstring
contentDescContainsstring
normalizeWhitespaceboolean
resourceIdstring
resourceIdContainsstring
serialstring
shouldBeCheckedboolean
shouldBeClickableboolean
shouldBeEnabledboolean
shouldExistboolean
textstring
textContainsstring

No output schema declared.

No examples provided.

devices ~15

List connected Android devices and emulators.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doctor ~14

Check adb availability and connected devices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

findElement ~108

Find UI elements by criteria.

NameTypeReqDescription
caseInsensitiveboolean
checkableboolean
classstring
clickableboolean
contentDescstring
contentDescContainsstring
normalizeWhitespaceboolean
resourceIdstring
resourceIdContainsstring
serialstring
textstring
textContainsstring

No output schema declared.

No examples provided.

inputText ~30

Type text into the focused input field.

NameTypeReqDescription
serialstring
textstringyes

No output schema declared.

No examples provided.

inspect ~73

Capture a screenshot and parse UI hierarchy into structured elements.

NameTypeReqDescription
includeElementsboolean
includeScreenshotboolean
maxElementsinteger
onlyInteractiveboolean
screenshotModestring
screenshotPathstring
serialstring

No output schema declared.

No examples provided.

installExpoGo ~88

Download the pinned Expo Go APK and install it on the device via adb install -r. Pass url to install a different official Expo Go release (only github.com/expo/expo-go-releases URLs are accepted).

NameTypeReqDescription
serialstring
urlstringOfficial Expo Go release APK URL override (must be under github.com/expo/expo-go-releases/releases/download/)

No output schema declared.

No examples provided.

keyEvent ~32

Send an Android key event to the device.

NameTypeReqDescription
keyCodestringyes
serialstring

No output schema declared.

No examples provided.

listPackages ~27

List installed package names.

NameTypeReqDescription
filterstring
serialstring

No output schema declared.

No examples provided.

longPress ~44

Press and hold on screen at coordinates.

NameTypeReqDescription
durationnumber
serialstring
xnumberyes
ynumberyes

No output schema declared.

No examples provided.

openApp ~31

Launch an Android app by package name.

NameTypeReqDescription
packageNamestringyes
serialstring

No output schema declared.

No examples provided.

screenshot ~36

Capture a screenshot without UI element parsing.

NameTypeReqDescription
modestring
pathstring
serialstring

No output schema declared.

No examples provided.

setDevice ~33

Override the active device serial for this MCP process. Use "auto" to clear override.

NameTypeReqDescription
serialstring

No output schema declared.

No examples provided.

swipe ~62

Swipe on screen from one coordinate to another.

NameTypeReqDescription
durationnumber
serialstring
x1numberyes
x2numberyes
y1numberyes
y2numberyes

No output schema declared.

No examples provided.

tap ~34

Tap on screen at coordinates.

NameTypeReqDescription
serialstring
xnumberyes
ynumberyes

No output schema declared.

No examples provided.

tapElement ~111

Find an element and tap its center coordinate.

NameTypeReqDescription
caseInsensitiveboolean
classstring
contentDescstring
contentDescContainsstring
indexnumber
normalizeWhitespaceboolean
preferClickableboolean
resourceIdstring
resourceIdContainsstring
serialstring
textstring
textContainsstring

No output schema declared.

No examples provided.

waitForElement ~139

Wait until an element appears or timeout is reached.

NameTypeReqDescription
caseInsensitiveboolean
classstring
contentDescstring
contentDescContainsstring
intervalnumber
normalizeWhitespaceboolean
resourceIdstring
resourceIdContainsstring
serialstring
shouldBeCheckedboolean
shouldBeClickableboolean
shouldBeEnabledboolean
textstring
textContainsstring
timeoutnumber

No output schema declared.

No examples provided.

Common questions

What is the Expo Android MCP server?

Expo Android MCP is listed in the public MCP registry as io.github.frndchagas/expo-android. MCP server for Android emulator automation via ADB. This page covers its npm package (@fndchagas/expo-android).

Is the Expo Android MCP server safe to use?

Expo Android MCP scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Expo Android MCP server expose?

Expo Android MCP exposes 17 tools: devices, doctor, setDevice, inspect, screenshot, and 12 more. Their descriptions and schemas cost roughly 1,005 tokens of context every time the server is loaded.

Is the Expo Android MCP server still maintained?

Expo Android MCP 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 Expo Android MCP server under?

Expo Android MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.