search_cases9 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/oyez/mcp |
answers-mcp | 34 |
| Politikdata.dk MCP
https://mcp.politikdata.dk/mcp |
answers-mcp | 21 |
| korea-tax-law
https://mcp.taxjarvis.com/mcp |
answers-mcp | 12 |
| contract-compass
https://contract.sallim.app/mcp |
answers-mcp | 11 |
| contract-compass
https://contract.sallim.app/mcp?via=official |
answers-mcp | 11 |
| VICP Registry
https://vicp-registry.org/mcp |
answers-mcp | 10 |
| case-doha-record
https://www.clearancesearchengine.com/api/mcp |
answers-mcp | 7 |
| gwinnett-index
https://www.gwindex.net/mcp |
answers-mcp | 5 |
| proofstack
https://proof-stack-lake.vercel.app/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.