io.github.Abubakr-Sanginov/expo-headless-mcp
NPM · EXPO-HEADLESS-MCP
See and operate Expo / React Native apps: screenshots, taps, typing, auto-testing. No emulator.
Available components
Last scanned (3 hours ago)
Scores higher than 39% of npm servers
Category Testing and QA
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 Security99
- 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 137 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 2 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
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1673 tokens (~185/item across 9 items; 9 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% 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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 69
First indexed and scored.
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 5 Nov 2026 · Analysed npm/expo-headless-mcp@0.2.0
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 137 packages
| Packages resolved | 137 |
|---|---|
| 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 →
auto_test ~142
Automatically exercises the whole app: reloads it several times, fills every TextInput with different data (empty, invalid, valid, very long, special characters), taps every button/switch (scrolling to reach them), dismisses alerts, and reports crashes, console errors/warnings, layout problems (overlaps, clipped text, off-screen elements) and buttons that do nothing, with screenshots of problems. Run it after every change, then fix what it reports and run it again.
| Name | Type | Req | Description |
|---|---|---|---|
| maxStepsPerRound | integer | – | Max taps per round (default 30) |
| rounds | integer | – | How many data rounds / app reloads (default 4) |
No output schema declared.
No examples provided.
click_screen ~102
Taps the screen at (x, y) in screen dp coordinates, or an element by "target" (testID, accessibilityLabel, or visible text). Fires onPress of the nearest pressable, focuses TextInputs, then returns a new screenshot. Use target "alert:<button>" to answer an Alert.
| Name | Type | Req | Description |
|---|---|---|---|
| long | boolean | – | Long press |
| target | string | – | – |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
describe_screen ~51
Text outline of the current screen: every text, input, image and pressable with its position, size and tap-center, plus detected layout problems (overlaps, clipped text, off-screen elements). No image.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
device_list ~84
Lists connected Android emulators / USB phones (adb) and booted iOS Simulators (macOS only) and tells what, if anything, must be done before they can be used (USB debugging, authorization, idb). Read-only: changes nothing. If nothing is connected, tell the user and recommend they check the app themselves. Physical iPhones cannot be driven.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
press_key ~40
Device mode only: presses a hardware key inside Expo Go. Allowed: back (Android only), enter, tab, delete.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
refresh_screen ~172
Bundles the Expo / React Native project (no emulator, phone or browser), renders it headlessly and returns a PNG screenshot of the screen. Call first; call again after editing code (re-bundles and restarts the app). Pass reload=false to just re-capture the current state.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | – | Entry file relative to the project, e.g. App.tsx |
| height | number | – | Screen height in dp (default 844) |
| projectPath | string | – | Expo project directory (default: EXPO_PROJECT env or server cwd) |
| reload | boolean | – | Re-bundle and restart the app (default true) |
| scale | number | – | PNG pixel scale (default 1.5) |
| width | number | – | Screen width in dp (default 390) |
No output schema declared.
No examples provided.
scroll_screen ~73
Scrolls the ScrollView/FlatList under (x, y) by dy (vertical) or dx (horizontal) dp; positive dy scrolls down. Returns a new screenshot.
| Name | Type | Req | Description |
|---|---|---|---|
| dx | number | – | – |
| dy | number | – | – |
| x | number | yes | – |
| y | number | yes | – |
No output schema declared.
No examples provided.
type_text ~117
Types text into a TextInput (replacing its value unless append=true) so forms and validation can be tested. Locate the field by "target" (testID, placeholder, accessibilityLabel, current value), by x/y, or omit both to use the focused field. Returns a new screenshot.
| Name | Type | Req | Description |
|---|---|---|---|
| append | boolean | – | – |
| submit | boolean | – | Also fire onSubmitEditing (Enter) |
| target | string | – | – |
| text | string | yes | – |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
use_target ~178
Chooses where the app is tested: "headless" (default, built-in renderer) or "device" (Expo Go on an Android emulator / USB phone via adb, or a booted iOS Simulator on macOS). Selecting "device" first asks the user for consent to control a physical phone, to install Expo Go if missing, and to replace an Expo Go whose SDK does not match the project; then starts the Expo dev server and opens the app. If the user declines, nothing is changed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | array | – | Consent keys the user approved in chat (only when a previous call asked you to relay a question) |
| projectPath | string | – | – |
| serial | string | – | adb serial or iOS simulator UDID from device_list (needed if several targets are ready) |
| target | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.Abubakr-Sanginov/expo-headless-mcp server?
io.github.Abubakr-Sanginov/expo-headless-mcp runs locally as an npm package, launched with npx -y expo-headless-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · expo-headless-mcp
claude mcp add abubakr-sanginov-expo-headless-mcp -- npx -y expo-headless-mcp
What is the io.github.Abubakr-Sanginov/expo-headless-mcp server?
io.github.Abubakr-Sanginov/expo-headless-mcp is listed in the public MCP registry as io.github.Abubakr-Sanginov/expo-headless-mcp. See and operate Expo / React Native apps: screenshots, taps, typing, auto-testing. No emulator. This page covers its npm package (expo-headless-mcp).
Is the io.github.Abubakr-Sanginov/expo-headless-mcp server safe to use?
io.github.Abubakr-Sanginov/expo-headless-mcp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.Abubakr-Sanginov/expo-headless-mcp server expose?
io.github.Abubakr-Sanginov/expo-headless-mcp exposes 9 tools: refresh_screen, click_screen, type_text, scroll_screen, describe_screen, and 4 more. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.
Is the io.github.Abubakr-Sanginov/expo-headless-mcp server still maintained?
io.github.Abubakr-Sanginov/expo-headless-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.Abubakr-Sanginov/expo-headless-mcp server under?
io.github.Abubakr-Sanginov/expo-headless-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.