AI Product Index / MCP servers you can actually call
10,080 remotely-callable MCP servers across 7,519 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 63,360 registry records | excluded |
|---|---|
| superseded by a newer version | 43,839 |
| marked inactive | 205 |
| package-only, no remote URL | 9,569 |
| auth | servers | transport | servers |
|---|---|---|---|
| none | 8,106 | streamable-http | 9,341 |
| required | 1,974 | sse | 739 |
Queries run against /api/mcp/search, the same
endpoint an agent would call. Nothing is stored.
Concentration is the thing the headline count hides: 10,080 endpoints across 7,519 hosts means the typical operator publishes a handful, and a few publish thousands.
| # | host | endpoints | |
|---|---|---|---|
| 1 | gateway.pipeworx.io | 1,305 | |
| 2 | server.smithery.ai | 216 | |
| 3 | api.mcp.ai | 99 | |
| 4 | tooloracle.io | 57 | |
| 5 | api.lazy-mac.com | 54 | |
| 6 | mcp.apify.com | 43 | |
| 7 | mcp.olyport.com | 38 | |
| 8 | api.meok.ai | 34 | |
| 9 | nexgendata-mcp-proxy.steve-corbeil.workers.dev | 33 | |
| 10 | antibody-package-occasional-floppy.trycloudflare.com | 30 | |
| 11 | mcp.viridisconservation.com | 30 | |
| 12 | waystation.ai | 24 | |
| 13 | lab.flashalpha.com | 20 | |
| 14 | hive-mcp-gateway.onrender.com | 19 | |
| 15 | mcp.infobip.com | 18 | |
| 16 | app.daedalmap.com | 17 | |
| 17 | mcp.mcpbundles.com | 17 | |
| 18 | {host} | 16 | |
| 19 | doc2mcp.site | 15 | |
| 20 | roxyapi.com | 13 | |
| 21 | mcp.ansvar.eu | 12 | |
| 22 | stagenth.com | 11 | |
| 23 | whensport.com | 11 | |
| 24 | agent365.svc.cloud.microsoft | 9 | |
| 25 | feedoracle.io | 8 |
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.