ToolsMCP
expo-headless-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- abubakr-sanginov (GitHub)
- Prerequisites
- Install expo-headless-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.2.0 · updated
- Official links
Publisher’s description
See and operate Expo / React Native apps: screenshots, taps, typing, auto-testing. No emulator.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.2.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- abubakr-sanginov (GitHub)
- Version observed
- 0.2.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.Abubakr-Sanginov%2Fexpo-headless-mcp/versions/0.2.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “headless”, “screenshots”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “headless”, “screenshots”. Rule browser-automation. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
expo-headless-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.Abubakr-Sanginov/expo-headless-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.