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
| Server | Status | Handshake | Uptime 30d |
|---|---|---|---|
| Bunzee | Auth required | — | 100% |
| BusinessLoanBroker.ai | Auth required | — | 3 checks |
| ai.butlerbrain/mcp | Auth required | — | 100% |
| buzzabout | Auth required | — | 3 checks |
| Buzzberg | Auth required | — | 100% |
| Buzzmark | Auth required | — | 100% |
| BuzzSearch | Auth required | — | 100% |
| Bynor | Auth required | — | 100% |
| ByteRay AI | Auth required | — | 100% |
| Caimera | Auth required | — | 100% |
| Calaf | Auth required | — | 100% |
| CalendarMCP | Auth required | — | 100% |
| Calfeed | Auth required | — | 100% |
| Calven | Auth required | — | 100% |
| Campaign Magic | Auth required | — | 100% |
| Canvora | Auth required | — | 100% |
| Cardboard AI | Auth required | — | 100% |
| CareerCorner | Auth required | — | 100% |
| CatchMyCall | Auth required | — | 100% |
| Cattalog | Auth required | — | 1 check |
| Caulo | Auth required | — | 100% |
| Caybl | Auth required | — | 100% |
| ai.cdbx/mcp-server | Auth required | — | 100% |
| Celesto Cloud Computers | Auth required | — | 100% |
| Central City | Auth required | — | 100% |
| CertScore.ai | Auth required | — | 100% |
| Chatley AI | Auth required | — | 100% |
| ChatterLab | Auth required | — | 100% |
| Chat Thing | Auth required | — | 100% |
| Alchemist Cloud Tickets | Auth required | — | 100% |
| Chipp | Auth required | — | 100% |
| Chipp Actions and components | Auth required | — | 100% |
| Chipp Analytics and evals | Auth required | — | 100% |
| Chipp Agent settings | Auth required | — | 100% |
| Chipp Agents | Auth required | — | 100% |
| Chipp Billing and monetization | Auth required | — | 100% |
| Chipp Channels | Auth required | — | 100% |
| Chipp Core | Auth required | — | 100% |
| Chipp Data operations | Auth required | — | 100% |
| Chipp Integrations | Auth required | — | 100% |
| Chipp Knowledge | Auth required | — | 100% |
| Chipp Legacy code | Auth required | — | 100% |
| Chipp Memory and schedules | Auth required | — | 100% |
| Chipp Newsletters | Auth required | — | 100% |
| Chipp Observability | Auth required | — | 100% |
| Chipp Packs | Auth required | — | 100% |
| Chipp Software factory projects | Auth required | — | 100% |
| Chipp Releases | Auth required | — | 100% |
| Chipp Tags | Auth required | — | 100% |
| Chipp Tickets | Auth required | — | 100% |
| Circleback | Auth required | — | 100% |
| Cirra AI Salesforce Admin MCP Server | Auth required | — | 100% |
| Clarid HMDA Validator | Auth required | — | 100% |
| ClarityTrack | Auth required | — | 100% |
| Cleanvoice | Auth required | — | 100% |
| Clearkeep | Auth required | — | 2 checks |
| Cleve | Auth required | — | 100% |
| Clevera | Auth required | — | 100% |
| Clevra | Auth required | — | 100% |
| ClipFlux | Auth required | — | 100% |
| Clip Studio MCP | Auth required | — | 100% |
| CloneKit | Auth required | — | 100% |
| CloudCrane | Auth required | — | 100% |
| CloudCrane | Auth required | — | 100% |
| CloudXray AI FinOps Directory | Auth required | — | 100% |
| Cluvi AI | Auth required | — | 100% |
| CNAPS.ai MCP Server | Auth required | — | 100% |
| cnpj.ai | Auth required | — | 100% |
| Cobl | Auth required | — | 2 checks |
| Cocuyo | Auth required | — | 100% |
| CodeGene | Auth required | — | 1 check |
| Cofound | Auth required | — | 100% |
| CognitoLabs.ai | Auth required | — | 3 checks |
| ai.colaunched/colaunched | Auth required | — | 100% |
| ColorCraft | Auth required | — | 3 checks |
| CommerceAI | Auth required | — | 100% |
| Commercializer | Auth required | — | 100% |
| CommitLayer | Auth required | — | 2 checks |
| CommSync | Auth required | — | 100% |
| Compelling | Auth required | — | 100% |
| compi | Auth required | — | 100% |
| Condux error monitoring | Auth required | — | 100% |
| ConnectMachine | Auth required | — | 100% |
| Connie | Auth required | — | 100% |
| Constellation Credit | Auth required | — | 100% |
| ContentMaschine | Auth required | — | 100% |
| Airflow DAG Doctor | Auth required | — | 3 checks |
| Data Quality Gate | Auth required | — | 100% |
| Deployment Fixer | Auth required | — | 3 checks |
| ContentSweep Supplier Feeds | Auth required | — | 100% |
| Contexel | Auth required | — | 100% |
| ContextGate | Auth required | — | 100% |
| Contio MeetingOS | Auth required | — | 100% |
| Conveo | Auth required | — | 100% |
| Conyr Solana Intelligence | Auth required | — | 2 checks |
| Cookiy | Auth required | — | 100% |
| CooperBuild | Auth required | — | 100% |
| Cordex | Auth required | — | 100% |
| Coris | Auth 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.