metadata27 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 |
|---|---|---|
| blixtworks
https://www.blixtworks.com/mcp |
answers-mcp | 68 |
| pipeworx-gateway
https://gateway.pipeworx.io/coinmarketcap/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/mygene-info/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-ny/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-fcc/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-fortworth/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-fulton/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-howardcounty/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-kingcounty/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-maryland/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-mesa/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-michigan/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-mo/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-nj/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-norfolk/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-novascotia/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-oakland/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-usdot/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-utah/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-va/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-vermont/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-wa/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-winnipeg/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/mychem/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/mydisease/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/myvariant/mcp |
answers-mcp | 34 |
| mercury-x402
https://network.mercury-hq.com/mcp |
answers-mcp | 18 |
27 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.