Remote servers
Every entry here carries checkable remote evidence. Entries we cannot establish are not on this page; coverage and unknowns are printed above.
Of 10,162 entries, 780 carry remote evidence, 4,387 carry local evidence (an install command that runs on your machine) and 4,938 cannot be determined. Registry snapshot 2026-10-20; what we cannot establish is not labelled and not guessed. The evidence is the record itself: we do not probe every endpoint, so no "online" badge is shown.
How we label these entries
Each card shows where the entry came from, the repository path where we can establish one, when we last saw it, and the public star count GitHub reports. A field marked not held means our database holds no value for that entry - it is not a statement about the project and not a verdict. We do not label repositories with pricing, interface language or registration status: these are code repositories, not product sites, so we do not measure those facts and will not guess them. This directory only lists entries that carry a star count (5,726 of 10,162 site-wide entries, 56.3%); where there is no star count, nothing is shown - we do not print a zero or a placeholder. Links are checked on a rolling basis · last sweep 2026-11-14.
Showing 1–48 of 780
Common questions about remote servers
How is "remote" decided here?
Three kinds of evidence, strongest first: (1) the official MCP Registry records a remote endpoint for the repository (833 entries); (2) the entry URL is itself an endpoint such as /mcp or /sse (4); (3) the install command hands you an endpoint URL (0). Hover the badge to see the endpoint we verified; every Registry record can be looked up by name through the registry API. Note that the evidence is the record itself: we do not probe every endpoint, so no "online" badge is shown.
Why are most entries not on this page?
Because we cannot establish it: 4,938 of 10,162 entries have neither endpoint evidence nor an install command - all we hold is a repository address and one line of description. We write unknown rather than guess from a name or a README (952 READMEs mention streamable, mostly as a protocol note).
Is "remote servers" a 14th top category?
No. The 13 top categories are fields; remote is a parallel filter, and one entry can be both. Filing it as a category would double-count entries and make the 13 category totals disagree with the catalogue total, so it stands alone and its number equals the cards on this page.
What does "one URL to connect" mean?
You give the client an endpoint URL and a transport and nothing else. For example Claude Code: claude mcp add --transport http <name> <endpoint URL>; Cursor, VS Code and Codex take a url field in their config files. The /clients/ page links each client's own documentation.
How often is this updated?
Entries come from the daily harvest; remote evidence is recomputed on every rebuild (Registry snapshot 2026-10-20).
What we actually check
Every card here carries checkable remote evidence: a remote endpoint recorded in the official MCP Registry, an entry URL that is itself an endpoint such as /mcp, or an install command that hands you an endpoint URL. Entries without evidence are not on this page; coverage and the number we cannot determine are printed in the stat bar and the FAQ. A name containing "remote" or a README mentioning streamable is not evidence. The evidence is the record itself; we do not probe every endpoint, so there is no "online" badge.
Found something missing or wrong?
Tell us and we re-check it against the source before it changes.
Contact us ↗