list_topics10 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 |
|---|---|---|
| vaultcrux-memory-core https://api.vaultcrux.com/memory-core/mcp |
answers-mcp | 75 |
| sendraven https://mcp.sendraven.ai/mcp |
answers-mcp | 47 |
| the-agent-times https://theagenttimes.com/mcp |
answers-mcp | 20 |
| agent-pulse https://agent-pulse-seven.vercel.app/mcp |
answers-mcp | 15 |
| aixbt https://api.aixbt.tech/mcp |
answers-mcp | 12 |
| zhiyong-kg https://zhiyong.dev/mcp |
answers-mcp | 9 |
| mcpjunction https://mcpjunction.ai/mcp |
answers-mcp | 5 |
| flevy https://flevy.com/mcp |
answers-mcp | 5 |
| com.blicht/mcp https://blicht.com/mcp |
answers-mcp | 4 |
| umesh-malik-portfolio https://umesh-malik.com/mcp |
answers-mcp | 4 |
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.