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
32821
Answering right now
19715
Up, credentials required
9191
Not answering
3915
Hosted MCP servers - showing 24401–24500 of 32821
ServerStatusHandshakeUptime 30d
dev.ecoa/ecoaAuth required—100%
dev.emailiq/email-intelligenceAuth required—100%
emisarAuth required—100%
Enrichr Web CaptureAuth required—100%
WeltAuth required—2 checks
EurobaseAuth required—100%
EusendAuth required—100%
EverframeAuth required—100%
Exit1 Uptime MonitoringAuth required—100%
Falcon BuilderAuth required—100%
FixterAuth required—100%
FlostepAuth required—2 checks
Forecall Failure KBAuth required—100%
FoxAuthAuth required—3 checks
FrostbyteAuth required—100%
LuminAuth required—100%
getpepprAuth required—2 checks
GlideAuth required—100%
GlitterballAuth required—3 checks
GoodBarberAuth required—100%
GoodeyeAuth required—100%
GreatWaitAuth required—100%
GvnrAuth required—100%
Heard FriendsAuth required—100%
HeardAuth required—100%
HeardAuth required—100%
HeystackAuth required—100%
HumanHoursAuth required—100%
HydrantAuth required—100%
iknowAuth required—100%
ImageStepAuth required—100%
EnforcerAuth required—100%
JamAuth required—3 checks
JobsPipeAuth required—100%
NotesAuth required—100%
knowsmeAuth required—100%
KogniteAuth required—100%
KuuhakuAuth required—100%
LastPingAuth required—100%
LaterbaseAuth required—100%
LaunchFlagAuth required—100%
LayoutlineAuth required—100%
LayrcakeAuth required—100%
LegalizeAuth required—100%
letterportAuth required—1 check
dev.lingo/mainAuth required—100%
Official Logo.dev MCPAuth required—4 checks
LovableAuth required—100%
dev.mailkite/agent-mailAuth required—100%
dev.mailkite/email-agentAuth required—100%
dev.mailkite/inbound-emailAuth required—100%
dev.mailkite/mail-receiveAuth required—100%
dev.mailkite/mail-sendAuth required—100%
dev.mailkite/mailkiteAuth required—100%
MascotlineAuth required—100%
dev.memnode/memnodeAuth required—100%
MeshArcAuth required—100%
dev.metarun/metarunAuth required—100%
ModemAuth required—100%
MonitoAuth required—2 checks
MontonAuth required—2 checks
dev.multimail/mcp-serverAuth required—100%
MyMemoryAuth required—4 checks
My wineAuth required—100%
NameFlowAuth required—2 checks
Native SoilAuth required—100%
AgentBridge — MCP and A2A Service BridgeAuth required—100%
noddle boardAuth required—100%
NoetixAuth required—1 check
OakstackAuth required—100%
OleanderAuth required—100%
OmniDebugLinkAuth required—100%
openstatusAuth required—100%
opsenAuth required—1 check
Orvain UIAuth required—2 checks
OutboxAuth required—100%
PageHubAuth required—100%
Mnemolog MCPAuth required—100%
PageWeaveAuth required—100%
ClipnoteAuth required—100%
past.devAuth required—100%
PasteHTMLAuth required—100%
Patent ConnectorAuth required—100%
Patlas — Patent Prior-Art SearchAuth required—100%
PDF to Markdown (pdf2md.dev)Auth required—100%
pendntAuth required—100%
pepitaAuth required—100%
PethostAuth required—100%
PhoneboxAuth required—100%
PingZen Uptime MonitoringAuth required—89.5%
PlayrunnerAuth required—100%
PloyzAuth required—100%
dev.plyo/plyoAuth required—100%
pncp.devAuth required—3 checks
PostLakeAuth required—100%
PostZenAuth required—100%
QueryScopeAuth required—100%
RampifyAuth required—100%
Ramus AndroidAuth required—100%
Rankd ASOAuth required—100%

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.