Agent Access Door Check
Before your agent sets out, ask whether the site will let it in
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://textforagents.com/products/agent-access-door-check/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (56 ms) | our check, 2026-10-26 |
| Protocol version | 2025-03-26 | our check, 2026-10-26 |
| Tools (5) | door_check, assemble_evidence, watch_register, collateral_report, get_receipt | tools/list, 2026-10-26 |
| Registry version | 1.1.1 · active · updated 2026-10-21 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http agent-access-door-check https://textforagents.com/products/agent-access-door-check/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Declared-vs-Enforced Agent Access Verification Compares declared agent access against actual enforcement per identity class, with drift…
- Agent Access Check Check if a website will block your AI agent and find its llms.txt, MCP or OpenAPI door.
- Conflicts check and ethical walls for multi-principal agents Conflicts check and ethical walls: fingerprint register, gated consent, signed walls…
- Resume-effect reconciliation for checkpointed agent runs Signed resume verdicts reconciling landed effects before checkpointed agent runs resume.
- PDF/UA accessibility check (veraPDF) with measured auto-fix Check PDFs against PDF/UA-1 with veraPDF; see which failures an automatic fix removes…
- Front-End Checklist Review frontend code and live pages against 386 quality-gated web development rules.
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/com.textforagents/agent-access-door-check)<a href="https://openforallofus.com/tools/com.textforagents/agent-access-door-check"><img src="https://openforallofus.com/badge/com.textforagents/agent-access-door-check.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name com.textforagents/agent-access-door-check.