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
33616
Answering right now
20131
Up, credentials required
9459
Not answering
4026
Hosted MCP servers - showing 28601–28700 of 33616
ServerStatusHandshakeUptime 30d
RallyAuth required—100%
SalesTouchAuth required—100%
SAMRUM — Family Personality InsightsAuth required—100%
SanityAuth required—100%
io.scanbimlabs/accAuth required—100%
io.scanbimlabs/navisworksAuth required—100%
io.scanbimlabs/revitAuth required—100%
io.scanbimlabs/scanbimAuth required—100%
io.scanbimlabs/twinmotionAuth required—100%
io.scispot/mcpAuth required—100%
ScopableAuth required—1 check
io.scorecard/mcpAuth required—100%
ScribixAuth required—100%
ScripeAuth required—1 check
Seal SecurityAuth required—100%
io.searchapi/mcpAuth required—100%
SeglyAuth required—100%
SEOforGPTAuth required—100%
sepiaceAuth required—100%
ServiceBox APIsAuth required—100%
ShareoutAuth required—100%
ShipbookAuth required—100%
ShotstackAuth required—100%
Signado MCPAuth required—100%
SigrexAuth required—85.7%
SilotreeAuth required—2 checks
simulis — marketing brainAuth required—100%
SKU.ioAuth required—3 checks
SkycloakAuth required—100%
SlidefastAuth required—88.2%
io.smartroutes/smartroutesAuth required—100%
io.snapcall/mcpAuth required—100%
SnapVisorAuth required—100%
io.snov/snov-mcp-serverAuth required—100%
Sociality.io MCPAuth required—100%
SocialRobot MCP ServerAuth required—100%
SolarScopeAuth required—4 checks
SoundcheckAuth required—100%
Sovrnti MCPAuth required—100%
SparkleTreeAuth required—100%
spArxx.ioAuth required—100%
SphereScoutAuth required—3 checks
StackShieldAuth required—100%
SteerdAuth required—4 checks
StoreRadar: Shopify store databaseAuth required—100%
StorywrightAuth required—100%
StreamRankAuth required—100%
StrunkAuth required—100%
StudioMeyer AcademyAuth required—100%
StudioMeyer CrewAuth required—100%
StudioMeyer CRMAuth required—100%
StudioMeyer GEOAuth required—100%
StudioMeyer MCP SuiteAuth required—100%
MeetMyAgentAuth required—100%
StudioMeyer MemoryAuth required—100%
StudioVector: AI for Mindbody studiosAuth required—3 checks
Stunt DoubleAuth required—100%
io.styleforge/mcpAuth required—100%
SubCenter for TeamsAuth required—100%
SudioAuth required—100%
SummerAuth required—100%
Summit53 Revenue EngineAuth required—100%
SuperBooksAuth required—100%
SupernovaAuth required—100%
SupersimpleAuth required—4 checks
Silicon Valley AtlasAuth required—100%
SynciAuth required—100%
SynionAuth required—100%
Tacyon MCAuth required—100%
io.talebuddy/talebuddyAuth required—100%
TalkfirstAuth required—100%
tavyaAuth required—100%
Temp MailAuth required—94.1%
Tempr MCP ConnectorAuth required—100%
Tempr Gateway AdminAuth required—100%
TendetaAuth required—100%
TessryxAuth required—100%
TestChimpAuth required—100%
Testiny Test ManagementAuth required—100%
TG MarketAuth required—100%
thanks.ioAuth required—3 checks
The Agent ForgeAuth required—100%
The PillarAuth required—100%
Tickwire for MetaTrader 4 and 5Auth required—3 checks
TigerSystemAuth required—4 checks
TightlyAuth required—100%
TightlyAuth required—100%
io.tkllabs.bh.mcp-servers/ethereum-toolkitAuth required—100%
io.tkllabs.bh.mcp-servers/ipfs-toolkitAuth required—100%
io.tkllabs.bh.mcp-servers/navigation-toolkitAuth required—100%
TMTB Marketing AI PlatformAuth required—100%
ToolforestAuth required—100%
toui.io URL ShortenerAuth required—100%
TounifyAuth required—1 check
TradeOnyxAuth required—100%
TradingPalAuth required—100%
TrafficBud SEOAuth required—100%
Trakis site auditsAuth required—100%
Delopt delivery dispatchAuth required—4 checks
Trovest Financial DataAuth 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.