events15 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 |
|---|---|---|
| dc-member-api
https://api.dynamitecircle.com/mcp |
answers-mcp | 85 |
| pipeworx-gateway
https://gateway.pipeworx.io/seatgeek/mcp |
answers-mcp | 40 |
| pipeworx-gateway
https://gateway.pipeworx.io/nasa-eonet/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/19hz/mcp |
answers-mcp | 33 |
| pipeworx-gateway
https://gateway.pipeworx.io/boston-calendar/mcp |
answers-mcp | 33 |
| pipeworx-gateway
https://gateway.pipeworx.io/nyc-parks/mcp |
answers-mcp | 33 |
| pipeworx-gateway
https://gateway.pipeworx.io/openagenda/mcp |
answers-mcp | 33 |
| pipeworx-gateway
https://gateway.pipeworx.io/barcelona-events/mcp |
answers-mcp | 32 |
| pipeworx-gateway
https://gateway.pipeworx.io/idf-events/mcp |
answers-mcp | 32 |
| pipeworx-gateway
https://gateway.pipeworx.io/madrid-events/mcp |
answers-mcp | 32 |
| pipeworx-gateway
https://gateway.pipeworx.io/montreal-events/mcp |
answers-mcp | 32 |
| pipeworx-gateway
https://gateway.pipeworx.io/paris-events/mcp |
answers-mcp | 32 |
| pipeworx-gateway
https://gateway.pipeworx.io/sf-recpark/mcp |
answers-mcp | 32 |
| warp-agent-mcp
https://mcp.wearewarp.com/api/mcp |
answers-mcp | 31 |
| weathersight
https://weathersight.io/api/mcp |
answers-mcp | 19 |
15 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.