search_packages8 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/govinfo/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/npm/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/pub-dev/mcp |
answers-mcp | 35 |
| npmscan
https://npmscan.com/api/mcp |
answers-mcp | 23 |
| devstack
https://devstack-mcp.vercel.app/mcp |
answers-mcp | 10 |
| Gitsim
https://chat.gitsim.com/api/mcp |
answers-mcp | 9 |
| event-escapes
https://mcp.eventescapes.com |
answers-mcp | 7 |
| sbox-watch
https://sbox.watch/mcp |
answers-mcp | 6 |
8 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.