Remote MCP servers list
13,975 hosted MCP servers answer right now. Of the 21,964 listed remote servers called so far, 13,975 completed the MCP handshake with no credentials and 5,521 want an API key or an OAuth sign-in first.
- Working
- 13,975
- Needs sign-in
- 5,521
- Paid per call
- 108
- Not an MCP endpoint
- 1,472
- Unreachable
- 661
- Not checked (legacy SSE)
- 227
- Not checked yet
- 0
0 servers · most-starred first
Nothing here yet — the live check runs hourly in batches. Browse all servers.
How the live check works
For every listed server with a streamable-http remote, Serverdex sends a plain MCP initialize request followed by tools/list — no API key, no OAuth, no account — and records the answer, the round-trip time, the protocol version and the tool definitions (shown on each server's page with an estimated context cost). Servers are re-checked about once a day; the first pass over all listed remotes takes a couple of days.
- Answering: the handshake succeeded without credentials. The tools may still need a key to run.
- Needs sign-in: the endpoint is up but answered 401/403 — a key or an OAuth login comes first.
- Not an MCP endpoint: the URL answers, but not with JSON-RPC — or it is a template / local address that can never be public.
- Unreachable: no answer (network error, timeout, 5xx). A server that is down once is not removed; we count consecutive misses and try again.
- Legacy SSE: servers that only publish the old SSE transport are not called yet.
Own one of these? Claim or list it · see which clients support remote servers in the client compatibility matrix · write the config for your client with the MCP config generator.