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
32570
Answering right now
19639
Up, credentials required
9082
Not answering
3849
Hosted MCP servers - showing 23401–23500 of 32570
ServerStatusHandshakeUptime 30d
Scout MonitoringAuth required—2 checks
Scraper APIAuth required—100%
com.screenata/complianceAuth required—100%
Screen BrowserAuth required—100%
ScreenMocksAuth required—100%
ScreensDesignAuth required—100%
ScreenshotAgentAuth required—100%
com.screenshotink/mcpAuth required—100%
Screenshot ScoutAuth required—100%
ScreenVerbAuth required—100%
ScreviAuth required—100%
ScribaseAuth required—100%
Scribble — Real Handwritten CardsAuth required—100%
Scribe MailAuth required—100%
ScribeToAnyAuth required—3 checks
ScribeToolsAuth required—100%
ScriptCompilerAuth required—1 check
ScriptGrainAuth required—100%
ScriptHaul APIAuth required—100%
com.scriptivox.www/transcriptionAuth required—100%
ScrollportAuth required—100%
SearcherLiteAuth required—100%
Searcherries: AI Visibility & SEOAuth required—100%
SeasonalEdgeAuth required—1 check
com.seatswiper/bookingAuth required—100%
SeayoraAuth required—100%
Secret Santa OrganizerAuth required—100%
com.securessmtp/securessmtpAuth required—100%
com.see-geo/seegeoAuth required—100%
com.seenpaid/seenpaidAuth required—100%
SeggWatAuth required—100%
SekkeiFlowAuth required—100%
SelfstormingAuth required—100%
SendburgAuth required—3 checks
SenderKitAuth required—100%
sendifaiAuth required—100%
SendPulseAuth required—100%
SendQuoteNow — AI Quote Engine for ContractorsAuth required—100%
SalvoAuth required—4 checks
SendSeven MessagingAuth required—100%
SenPrints Seller ConnectorAuth required—100%
SentientMailAuth required—100%
Sentinel BriefingAuth required—1 check
SEOAsistAuth required—2 checks
SeoclerksAuth required—1 check
SEOFuxx SEO AuditAuth required—100%
SeoGrepAuth required—100%
SeomelyAuth required—100%
SEO PerceptionAuth required—3 checks
SeoPerseoAuth required—100%
SEO Rank FixerAuth required—2 checks
SEOWrenchAuth required—1 check
com.sequentum/mcpAuth required—100%
SE RankingAuth required—100%
SERP Agent SEOAuth required—100%
serpgrab: Google Search and MapsAuth required—2 checks
serpgrab: Google Search and MapsAuth required—1 check
SerpResultAuth required—100%
SerpstatAuth required—100%
Server4AgentAuth required—100%
Session ReplayAuth required—100%
com.sessionario/sessionarioAuth required—100%
SeturosAuth required—100%
DS ManagerAuth required—2 checks
ComponecatAuth required—100%
com.shamra-academia/researchAuth required—100%
ShapelessAIAuth required—100%
ShareSEERAuth required—100%
Sherweb Platform MCP ServerAuth required—100%
ShinobiDataAuth required—100%
ShipdayAuth required—2 checks
com.shippdf/pdfAuth required—100%
PebbleAuth required—100%
ShippoAuth required—100%
ShipvelaAuth required—100%
ShortFastAuth required—1 check
com.shortgenius/shortgeniusAuth required—100%
Shorty AI Video EditorAuth required—1 check
ShotlingoAuth required—100%
SHPBL: Repository Audit & RepairAuth required—100%
Shuffll EngageAuth required—100%
ShurqAuth required—100%
SidecarAuth required—100%
Siftsmith Company SignalsAuth required—100%
SiglataAuth required—100%
SignageSpaceAuth required—100%
SignatureAPIAuth required—100%
Sign CustomiserAuth required—2 checks
SignedAuth required—100%
SignvoyAuth required—100%
Sigil e-signaturesAuth required—1 check
SigParserAuth required—100%
SigwrenAuth required—1 check
Simafri SuiteAuth required—100%
SimpleBackupsAuth required—1 check
Simple FatooraAuth required—4 checks
SimpleFeed MCPAuth required—100%
SimpleFeed MCP Free DiscoveryAuth required—100%
SimplePDFAuth required—4 checks
Simpliers GiveawayAuth 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.