verify_report_receipt — Checkbooth MCP Tool
verify_report_receipt
(verify report receipt) is one of 12 tools on the
Checkbooth
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_report_receipt from your client
- Claude Code Checkbooth verify_report_receipt run in your project directory
- Claude Desktop Checkbooth verify_report_receipt ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Checkbooth verify_report_receipt ~/.cursor/mcp.json
- VS Code Checkbooth verify_report_receipt .vscode/mcp.json
- Zed Checkbooth verify_report_receipt ~/.config/zed/settings.json
- Windsurf Checkbooth verify_report_receipt ~/.codeium/windsurf/mcp_config.json
- Cline Checkbooth verify_report_receipt ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Checkbooth verify_report_receipt ~/.gemini/settings.json
- Grok Checkbooth verify_report_receipt .mcp.json (in your project root)
- ChatGPT Checkbooth verify_report_receipt Settings → Connectors → Advanced → Developer mode
- Claude.ai Checkbooth verify_report_receipt Settings → Connectors → Add custom connector
- LangChain Checkbooth verify_report_receipt pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http checkbooth https://checkbooth.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 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.