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