compare_models9 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 |
|---|---|---|
| imagine-mcp
https://app.creativeclaw.co/mcp |
answers-mcp | 46 |
| pipeworx-gateway
https://gateway.pipeworx.io/climate/mcp |
answers-mcp | 33 |
| OpenDealer MCP Server
https://mcp.opendealer.app/rpc |
answers-mcp | 27 |
| ai-pricing-hub
https://aipricinghub.com/mcp/rpc |
answers-mcp | 11 |
| the-aggregate
https://theaggregate.ai/mcp |
answers-mcp | 8 |
| modelpricewatch
https://modelpricewatch.com/mcp |
answers-mcp | 5 |
| operant-mcp
https://operant-mcp.saagar210.workers.dev/mcp |
answers-mcp | 5 |
| api-response-cost-analyzer-mcp
https://api.lazy-mac.com/api-response-cost-analyzer/mcp |
answers-mcp | 4 |
| ai-model-router
https://api.lazy-mac.com/ai-model-router/mcp |
answers-mcp | 3 |
9 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.