get_endpoint11 servers reported a tool by this name when we called them. Names are chosen by whoever wrote the server, so two tools sharing a name do not have to do the same thing. We record what was reported, not what it does.
| server | result when we called it | tools |
|---|---|---|
| echorelay-mcp
https://mcp.echorelay.dev |
answers-mcp | 79 |
| relin-mcp
https://relin.app/mcp |
answers-mcp | 52 |
| HookPulse
https://hookpulse.net/mcp |
answers-mcp | 14 |
| steamwebapi
https://mcp.steamwebapi.com/mcp |
answers-mcp | 10 |
| branch-app-group
https://docs.branchapp.com/mcp |
answers-mcp | 8 |
| MarketCheck Docs
https://developers.marketcheck.com/api/docs-mcp |
answers-mcp | 5 |
| Solana API & WebSocket Docs
https://mcp.vybenetwork.xyz |
answers-mcp | 5 |
| Solana API & WebSocket Docs
https://docs.vybenetwork.com/mcp |
answers-mcp | 5 |
| jojapi
https://mcp.jojapi.com |
answers-mcp | 4 |
| BenjiPays
https://benjipays.readme.io/mcp |
answers-mcp | 4 |
| BenjiPays
https://developer.benjipays.com/mcp |
answers-mcp | 4 |
11 of these answered an MCP handshake on the day we checked. That is not a promise the tool works, only that the server was running and told us the tool existed.