create_task11 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 |
|---|---|---|
| timix-mcp https://api.timix.ai/api/integration/v1/mcp |
answers-mcp | 114 |
| AIOProductOS https://platform.aioproductos.com/api/mcp |
answers-mcp | 71 |
| OneHaus https://mcp.onehaus.app |
answers-mcp | 68 |
| rmcp https://api.dotnova.io/mcp |
answers-mcp | 62 |
| salesagent-mcp https://app.salesbot.cz/api/mcp |
answers-mcp | 50 |
| guesty-mcp-server https://guesty-mcp-server.vercel.app/mcp |
answers-mcp | 43 |
| mailcannon https://www.thinkandautomate.dev/api/mcp |
answers-mcp | 34 |
| cnvs-mcp https://cnvs.app/mcp |
answers-mcp | 25 |
| ganty-mcp https://ganty.app/api/mcp |
answers-mcp | 15 |
| astranl-mcp https://astranl.com/mcp/streamable |
answers-mcp | 6 |
| hire-specialist https://mcp.stoory.io/mcp |
answers-mcp | 6 |
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.