Declared-vs-Enforced Agent Access Verification MCP Server

by textforagents Your server? Claim it

answering

Declared-vs-Enforced Agent Access Verification is answering right now. Last checked 5 min ago. It exposes 4 tools.

Compares declared agent access against actual enforcement per identity class, with drift watch.

Uptime history 5 days of history · worst day 97%

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

321 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

23 Oct a tool changed version

22 Oct a tool appeared drift_remove

22 Oct a tool description was rewritten drift_run

22 Oct a tool changed version

21 Oct a tool changed version

Declared-vs-Enforced Agent Access Verification does not always answer

Over the last week it answered 99.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add declared-vs-enforced-agent-access-verification --transport http https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp

Settings → Connectors → Add custom connector, then paste this address

https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp

~/.codex/config.toml

[mcp_servers.declared-vs-enforced-agent-access-verification]
url = "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "declared-vs-enforced-agent-access-verification": {
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "declared-vs-enforced-agent-access-verification": {
      "type": "http",
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

drift

drift_remove

Remove one enrolled drift-watch target (records no drift event).

drift_run

Re-probe one enrolled target now and record two-sided drift (manual runs metered: 1/min/target).

drift_targets

List your enrolled drift-watch targets.

access

access_probe

Pre-flight declared-vs-enforced probe of one target path (one-time grant; the $0.01 x402 rail is the HTTP /probe endpoint).

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp	streamable-http	answering	318 ms	5 min ago

Alternatives to Declared-vs-Enforced Agent Access Verification

same job, measured the same way

MCP V1

by 636865636b73756d

Sub-cent factual claim verification against live data sources.

23 installs/wk local only

Verify MCP

by agentutil

Sub-cent factual claim verification against live data sources.

16 installs/wk local only

Agent deliverable verification: acceptance criteria vs evidence

by nodcheck

Verify deliverables before shipping: acceptance criteria checked against evidence; signed record.

8 tools answering

MCPVault

by coburn2716

Search evidence-labelled MCP servers with freshness, install, compatibility and verification data.

14 installs/wk local only

Pre-install canonical-identity verification

by textforagents

Pre-install canonical-identity verification for MCP servers and skills, with signed verdicts.

3 tools answering

Agent Incident Classification Notification

by textforagents

Signed agent-incident classification vs PP-26-4396, with third-party notification receipts.

3 tools answering

Agent Mandate Verification

by api-disk-integrations

Verify a proposed action against a signed Agent Mandate without executing or mutating accounts.

19 installs/wk local only

Works With Agents MCP

by vystartasv

14 MCP tools: facts, pitfalls, skills, handoff protocols, trust scores, identity verification.

130 installs/wk local only

Declared-vs-Enforced Agent Access Verification — questions

Answers built from our own checks of this server.

What can Declared-vs-Enforced Agent Access Verification do?

It exposes 4 tools, read directly from the server on our last check. Among them: access_probe, drift_remove, drift_run, drift_targets. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Declared-vs-Enforced Agent Access Verification working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 321 ms. The bar chart above shows every period we have measured.

How do I connect Declared-vs-Enforced Agent Access Verification?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Declared-vs-Enforced Agent Access Verification need an API key?

No. Declared-vs-Enforced Agent Access Verification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Declared-vs-Enforced Agent Access Verification?

It answers our handshake in 321 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.