catalog16 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 |
|---|---|---|
| k402
https://x402-compute.68cxgfyr0.workers.dev/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/cisa-kev/mcp |
answers-mcp | 35 |
| Liminality
https://liminality.physea.ai/mcp |
answers-mcp | 22 |
| Liminality
https://mcp.physea.ai/mcp |
answers-mcp | 22 |
| eu-verify
https://data.greeneris.io/mcp |
answers-mcp | 19 |
| pitchpilot-mcp
https://pitchpilot-mcp.pitchpilot-agents.workers.dev/mcp |
answers-mcp | 13 |
| sigtap-agent-tools
https://sigtap-mcp.sigtap.workers.dev/mcp |
answers-mcp | 13 |
| agenticweb.nl
https://api.agenticweb.nl/api/mcp |
answers-mcp | 12 |
| Iron City
https://ironcity.sovereigntyempire.com/mcp |
answers-mcp | 10 |
| ARAKEL Machine Evidence Network
https://proof.arakelproof.space/mcp |
answers-mcp | 10 |
| agent-failure-archive
https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp |
answers-mcp | 9 |
| rasczak
https://rasczak-agent-service.rasczak-commons.workers.dev/mcp |
answers-mcp | 8 |
| x402-seller
https://x402-seller-m8nx.onrender.com/mcp |
answers-mcp | 7 |
| agentfeeds
https://api.agentfeeds.jp/mcp |
answers-mcp | 6 |
| scrape402
https://x402.shizu.me/mcp/rpc |
answers-mcp | 5 |
| EventEdge Oracle
https://edge.arakelproof.space/mcp |
answers-mcp | 2 |
16 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.