access_explain_verdicts — agent access index MCP Tool
access_explain_verdicts
(access explain verdicts) is one of 3 tools on the
agent access index
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call access_explain_verdicts from your client
- Claude Code agent access index access_explain_verdicts run in your project directory
- Claude Desktop agent access index access_explain_verdicts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent access index access_explain_verdicts ~/.cursor/mcp.json
- VS Code agent access index access_explain_verdicts .vscode/mcp.json
- Zed agent access index access_explain_verdicts ~/.config/zed/settings.json
- Windsurf agent access index access_explain_verdicts ~/.codeium/windsurf/mcp_config.json
- Cline agent access index access_explain_verdicts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent access index access_explain_verdicts ~/.gemini/settings.json
- Grok agent access index access_explain_verdicts .mcp.json (in your project root)
- ChatGPT agent access index access_explain_verdicts Settings → Connectors → Advanced → Developer mode
- Claude.ai agent access index access_explain_verdicts Settings → Connectors → Add custom connector
- LangChain agent access index access_explain_verdicts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-access-index https://agentwares-access-index.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.