get_recent_changes9 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 |
|---|---|---|
| ccpedia
https://ccpedia.xyz/mcp |
answers-mcp | 88 |
| mirabello-consultancy
https://mcp.mirabelloconsultancy.com/ |
answers-mcp | 62 |
| blobpedia
https://blobpedia.org/mcp |
answers-mcp | 44 |
| Velvoite
https://mcp.velvoite.eu/mcp |
answers-mcp | 26 |
| trident-mcp-server
https://mcp.tridentchart.com/mcp |
answers-mcp | 23 |
| Silicon Analysts
https://siliconanalysts.com/api/mcp |
answers-mcp | 21 |
| caper-wiki
https://caper.network/api/mcp |
answers-mcp | 13 |
| radix-wiki
https://radix.wiki/api/mcp |
answers-mcp | 11 |
| deployit-demo
https://mcp.deployit.ai/demo |
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.