search_documents11 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/riksdagen-se/mcp |
answers-mcp | 35 |
| iwac-mcp-server
https://islam.zmo.de/mcp/ |
answers-mcp | 34 |
| hpt-su
https://mcp.hpt.su/mcp |
answers-mcp | 21 |
| OpenPublica
https://api.openpublica.com/mcp |
answers-mcp | 15 |
| supovia-mcp
https://mcp.supovia.com/mcp |
answers-mcp | 14 |
| mkdshare
https://mkdshare.dev/mcp |
answers-mcp | 11 |
| comitelligence
https://comitelligence-mcp.onrender.com/mcp |
answers-mcp | 8 |
| dokumendiregister
https://dokumendiregister.ee/api/dokreg-mcp/mcp |
answers-mcp | 6 |
| regulatory-intel
https://regulatory.datakoot.com/mcp |
answers-mcp | 5 |
| rmcp
https://doc.liz6.com/mcp |
answers-mcp | 5 |
| StatelessServer
https://developerknowledge.googleapis.com/mcp |
answers-mcp | 3 |
11 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.