Declared-vs-Enforced Agent Access Verification
Compares declared agent access against actual enforcement per identity class, with drift watch.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (53 ms) | our check, 2026-10-21 |
| Protocol version | 2025-03-26 | our check, 2026-10-21 |
| Tools (3) | access_probe, drift_targets, drift_run | tools/list, 2026-10-21 |
| Registry version | 1.0.0 · active · updated 2026-10-20 | 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 declared-vs-enforced-agent-access-verification https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Agent-asset reclamation (lost-and-found) Lost-and-found for agent-created assets: sweep, title proof, register, check first.
- Agent exit execution for self-procured services Dependency-probe-gated exit execution with hash-verified extraction and signed receipts.
- Browser rehearsal range for agents Rehearsal range: mirror a site, rehearse the workflow, earn a drift-bound promotion…
- Catalog-cache guard for agent tool catalogs Cache guard: forced-private partitioning, TTL clamp, fingerprint diffing, exposure…
- Continuous agent-speed defense for public surfaces Agent-speed defense for your own public surfaces: daily diff probes, per-identity…
- Demand-response aggregator for agent fleets Demand-response for agent fleets: contracted shed, verified settlement, paid…
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/declared-vs-enforced-agent-access-verification)<a href="https://openforallofus.com/tools/com.textforagents/declared-vs-enforced-agent-access-verification"><img src="https://openforallofus.com/badge/com.textforagents/declared-vs-enforced-agent-access-verification.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/declared-vs-enforced-agent-access-verification.