← all repositories
punkpeye/awesome-remote-mcp-servers

The MCP list that only admits servers that answer the handshake

A curated directory of MCP servers that live at a URL instead of in your process tree, with each entry admitted only after its endpoint answers an MCP initialize handshake.

awesome-remote-mcp-servers
Too new to rank. Velocity needs a few days of history.
not enough history yet
star history

What it does This is an awesome-style directory of remote MCP servers — endpoints someone else operates, reached over Streamable HTTP, authenticated with OAuth or an API key. The pitch is “no install, no runtime, no local process”: distribution collapses from npm/PyPI/Docker/binary to a URL, and updates ship from the provider instead of from you. It’s the companion to the same maintainer’s awesome-mcp-servers, which covers servers you run yourself. Coverage spans dozens of categories, from aggregators and browser automation to agriculture, legal, and version control.

The interesting bit Curation here has a gate: an entry only makes the list after its endpoint answers an MCP initialize handshake. That’s a low bar, but it’s a real one — most awesome lists test nothing. Each entry also carries an auth marker (🔓 anonymous, 🔑 API key, 🔐 OAuth), so you know the friction before you click.

Key highlights

  • Local vs. remote, distilled into one table: URL distribution, Streamable HTTP transport (or legacy SSE), provider-side upgrades.
  • Auth legend tells you at a glance whether connecting is anonymous, token-based, or a browser OAuth dance.
  • Some entries carry Glama connector badges with independent scores for tool definition quality and endpoint health.
  • Companion list (awesome-mcp-servers) for the self-hosted crowd.

Caveats

  • It’s a list, not software — the entire value is curation, and the README doesn’t say whether the handshake check is one-time or continuously re-verified.
  • Commercial fingerprints are visible: a ray.run promo sits at the top and Glama badges run throughout, so the directory doubles as a funnel.
  • The aggregator section leans hard into pay-per-call crypto rails (x402, USDC on Base) — a taste rather than a flaw, but it colors the catalog.

Verdict If you’re wiring an MCP client to hosted endpoints and want a verified starting index, this saves you a lot of URL hunting. If you self-host, or bristle at third parties holding your OAuth tokens, the companion list — or no list — is your lane.

Frequently asked

What is punkpeye/awesome-remote-mcp-servers?
A curated directory of MCP servers that live at a URL instead of in your process tree, with each entry admitted only after its endpoint answers an MCP initialize handshake.
Is awesome-remote-mcp-servers open source?
Yes — punkpeye/awesome-remote-mcp-servers is open source, released under the MIT license.
How popular is awesome-remote-mcp-servers?
punkpeye/awesome-remote-mcp-servers has 3.8k stars on GitHub.
Where can I find awesome-remote-mcp-servers?
punkpeye/awesome-remote-mcp-servers is on GitHub at https://github.com/punkpeye/awesome-remote-mcp-servers.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.