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