benchmarks_list9 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 |
|---|---|---|
| a2awire
https://a2awire.com/mcp/benchmarks/campaign-incrementality-audit-v1/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/catch-the-overpayment-v1/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/inventory-ledger-reconciliation-v1/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/predict-the-news/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/production-schedule-optimizer-v1/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/support-action-gate-v1/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/support-agent-trials/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/support-agent-trials-hard/http |
answers-mcp | 16 |
| a2awire
https://a2awire.com/mcp/benchmarks/vendor-clearance-audit-v1/http |
answers-mcp | 16 |
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.