search_apis9 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 |
|---|---|---|
| pipeworx-gateway
https://gateway.pipeworx.io/apis-guru/mcp |
answers-mcp | 35 |
| helpmyagent
https://api.helpmyagent.com/mcp |
answers-mcp | 30 |
| anyapi
https://api.getanyapi.com/mcp |
answers-mcp | 10 |
| jarvisclaw-mcp
https://api.jarvisclaw.ai/mcp |
answers-mcp | 9 |
| apistatuscheck
https://apistatuscheck.com/api/mcp |
answers-mcp | 8 |
| jojapi
https://mcp.jojapi.com |
answers-mcp | 4 |
| jentic-mcp-server
https://api.jentic.com/mcp |
answers-mcp | 4 |
| ppn-mcp-gateway
https://mcp.ppn-hub.com/mcp |
answers-mcp | 3 |
| payapi-market
https://payapi.market/mcp |
answers-mcp | 3 |
9 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.