Directory · Remote MCP

Hosted MCP servers

Every remote MCP server we can find, checked continuously with a real MCP handshake over Streamable HTTP. Not a list of what people say they run — a record of what answered.

Endpoints indexed
32654
Answering right now
19685
Up, credentials required
9114
Not answering
3855
Hosted MCP servers - showing 23701–23800 of 32654
ServerStatusHandshakeUptime 30d
SuprSendAuth required—100%
SureSMSAuth required—100%
com.svgator/mcpAuth required—100%
Swamix MCPAuth required—100%
Swath APIAuth required—100%
Sweet Saver FareAuth required—100%
Swifteq MCP Server for ZendeskAuth required—4 checks
SwolvyAuth required—1 check
SydiumAuth required—100%
SynapticRelayAuth required—100%
SynapticRelay freelance boardAuth required—100%
com.syncrosecure/mcp-serverAuth required—100%
SyncSignature Email SignaturesAuth required—100%
SyncSoAuth required—100%
SynentoAuth required—2 checks
TabfleetAuth required—100%
TakeOnAuth required—1 check
Takibi BaseAuth required—100%
TakoCodeAuth required—100%
TaktovkaAuth required—100%
Talent SummonerAuth required—100%
Talkenda MCP ServerAuth required—100%
Tallyfy Workflow AutomationAuth required—100%
TallymeterAuth required—100%
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
com.tamilcalendar/panchangamAuth required—4 checks
TandemAuth required—100%
Talent Augmentation OSAuth required—100%
TapcartAuth required—100%
Tapetide - Indian Stock Market MCPAuth required—100%
TaprootAuth required—100%
TarkaGrid Civic IntelligenceAuth required—100%
TaskholdAuth required—100%
TaskrizAuth required—4 checks
com.taxlocus/taxlocusAuth required—100%
TeamhoodAuth required—4 checks
com.teamo360/teamoAuth required—100%
TeamYouAuth required—100%
TebAuth required—100%
TecoposAuth required—100%
TelebartAuth required—1 check
TTMT – Telegram to MetaTraderAuth required—100%
TeleprompterAuth required—100%
TelerivetAuth required—100%
Telesherpa Ontology PlatformAuth required—100%
TellnodAuth required—2 checks
TellseedAuth required—100%
TemlavoAuth required—2 checks
TempoRevenueAuth required—100%
Tempreon — Personal AI MemoryAuth required—100%
TempusLogAuth required—100%
com.tenantsdb/tenantsdbAuth required—100%
EU Tender GapAuth required—100%
Tenet InvestingAuth required—100%
TenorOpsAuth required—3 checks
PDF ToolkitAuth required—100%
com.tesorio/mcpAuth required—100%
TessamonialsAuth required—2 checks
com.testrigor/mcp-serverAuth required—100%
Text2EventAuth required—100%
Absence-Tiered Authority EnvelopeAuth required—1 check
Agent black-start and islandingAuth required—2 checks
Agent NOTAMs: hazard bulletins for agentsAuth required—2 checks
The capability diet: tool pruning for agentsAuth required—2 checks
Combined Residue CensusAuth required—1 check
Conflicts check and ethical walls for multi-principal agentsAuth required—1 check
Context crossmatch: compatibility typing for context ingestionAuth required—1 check
Effect rewind: compensation registry for agent actionsAuth required—1 check
Error-actionability translation for MCP tool failuresAuth required—2 checks
Event-wake witness for agent triggersAuth required—2 checks
Fleet succession: dead-man's switch for agent fleetsAuth required—1 check

Handshake is the time to complete MCP initialize, measured from our probe, once. Uptime is the share of the last 30 days of checks in which the endpoint responded — an endpoint that answers with an authentication challenge counts as responding, because that is a working server. Glide is in this table on the same terms as everyone else.

What the probe actually does

  • ·Sends MCP `initialize` over Streamable HTTP and records the protocol revision the server negotiates.
  • ·Sends `notifications/initialized`, then `tools/list`, and records the tool count.
  • ·Records a 401 or 403 as “auth required” — a working server, not an outage.
  • ·Records the failure class when nothing answers: timeout, DNS, connection, TLS, HTTP error, or a rejected handshake.
  • ·Runs once an hour per endpoint at most, from one bounded queue, with no retries against a failing host.

Hosted MCP servers, answered

What is a hosted MCP server?

An MCP server someone else runs and you connect to over HTTP, instead of a package you install and run locally over stdio. The registry calls the HTTP kind a remote, and Streamable HTTP is the transport it uses. Everything on this page is that kind; local stdio packages are not listed, because there is no endpoint to check.

How is this different from the other MCP directories?

The others list what publishers declare. This one opens an MCP session against the endpoint and publishes what came back — including when it is ours that fails. Every row says when it was last checked, so you can tell fresh from stale. A directory entry is a claim; a month of handshakes is evidence.

Does “auth required” mean the server is broken?

No — the opposite. It means the endpoint answered and asked for credentials, which is what a correctly secured hosted server should do to an anonymous prober. It counts as responding in the uptime column.

How do I host my own MCP server?

Publish it to the official registry with a remotes entry of type streamable-http and it appears here on the next sync, probed like everything else. If what you need is an MCP server that can open a bank account and a USDC wallet from inside the conversation, that is the Glide connector.