Agent MCP Directory

Expo: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Expo at mcp.expo.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyExpo
Domainexpo.dev
CategoryDeveloper Tools (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Tranco rank6,150 on the list of 4 November 2026
Ora score66, grade C; Ora scanned the domain on 26 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for expo.dev, a vendor-published score)
Company found throughthe vendor's own documentation; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.expo.dev/mcp
How it was foundlisted in the vendor's own documentation; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:01 UTC
Handshake time110 ms over 1 attempt
Documentationdocs.expo.dev

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:56:09Z https://mcp.expo.dev/mcp sent initialize result auth-required (HTTP 401) 139 ms
  • 20:01:48Z https://mcp.expo.dev/mcp sent initialize result auth-required (HTTP 401) 110 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.expo.dev/.well-known/oauth-protected-resource/mcp"
Protected resource metadatamcp.expo.dev
Authorization server metadatamcp.expo.dev
Registration endpointhttps://mcp.expo.dev/oauth/register
Client ID metadata documentssupported

The sign-in route, step by step

  1. Request https://mcp.expo.dev/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.expo.dev/.well-known/oauth-protected-resource/mcp to find the authorization server.
  3. Register a client at the registration endpoint https://mcp.expo.dev/oauth/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Packageeas-cli on npm (page)
Existsyes
Latest version27.4.1
Last publish4 November 2026
Command nameseas
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.