list_versions10 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 |
|---|---|---|
| mcp-typescript server on vercel
https://shiply.now/mcp |
answers-mcp | 114 |
| pipeworx-gateway
https://gateway.pipeworx.io/npm/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/maven-central/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/nuget/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/packagist/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/pkg-go-dev/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/pub-dev/mcp |
answers-mcp | 35 |
| midvash
https://mcp.midvash.com/mcp/registry |
answers-mcp | 11 |
| fft-companion
https://mcp.fftcompanion.app/mcp |
answers-mcp | 8 |
| llmref
https://api.llmref.org/v1/mcp |
answers-mcp | 4 |
10 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.