whoami51 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 |
|---|---|---|
| BorealHost https://borealhost.ai/mcp/ |
answers-mcp | 152 |
| redu-cloud-mcp https://mcp.redu.cloud/mcp |
answers-mcp | 81 |
| Tango https://tango.applayer.io/mcp |
answers-mcp | 81 |
| AIOProductOS https://platform.aioproductos.com/api/mcp |
answers-mcp | 71 |
| clusterhack https://clusterhack.dev/mcp/ |
answers-mcp | 60 |
| the-balanced-investor-club https://thebalancedinvestorclub.com/api/mcp/mcp |
answers-mcp | 57 |
| afterlaunch https://afterlaunch.io/api/mcp |
answers-mcp | 51 |
| spriteship https://spriteship.com/mcp |
answers-mcp | 44 |
| seekrit https://mcp.seekrit.dev/mcp |
answers-mcp | 40 |
| Riddle Creator MCP https://www.riddle.com/creator/api/v3/mcp |
answers-mcp | 38 |
| coinrithm-trading https://mcp.coinrithm.com/mcp |
answers-mcp | 38 |
| zooza-mcp https://mcp.zooza.app/mcp |
answers-mcp | 34 |
| latticenet https://latticenet.ai/mcp |
answers-mcp | 33 |
| com.mcpscores/agent-continuity https://mcpfax-continuity.bowling-anthony.workers.dev/mcp |
answers-mcp | 33 |
| eyeot-erp https://erp.eyeot.fr/api/v1/mcp |
answers-mcp | 33 |
| duami https://duami.ai/mcp |
answers-mcp | 29 |
| bim.house https://bim.house/mcp |
answers-mcp | 29 |
| eqvps https://mcp.eqvps.com/mcp |
answers-mcp | 27 |
| Ripostiq https://ripostiq.com/mcp |
answers-mcp | 24 |
| reachpad https://reachpad.dev/mcp |
answers-mcp | 24 |
| exmachina-ai https://exmachina-ai.fly.dev/mcp |
answers-mcp | 23 |
| FeatureJet MCP https://mcp.featurejet.com/mcp |
answers-mcp | 22 |
| squirrelscan https://mcp.squirrelscan.com/mcp |
answers-mcp | 20 |
| lightbringer-mcp-server https://mcp.lightbringer.com/mcp |
answers-mcp | 18 |
| recao https://recao.app/api/mcp |
answers-mcp | 17 |
| gitbuyer https://gitbuyer.com/mcp |
answers-mcp | 16 |
| aura https://aura.rohnelt.dev/mcp |
answers-mcp | 16 |
| depthfeed https://api.depthfeed.com/mcp |
answers-mcp | 15 |
| crevio-api https://mcp.crevio.co/mcp |
answers-mcp | 14 |
| forkmate https://app.forkmate.ai/mcp |
answers-mcp | 12 |
| forkmate https://mcp.forkmate.ai/ |
answers-mcp | 12 |
| sitectrl https://mcp.sitectrl.ai/mcp |
answers-mcp | 12 |
| tomorrowcentral https://api.tomorrowcentral.com/mcp |
answers-mcp | 12 |
| loro.bot https://loro.bot/mcp |
answers-mcp | 11 |
| submitmap https://submitmap.com/api/mcp |
answers-mcp | 11 |
| kortex https://kortex.rohnelt.dev/mcp |
answers-mcp | 10 |
| vortex https://vortex.rohnelt.dev/mcp |
answers-mcp | 10 |
| ai-crawler-index https://www.pathwren.workers.dev/mcp?s=pathwren-edge&c=mcp-registry |
answers-mcp | 9 |
| ai-crawler-index https://www.pathwren.workers.dev/c/mcp-registry-official/mcp |
answers-mcp | 9 |
| crawler-ip-verifier https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck |
answers-mcp | 8 |
| crawler-log-triage https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/triage |
answers-mcp | 8 |
| robots-policy-lint https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/robots |
answers-mcp | 8 |
| victano https://mcp.victano.com/mcp |
answers-mcp | 7 |
| lettera https://api.lettera.dev/mcp |
answers-mcp | 7 |
| agent-discovery-doctor https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/doctor |
answers-mcp | 7 |
| mcp-endpoint-lint https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint |
answers-mcp | 7 |
| dealscanner https://mcp.dealscanner.io/mcp |
answers-mcp | 7 |
| blogcaster-mcp https://blogcaster-mcp.rrpb2580.workers.dev/mcp |
answers-mcp | 7 |
| at-directory https://mcp.agenticterminal.ai/mcp |
answers-mcp | 6 |
| project-launch-ai https://projectlaunch.ai/mcp |
answers-mcp | 4 |
| Notsy Facturación https://mcp.notsy.com.mx/mcp |
answers-mcp | 4 |
51 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.