`verify_certificate`

12 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
GeodesicAI https://app.geodesiclabs.ai/mcp	answers-mcp	37
taste-mcp https://api.humantaste.app/mcp/	answers-mcp	20
agent-offset-clearinghouse-agent https://mcp.viridisconservation.com/offsets/mcp	answers-mcp	19
progenly https://progenly.com/mcp	answers-mcp	16
redeal https://api.redeal.dev/mcp	answers-mcp	12
agent-provenance-agent https://mcp.viridisconservation.com/provenance/mcp	answers-mcp	11
deusproof https://deusproof.com/mcp	answers-mcp	10
causallayer-mcp https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp	answers-mcp	10
causallayer-mcp https://mcp.faultkey.com/mcp	answers-mcp	10
mcp-typescript server on vercel https://mcp.mydatapass.app/api/mcp	answers-mcp	5
agentcommunity https://agentcommunity.org/mcp	answers-mcp	4
kaneme https://kaneme.com/api/mcp/public	answers-mcp	2

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