AI Product Index / Find a remote MCP endpoint

Find a remote MCP endpoint

16,526 declared remote MCP endpoints across 11,899 hosts, with authentication and transport details. A rotating sample is probed weekly; individual availability and tool behavior remain unverified.

Mirrored from Official MCP Registry on 2026-09-07, liveness probed 2026-10-19. Raw: stats.json · catalog.json · health.json.

16,526
declared remote endpoints
11,899
distinct hosts
13,469
declare no credentials
90.4%
responded in latest sample

What is in scope

The rule is active + latest + remotely callable, and the exclusions are the opinion. A server distributed only as an installable package is a thing you install; this catalog covers declared remote URLs. A URL may still require provider setup, credentials or an account before you can use it.

from 94,665 registry recordsexcluded
superseded by a newer version66,430
marked inactive317
package-only, no remote URL11,801

Credentials and transport

authserverstransportservers
none13,469streamable-http15,460
required3,057sse1,066

Find an endpoint

Filter by the requirements of your client. Catalog details are publisher declarations, not a compatibility guarantee.




No credentials does not mean free. Check the provider’s price and your client’s supported transport.

Results appear here. With JavaScript off, use the JSON search.

Before you connect

Health checks cover a rotating sample. Failed observations carry their own date; no recorded failure does not mean a successful check. Even an HTTP response does not prove that authentication, payment or a tool operation will succeed.

  1. Choose a client that supports the result’s transport and accepts a remote MCP URL.
  2. Use the endpoint URL in that client’s remote-server configuration. Follow the provider’s own instructions for credentials and pricing.
  3. Inspect the offered tools and permissions before running anything. This directory has not verified their task-level behavior.

The 25 largest operators

Concentration is the thing the headline count hides: 16,526 endpoints across 11,899 hosts means the typical operator publishes a handful, and a few publish thousands.

#hostendpoints
1 gateway.pipeworx.io 1,314
2 api.mcp.ai 1,115
3 api.m2mcent.com 276
4 server.smithery.ai 216
5 mcp.apify.com 107
6 agent-observatory-sensor.nolimit-observatory.workers.dev 103
7 openings-vote-drilling-initially.trycloudflare.com 90
8 tooloracle.io 57
9 api.lazy-mac.com 54
10 mcp.jojapi.com 49
11 a2awire.com 44
12 api.meok.ai 39
13 mcp.olyport.com 38
14 nexgendata-mcp-proxy.steve-corbeil.workers.dev 33
15 antibody-package-occasional-floppy.trycloudflare.com 30
16 mcp.zovo.one 30
17 mcp.viridisconservation.com 29
18 mcp.nexlab.net 24
19 waystation.ai 24
20 mcp.moltlinestudio.com 22
21 lab.flashalpha.com 20
22 hive-mcp-gateway.onrender.com 19
23 roxyapi.com 19
24 {host} 18
25 mcp.boykaf.com 18

Provenance and removal

This is a mirror of a public registry, republished so it can be queried and so its liveness is knowable. It states no facts of its own about these endpoints beyond whether they answered a request. If you operate one of them and want it gone, open an issue on the repo — no justification needed, and it is removed on the next build.