Declared-vs-Enforced Agent Access Verification
Compares declared agent access against actual enforcement per identity class, with drift watch.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http declared-vs-enforced-agent-access-verifi 'https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp'
{
"mcpServers": {
"declared-vs-enforced-agent-access-verifi": {
"type": "http",
"url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
}
}
}
Frequently asked questions
What is Declared-vs-Enforced Agent Access Verification?
Compares declared agent access against actual enforcement per identity class, with drift watch.
How do I install Declared-vs-Enforced Agent Access Verification?
It runs as a remote server. In Claude Code: claude mcp add --transport http declared-vs-enforced-agent-access-verifi 'https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Declared-vs-Enforced Agent Access Verification need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Who maintains Declared-vs-Enforced Agent Access Verification?
It is published by com.textforagents. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.