get_schema9 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 |
|---|---|---|
| webhook-studio https://webhook-studio.com/mcp |
answers-mcp | 17 |
| clipkit https://www.clipkit.dev/mcp |
answers-mcp | 15 |
| insurance-advisor https://whylingxi.cn/mcp |
answers-mcp | 9 |
| TickerDB https://mcp.tickerdb.com/mcp |
answers-mcp | 9 |
| codecraft https://codecraft-ashy-seven.vercel.app/mcp |
answers-mcp | 9 |
| energetica-data https://energetica.ar/api/mcp |
answers-mcp | 8 |
| filingpulse https://mcp.filingpulse.io/mcp |
answers-mcp | 7 |
| structforge https://structforge.askqa.app/mcp |
answers-mcp | 6 |
| agent-papers https://agentpapers.dev/api/mcp |
answers-mcp | 6 |
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.