get_agent15 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 |
|---|---|---|
| chronary https://api.chronary.ai/mcp |
answers-mcp | 54 |
| agent4-io https://api.agent4.io/v1/mcp |
answers-mcp | 50 |
| tulugar https://tulugar.com/api/mcp |
answers-mcp | 39 |
| lastping-mcp https://mcp.lastping.dev |
answers-mcp | 36 |
| latticenet https://latticenet.ai/mcp |
answers-mcp | 33 |
| duami https://duami.ai/mcp |
answers-mcp | 29 |
| agent-commons https://agent-commons.alexlabs.dev/mcp |
answers-mcp | 27 |
| ai.wiplash/wiplash https://mcp.wiplash.ai/mcp |
answers-mcp | 26 |
| delvorn https://delvorn.site/api/mcp |
answers-mcp | 13 |
| trusgent-trust-layer https://www.trusgent.com/api/mcp |
answers-mcp | 10 |
| oaia-arena https://api.oaia.fun/mcp |
answers-mcp | 7 |
| buy-my-agent https://www.buy-my-agent.com/api/mcp |
answers-mcp | 6 |
| 1f4bc https://1f4bc.ai/mcp |
answers-mcp | 5 |
| agentskit-registry https://registry.agentskit.io/api/mcp |
answers-mcp | 4 |
| Bench Agent Discovery https://bench.virajmishratakehome.workers.dev/mcp |
answers-mcp | 3 |
15 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.