browse11 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 |
|---|---|---|
| com.wingmanprotocol.agent/gateway
https://agent.wingmanprotocol.com/mcp |
answers-mcp | 57 |
| com.wingmanprotocol.agent/gateway
https://wingmanprotocol.com/mcp |
answers-mcp | 57 |
| pipeworx-gateway
https://gateway.pipeworx.io/bookbrainz/mcp |
answers-mcp | 34 |
| invinoveritas
https://api.babyblueviper.com/mcp |
answers-mcp | 33 |
| 1f3ea
https://1f3ea.com/mcp |
answers-mcp | 21 |
| bstorms
https://bstorms.ai/mcp |
answers-mcp | 14 |
| pinnacle-ask
https://ask-mcp.pinnacleblooms.org/mcp |
answers-mcp | 11 |
| redm-mcp
https://redm-mcp.fivem.no/mcp |
answers-mcp | 10 |
| thisispaper
https://www.thisispaper.com/intelligence/api/mcp |
answers-mcp | 10 |
| mycardfolio
https://mycardfolio.com/api/mcp |
answers-mcp | 7 |
| flowpack
https://flowpack-mcp.flowpackplugin.workers.dev/mcp |
answers-mcp | 5 |
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.