submit-receipt — Crinkl Commerce MCP MCP Tool
submit-receipt
(submit receipt) is one of 22 tools on the
Crinkl Commerce MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call submit-receipt from your client
- Claude Code Crinkl Commerce MCP submit-receipt run in your project directory
- Claude Desktop Crinkl Commerce MCP submit-receipt ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Crinkl Commerce MCP submit-receipt ~/.cursor/mcp.json
- VS Code Crinkl Commerce MCP submit-receipt .vscode/mcp.json
- Zed Crinkl Commerce MCP submit-receipt ~/.config/zed/settings.json
- Windsurf Crinkl Commerce MCP submit-receipt ~/.codeium/windsurf/mcp_config.json
- Cline Crinkl Commerce MCP submit-receipt ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Crinkl Commerce MCP submit-receipt ~/.gemini/settings.json
- Grok Crinkl Commerce MCP submit-receipt .mcp.json (in your project root)
- ChatGPT Crinkl Commerce MCP submit-receipt Settings → Connectors → Advanced → Developer mode
- Claude.ai Crinkl Commerce MCP submit-receipt Settings → Connectors → Add custom connector
- LangChain Crinkl Commerce MCP submit-receipt pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crinkl-commerce https://mcp.crinkl.xyz/mcpOther tools on this server
- get-protocol-summary
- get-cumulative-gmv
- get-daily-gmv
- get-trailing-gmv
- get-spend-signals
- resolve-cbsa
- get-merchant-summary
- get-spend-distribution
- get-settlement-summary
- get-gmv-inclusion-proof
- verify-reward-commitment
- verify-issued-gmv
- get-recent-issued-proofs
- get-issuer-keys
- get-reward-policy
- get-agent-capabilities
- get-vendors
- pair-agent
- claim-api-key
- verify-receipt
- get-agent-me
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.