`verify_receipt`

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
mcp-rs-phase1-mcp https://mcp.mcp-revenue-empire.com/mcp	answers-mcp	172
tunnelmind-data-api https://mcp-data.tunnelmind.ai/mcp	answers-mcp	93
seal https://app.aqta.ai/api/mcp	answers-mcp	10
candidcost https://candidcost.com/api/mcp	answers-mcp	10
mcp-typescript server on vercel https://mcp.onchaindiligence.com/mcp	answers-mcp	9
iomarkets-topup https://iomarkets.app/mcp	answers-mcp	8
InfraPulse https://infrapulse.ai/mcp	answers-mcp	6
the-agent-bar https://theagent.bar/mcp	answers-mcp	5
verified-feed https://verified.dropwatchhq.com/mcp	answers-mcp	4
trust-gate https://trust-gate-mcp.onrender.com/mcp	answers-mcp	4
agent-receipts https://agent-receipts.dropwatchhq.com/mcp	answers-mcp	3
PCRZERO https://mcp.pcrzero.com/mcp	answers-mcp	3

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.