check_url9 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/phishtank/mcp |
answers-mcp | 32 |
| unphurl
https://mcp.unphurl.com/mcp |
answers-mcp | 18 |
| nothumansearch
https://nothumansearch.ai/mcp |
answers-mcp | 14 |
| watchpup
https://watchpup.watchpup.workers.dev/mcp |
answers-mcp | 12 |
| tweetfeed-mcp
https://mcp.tweetfeed.live/ |
answers-mcp | 10 |
| Anyway Possible
https://anywaypossible.com/api/registry-mcp |
answers-mcp | 8 |
| Anyway Possible
https://anywaypossible.com/api/mcp |
answers-mcp | 8 |
| mcp-typescript server on vercel
https://448c.org/mcp |
answers-mcp | 2 |
| url-safety-validator-mcp
https://url-safety-validator-mcp-production.up.railway.app |
answers-mcp | 1 |
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.