Remote MCP · Endpoint

Expo MCP server

No. Expo answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_expo

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/expo-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
51 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
Listing
From the official MCP registry (active).
Recent checks of Expo
CheckedResultHandshake
1 day agoHandshake completed51 ms
3 days agoHandshake completed91 ms
5 days agoHandshake completed591 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed49 ms
9 days agoHandshake completed64 ms
12 days agoHandshake completed41 ms
13 days agoHandshake completed96 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed44 ms
18 days agoHandshake completed98 ms
19 days agoHandshake completed210 ms
20 days agoHandshake completed180 ms
20 days agoHandshake completed132 ms
21 days agoHandshake completed101 ms
23 days agoHandshake completed125 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Expo and makes no claim about it beyond what these checks measured.