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