verify_audit_trail — backend MCP Tool
verify_audit_trail
(verify audit trail) is one of 6 tools on the
backend
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_audit_trail from your client
- Claude Code backend verify_audit_trail run in your project directory
- Claude Desktop backend verify_audit_trail ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor backend verify_audit_trail ~/.cursor/mcp.json
- VS Code backend verify_audit_trail .vscode/mcp.json
- Zed backend verify_audit_trail ~/.config/zed/settings.json
- Windsurf backend verify_audit_trail ~/.codeium/windsurf/mcp_config.json
- Cline backend verify_audit_trail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI backend verify_audit_trail ~/.gemini/settings.json
- Grok backend verify_audit_trail .mcp.json (in your project root)
- ChatGPT backend verify_audit_trail Settings → Connectors → Advanced → Developer mode
- Claude.ai backend verify_audit_trail Settings → Connectors → Add custom connector
- LangChain backend verify_audit_trail pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http backend https://api.collarguardrail.com/mcp-http/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.