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
49223
Answering right now
27485
Up, credentials required
15335
Not answering
6403
Hosted MCP servers - showing 201–300 of 15335
ServerStatusHandshakeUptime 30d
BunzeeAuth required—100%
BusinessLoanBroker.aiAuth required—3 checks
ai.butlerbrain/mcpAuth required—100%
buzzaboutAuth required—3 checks
BuzzbergAuth required—100%
BuzzmarkAuth required—100%
BuzzSearchAuth required—100%
BynorAuth required—100%
ByteRay AIAuth required—100%
CaimeraAuth required—100%
CalafAuth required—100%
CalendarMCPAuth required—100%
CalfeedAuth required—100%
CalvenAuth required—100%
Campaign MagicAuth required—100%
CanvoraAuth required—100%
Cardboard AIAuth required—100%
CareerCornerAuth required—100%
CatchMyCallAuth required—100%
CattalogAuth required—1 check
CauloAuth required—100%
CayblAuth required—100%
ai.cdbx/mcp-serverAuth required—100%
Celesto Cloud ComputersAuth required—100%
Central CityAuth required—100%
CertScore.aiAuth required—100%
Chatley AIAuth required—100%
ChatterLabAuth required—100%
Chat ThingAuth required—100%
Alchemist Cloud TicketsAuth required—100%
ChippAuth required—100%
Chipp Actions and componentsAuth required—100%
Chipp Analytics and evalsAuth required—100%
Chipp Agent settingsAuth required—100%
Chipp AgentsAuth required—100%
Chipp Billing and monetizationAuth required—100%
Chipp ChannelsAuth required—100%
Chipp CoreAuth required—100%
Chipp Data operationsAuth required—100%
Chipp IntegrationsAuth required—100%
Chipp KnowledgeAuth required—100%
Chipp Legacy codeAuth required—100%
Chipp Memory and schedulesAuth required—100%
Chipp NewslettersAuth required—100%
Chipp ObservabilityAuth required—100%
Chipp PacksAuth required—100%
Chipp Software factory projectsAuth required—100%
Chipp ReleasesAuth required—100%
Chipp TagsAuth required—100%
Chipp TicketsAuth required—100%
CirclebackAuth required—100%
Cirra AI Salesforce Admin MCP ServerAuth required—100%
Clarid HMDA ValidatorAuth required—100%
ClarityTrackAuth required—100%
CleanvoiceAuth required—100%
ClearkeepAuth required—2 checks
CleveAuth required—100%
CleveraAuth required—100%
ClevraAuth required—100%
ClipFluxAuth required—100%
Clip Studio MCPAuth required—100%
CloneKitAuth required—100%
CloudCraneAuth required—100%
CloudCraneAuth required—100%
CloudXray AI FinOps DirectoryAuth required—100%
Cluvi AIAuth required—100%
CNAPS.ai MCP ServerAuth required—100%
cnpj.aiAuth required—100%
CoblAuth required—2 checks
CocuyoAuth required—100%
CodeGeneAuth required—1 check
CofoundAuth required—100%
CognitoLabs.aiAuth required—3 checks
ai.colaunched/colaunchedAuth required—100%
ColorCraftAuth required—3 checks
CommerceAIAuth required—100%
CommercializerAuth required—100%
CommitLayerAuth required—2 checks
CommSyncAuth required—100%
CompellingAuth required—100%
compiAuth required—100%
Condux error monitoringAuth required—100%
ConnectMachineAuth required—100%
ConnieAuth required—100%
Constellation CreditAuth required—100%
ContentMaschineAuth required—100%
Airflow DAG DoctorAuth required—3 checks
Data Quality GateAuth required—100%
Deployment FixerAuth required—3 checks
ContentSweep Supplier FeedsAuth required—100%
ContexelAuth required—100%
ContextGateAuth required—100%
Contio MeetingOSAuth required—100%
ConveoAuth required—100%
Conyr Solana IntelligenceAuth required—2 checks
CookiyAuth required—100%
CooperBuildAuth required—100%
CordexAuth required—100%
CorisAuth required—1 check
Coris (EU)Auth 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.