tags5 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/datagov-au/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-europa/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/the-guardian/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/boston-calendar/mcp |
answers-mcp | 33 |
| flask
https://api.flask.do/api/mcp/mcp |
answers-mcp | 17 |
5 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.