validate10 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 |
|---|---|---|
| GeodesicAI
https://app.geodesiclabs.ai/mcp |
answers-mcp | 37 |
| invinoveritas
https://api.babyblueviper.com/mcp |
answers-mcp | 33 |
| freightutils-mcp
https://www.freightutils.com/api/mcp/mcp |
answers-mcp | 25 |
| freightutils-mcp
https://www.freightutils.com/api/mcp |
answers-mcp | 25 |
| mercury-x402
https://network.mercury-hq.com/mcp |
answers-mcp | 18 |
| data-transform-api
https://api.lazy-mac.com/data-transform/mcp |
answers-mcp | 10 |
| aidc-design-engine
https://aidc-ai.io/api/mcp |
answers-mcp | 7 |
| 402Signal
https://402signal.com/mcp |
answers-mcp | 3 |
| 402Signal
https://402signal.com/mcp/v0.3.1 |
answers-mcp | 3 |
| machinegrade-validate-mcp
https://api.machinegrade.dev/mcp |
answers-mcp | 1 |
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.