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 2001–2100 of 15335
ServerStatusHandshakeUptime 30d
Selis MCPAuth required—100%
Seller AssistantAuth required—100%
SemanticHubAuth required—100%
app.sendar/mcpAuth required—100%
SendcoveAuth required—100%
SendheyAuth required—100%
app.sensefold/sensefoldAuth required—100%
SentinelX MCPAuth required—100%
SEOBoltAuth required—3 checks
seodraftAuth required—100%
SeolyticsAuth required—100%
Sera StudioAuth required—2 checks
SerpelAuth required—100%
SharekiteAuth required—1 check
ShareMyPageAuth required—100%
Shiko Mind MapsAuth required—100%
ShipFunnelsAuth required—2 checks
ShopsBuilder — AI Store BuilderAuth required—100%
Shortik CreatorAuth required—100%
ShortSyncAuth required—100%
Sickle — every mailbox for your agentAuth required—100%
Simple HostAuth required—100%
Simple HostAuth required—100%
Sitejar Web Compliance ScannerAuth required—100%
SkalerAuth required—3 checks
Smacros: smarter macro trackingAuth required—100%
SmartCompanionAuth required—2 checks
SmartGeniusAuth required—100%
smsportal.app SMSAuth required—100%
SnapCountAuth required—100%
Social ExpertAuth required—100%
SocialRainbowAuth required—100%
SocloAuth required—100%
SoKalAuth required—100%
Solk CRMAuth required—100%
SomviaAuth required—100%
SoulStackAuth required—100%
SourceAuth required—4 checks
Space ContextAuth required—100%
SpliteoAuth required—100%
SpoonjoyAuth required—100%
SpreadcastAuth required—100%
StashhhAuth required—100%
StationSignalsAuth required—3 checks
StatuzAuth required—100%
SteadyFeedAuth required—100%
SteepAuth required—100%
Stone ProjectAuth required—100%
Struq MCPAuth required—2 checks
Calligraphy Maker by Studio99Auth required—100%
StudiohausAuth required—100%
SubtlyAuth required—100%
SummitScribeAuth required—3 checks
SuperclockAuth required—3 checks
Typebar (formerly SuperDocs)Auth required—100%
SuperpillsAuth required—100%
SVG LabAuth required—100%
SVG MeAuth required—100%
SvitgridAuth required—1 check
SwapWalletAuth required—100%
SwipekitAuth required—4 checks
SYNCDATEAuth required—2 checks
TabTreeAuth required—100%
TabulariaAuth required—100%
tabAuth required—100%
TahonaAuth required—100%
Tandem CRMAuth required—100%
TasgAuth required—100%
Integrated Work Delivery PlatformAuth required—3 checks
TaskweekAuth required—2 checks
TBitAuth required—100%
TBRP CodexAuth required—100%
TeamwideAuth required—100%
tectonic platesAuth required—100%
TeddyAuth required—100%
TeleBoostAuth required—100%
TelemoonAuth required—3 checks
TelofyAuth required—100%
Tesla Coil Audio DriverAuth required—1 check
TGpipeAuth required—1 check
TGStudioAuth required—3 checks
The AgentcyAuth required—3 checks
Dream TripAuth required—100%
MochiAuth required—2 checks
The Next RaceAuth required—1 check
LinkedIn Content PlannerAuth required—100%
Person EnrichmentAuth required—100%
There ThereAuth required—100%
SAGAAuth required—100%
TheSignupAuth required—100%
TasksAuth required—100%
app.thoughtspot/mcp-serverAuth required—100%
Threads for ClaudeAuth required—100%
ThresholdLinkAuth required—3 checks
ToDevAuth required—100%
TomeboundAuth required—100%
TomeletAuth required—100%
TrackcalrAuth required—3 checks
TracwellAuth required—3 checks
Trade ItAuth 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.