AI Product Index / MCP servers you can actually call
16,526 remotely-callable MCP servers across 11,899 hosts — the ones with a URL, not the ones you would have to install — checked weekly for whether they answer.
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 set up; one with a URL is a thing an agent can use right now, and this catalog answers the second question.
| from 94,665 registry records | excluded |
|---|---|
| superseded by a newer version | 66,430 |
| marked inactive | 317 |
| package-only, no remote URL | 11,801 |
| auth | servers | transport | servers |
|---|---|---|---|
| none | 13,469 | streamable-http | 15,460 |
| required | 3,057 | sse | 1,066 |
Queries run against /api/mcp/search, the same
endpoint an agent would call. Nothing is stored.
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.
| # | host | endpoints | |
|---|---|---|---|
| 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 |
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.