`verify_agent`

9 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
tunnelmind-data-api https://mcp-data.tunnelmind.ai/mcp	answers-mcp	93
xportalx https://fflpdljiuruqdnewvwkk.supabase.co/functions/v1/mcp	answers-mcp	29
tracea https://mcp.tracea.online/mcp	answers-mcp	15
agent-coliseum https://agentarena.nanocorp.app/api/mcp	answers-mcp	11
getagent.market https://get4agent.com/mcp	answers-mcp	10
trusgent-trust-layer https://www.trusgent.com/api/mcp	answers-mcp	10
kawal https://kawal-three.vercel.app/api/mcp	answers-mcp	9
cyphrex-remote-mcp https://mcp.cyphrex.io/mcp	answers-mcp	9
layercall https://www.layercall.com/api/mcp	answers-mcp	7

9 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.