chat10 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 |
|---|---|---|
| AgentServices
https://agentservices.to/mcp |
answers-mcp | 64 |
| bim.house
https://bim.house/mcp |
answers-mcp | 29 |
| marketintell
https://api.marketintell.ai/mcp |
answers-mcp | 17 |
| insurance-advisor
https://whylingxi.cn/mcp |
answers-mcp | 9 |
| jarvisclaw-mcp
https://api.jarvisclaw.ai/mcp |
answers-mcp | 9 |
| PersonAIzer.Sessions
https://sessions.personaizer.com/mcp |
answers-mcp | 5 |
| scrape402
https://x402.shizu.me/mcp/rpc |
answers-mcp | 5 |
| router
https://mcp.router.ai/mcp |
answers-mcp | 4 |
| unorouter
https://mcp.unorouter.com/mcp |
answers-mcp | 3 |
| hal9/mcpbuild/send-email
https://next.hal9.ai/mcp/mcpbuild/send-email |
answers-mcp | 1 |
10 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.