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
32897
Answering right now
19757
Up, credentials required
9211
Not answering
3929
Hosted MCP servers - showing 24901–25000 of 32897
ServerStatusHandshakeUptime 30d
AntaeusAuth required—1 check
AntworkAuth required—100%
AO apps hubAuth required—100%
Apdf — PDF Tracking & AnalyticsAuth required—100%
APISignAuth required—100%
Appcircle MCPAuth required—100%
TangoAuth required—100%
AppllamaAuth required—100%
ApplyraAuth required—100%
AppSigma AccountAuth required—2 checks
AppSigma App Store DataAuth required—2 checks
ARCNMAuth required—100%
io.artifacta/mcpAuth required—100%
AstraEye LabsAuth required—100%
AtalayaAuth required—100%
AudD Music RecognitionAuth required—3 checks
io.autoady.www/mcpAuth required—100%
AvatarFactoryAuth required—100%
io.balldontlie/mcpAuth required—100%
BankSyncAuth required—100%
BaserowAuth required—4 checks
BastrioAuth required—1 check
Beamline UIAuth required—100%
Beancount.ioAuth required—100%
BeanHubAuth required—100%
FluentAuth required—4 checks
BenchmarqAuth required—100%
BetterlyticsAuth required—100%
Bitquery MCP ServerAuth required—100%
io.blinkpdf/blinkpdfAuth required—100%
BlocsmithAuth required—100%
BlogSEOAuth required—100%
BlumifyAuth required—100%
BoardBrief AIAuth required—100%
BotSeeAuth required—4 checks
branchlyAuth required—100%
BrandfetchAuth required—100%
Brode.ioAuth required—100%
BrowserlessAuth required—4 checks
BuskaAuth required—100%
BuyerCueAuth required—100%
CallNodeAuth required—3 checks
Camberstack: Google AdsAuth required—100%
io.campaignstack/campaignstackAuth required—100%
CanopyAuth required—100%
CapacitiesAuth required—100%
Carbone MCPAuth required—100%
CarbonGuruAuth required—100%
Casii MCPAuth required—100%
io.catchmetrics.mcp/rum-analyticsAuth required—100%
Cayra Decision IntelligenceAuth required—100%
Certifier MCPAuth required—100%
ChamadeAuth required—100%
Chirp Home AutomationAuth required—100%
Chirp Home AutomationAuth required—100%
Chorus ResearchAuth required—100%
ClipwaveAuth required—100%
ClipwrightAuth required—3 checks
CloudPepperAuth required—100%
CloudresumeAuth required—100%
CodeBAuth required—1 check
CodeQRAuth required—100%
io.consentease/mcp-serverAuth required—100%
ConsentStackAuth required—100%
Consequential AnalyticsAuth required—100%
ContextStreamAuth required—100%
io.converly/converlyAuth required—100%
Conversion ToolsAuth required—100%
Costory FinOps MCPAuth required—100%
io.coupler/remote-mcp-serverAuth required—100%
Control PlaneAuth required—100%
craaftAuth required—100%
CrimeScoreAuth required—100%
CronchAuth required—100%
Cubite LMS: Learning Management SystemAuth required—94.7%
Cypress Cloud MCPAuth required—100%
DadanAuth required—100%
Research MCP ServerAuth required—100%
DatagoatAuth required—88.9%
DataQuollAuth required—100%
datavesselAuth required—100%
daybag.ioAuth required—100%
DaycalAuth required—100%
dazieAuth required—100%
io.dbplanner/db-plannerAuth required—100%
io.decisionrules/mcp-serverAuth required—100%
DecRecAuth required—100%
DemitonAuth required—100%
DevInboxAuth required—100%
Diagrid CatalystAuth required—2 checks
DNS SpyAuth required—4 checks
DoDomainAuth required—100%
dot•requirementsAuth required—100%
Dovri customer support handoffAuth required—100%
DrawdyAuth required—1 check
DueChatAuth required—1 check
Dumpster ControlsAuth required—64.3%
DunjnAuth required—2 checks
EasyWeek BookingAuth required—100%
EasyWeek BusinessAuth 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.