jwt_decode8 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 |
|---|---|---|
| blixtworks
https://www.blixtworks.com/mcp |
answers-mcp | 68 |
| rmcp
https://raccha.ai/mcp |
answers-mcp | 59 |
| quartermaster
https://quartermaster.surewhynot.app/mcp |
answers-mcp | 49 |
| formatho-runtime
https://mcp.formatho.com/mcp |
answers-mcp | 26 |
| cleanor
https://mcp.cleanor.app/mcp |
answers-mcp | 22 |
| casper-tools
https://determines-product-administration-farmer.trycloudflare.com |
answers-mcp | 17 |
| pitchpilot-mcp
https://pitchpilot-mcp.pitchpilot-agents.workers.dev/mcp |
answers-mcp | 13 |
| sigtap-agent-tools
https://sigtap-mcp.sigtap.workers.dev/mcp |
answers-mcp | 13 |
8 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.