Back to the tool index

read_url

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

serverresult when we called ittools
Andreax x402 Services
https://pagos.andreax.dev/mcp
answers-mcp 160
k402
https://x402-compute.68cxgfyr0.workers.dev/mcp
answers-mcp 36
eucompliance-tools
https://mcp.eucompliance.tools/mcp
answers-mcp 24
sausage-web
https://x402.professorsausages.com/mcp/web
answers-mcp 12
skill-audit
https://eltociear-skill-audit.hf.space/mcp
answers-mcp 11
srezai
https://srezai.ru/api/mcp
answers-mcp 10
tokenguard
https://eltociear-tokenguard.hf.space/mcp
answers-mcp 9
web-access-gateway
https://web-access-gateway.mattskowronis.workers.dev/mcp
answers-mcp 8
fetchgate
https://fetchgate.dev/mcp
answers-mcp 6
agent-web
https://agent-web.foomworks.workers.dev/mcp
answers-mcp 5

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