xyz.crinkl.mcp/crinkl-commerce
Official22 toolsCrinkl Commerce MCP
Verified commerce data and proof-backed shopper activation tools for agents.
Access verified commerce data and activate shoppers with proof-backed tools.
Captured live from the server via tools/list.
get-protocol-summary
Get a concise explanation of what Crinkl is and how the protocol works. Use this first if you have no prior context about Crinkl. Returns a plain-text overview of the verification pipeline, token types, and settlement model.
No parameters.
get-cumulative-gmv
Get cumulative Gross Merchandise Value (GMV) from the public cumulative feed. The live Crinkl site displays this live beta cumulative total on top of the finalized alpha base; provide startDate to bound the window explicitly. Returns a cryptographically signed token containing total USD cents, spend count, and computation timestamp.
Parameters (2)
- startDatestring
Optional ISO date (YYYY-MM-DD) to start counting from. The live beta cumulative feed uses 2026-01-27.
- asOfDatestring
Optional ISO date to compute GMV as of (defaults to now)
get-daily-gmv
Get the signed GMV summary for a specific calendar date (UTC). Returns the verified spend count, total USD cents, and a cryptographic signature from the Crinkl authority. Each daily GMV token is independently verifiable using the issuer's Ed25519 public key.
Parameters (1)
- datestringrequired
UTC date in YYYY-MM-DD format
get-trailing-gmv
Get a rolling N-day GMV trend summary. Returns daily verified GMV figures for the trailing window, enabling trend analysis of verified commerce volume. Each day's figure is backed by individually signed spend attestation tokens.
Parameters (1)
- daysnumber
Number of trailing days (default 7, max 90)
get-spend-signals
Get recent verified spend activity signals from the Crinkl network. Each signal represents a cryptographically attested receipt that has passed OCR extraction, store resolution, and hard verification. Signals include store name, category (e.g. Grocery & Supermarkets, Gas & Convenience), CBSA metro code, and spend amount — but no personally identifiable information. Use resolve-cbsa to convert CBSA codes to metro area names.
Parameters (1)
- limitnumber
Number of recent signals to return (default 20, max 50)
resolve-cbsa
Resolve a CBSA (Core Based Statistical Area) code to its metro area name. CBSA codes appear in spend signals and distribution data as 5-digit codes (e.g. '35620'). This tool converts them to human-readable names (e.g. '35620' → 'New York-Newark-Jersey City, NY-NJ'). Also handles non-metro codes like 'non-metro:US-TN'.
Parameters (1)
- codestringrequired
The CBSA code to resolve (e.g. '35620' or 'non-metro:US-TX')
get-merchant-summary
Get aggregated merchant and category distribution across all verified spends. Shows top store brands, category breakdown (grocery, restaurant, gas, etc.), and spend concentration metrics. All data is derived from cryptographically verified receipt attestations.
No parameters.
get-spend-distribution
Get the geographic and category distribution of verified spends over a trailing window. Returns a breakdown by store category and CBSA (Core Based Statistical Area) metro code, enabling analysis of where and how verified commerce is distributed across the United States.
Parameters (1)
- daysnumber
Number of trailing days (default 7, max 90)
get-settlement-summary
Get Bitcoin settlement statistics for the Crinkl network. Returns the current BTC price used for reward calculations, sats-per-receipt rate, total Lightning Network payouts, total sats claimed by users, and wallets with balance. Crinkl settles receipt rewards in real Bitcoin via Lightning Network — this endpoint shows the on-chain settlement layer metrics.
No parameters.
get-gmv-inclusion-proof
Get a Merkle inclusion proof that a specific spend is included in a daily GMV total. Returns the spend leaf hash, sibling hashes for the Merkle path, and the GMV root hash. This cryptographic proof allows anyone to independently verify that a spend was counted in the reported GMV without trusting the server.
Parameters (1)
- spendIdstringrequired
The spend ID (UUID) to get an inclusion proof for
verify-reward-commitment
Verify a reward commitment token's cryptographic integrity. Checks that the reward Merkle tree is valid, the batch signature is authentic, and the reward amounts match the committed values. Reward commitments bind point/sat allocations to specific spends before payout, preventing retroactive manipulation.
Parameters (1)
- tokenobjectrequired
The full reward commitment token JSON object to verify
verify-issued-gmv
Perform full end-to-end verification of a spend's inclusion in verified GMV. Accepts a spend attestation token, GMV token, GMV inclusion proof, and reward commitment token, then verifies: (1) spend token signature is valid, (2) GMV token signature is valid, (3) spend is in the GMV Merkle tree, (4) reward commitment is valid, (5) all spend IDs match across artifacts. This is the strongest possible verification — a single call that proves a receipt's entire journey from scan to settlement.
Parameters (5)
- spendTokenobjectrequired
The spend attestation token
- gmvTokenobjectrequired
The observed GMV token for the spend's date
- gmvInclusionProofobjectrequired
The Merkle inclusion proof
- rewardCommitmentTokenobjectrequired
The reward commitment token
- batchAnchorobject
Optional batch anchor for on-chain verification
get-recent-issued-proofs
Get recently issued proof bundles that demonstrate end-to-end verifiability. Each bundle contains a spend attestation token, GMV inclusion proof, and reward commitment — everything needed to independently verify a receipt's journey from scan to Bitcoin settlement. These are real production proofs, not test data. Note: rewardCommitmentToken and batchAnchor may be null for recent spends because reward commitments are batched asynchronously (typically within hours). The spend token and GMV inclusion proof are always present and independently verifiable. Check the 'steps' array and 'ok' field for per-step verification results.
Parameters (1)
- limitnumber
Number of recent proofs to return (default 10, max 50)
get-issuer-keys
Get the Crinkl authority's Ed25519 public key used to sign all attestation tokens. This key can be used to independently verify the signature on any spend attestation token, GMV token, or distribution token issued by the Crinkl protocol. The key is returned in base64 format.
No parameters.
get-reward-policy
Get the current Crinkl reward policy. Returns the active policy version, SHA-256 policy hash, reward parameters (referral bonuses, base points), category multipliers (grocery 1.5×, dining 1.5×, etc.), $CRINKL token holding tier multipliers, and the latest reserve checkpoint (BTC price, sats/receipt, coverage ratio). All values are deterministic — the policy hash covers the full parameter set. Updated daily.
No parameters.
get-agent-capabilities
Get Crinkl's canonical external agent capability catalog. Returns the live authority levels, the delegated agent capability set, the human-only governance controls, the approval boundaries, the current delegation model, and each gateway/MCP capability with its route, tool name, and source of truth.
No parameters.
get-vendors
Get the currently approved DKIM vendor domains exposed by the public agent endpoint. Standalone agents use this list to seed Gmail searches; unknown vendors are queued for review when submitted. No authentication required.
No parameters.
pair-agent
Start the human-authorized agent pairing flow. Generates a 4-character code that a human approves in the Crinkl PWA to authorize the agent. Returns the code and expiration time (10 minutes). No authentication required.
Parameters (1)
- deviceTokenstringrequired
A random 64-character hex string. Store this — needed to claim the API key.
claim-api-key
Poll for the API key after the human approves the pairing code in the Crinkl PWA. Returns 202 while pending, 200 with the API key once approved, 410 if expired. Poll every 5 seconds. No authentication required.
Parameters (2)
- deviceTokenstringrequired
The same deviceToken used in pair-agent.
- codestringrequired
The 4-character pairing code returned by pair-agent.
verify-receipt
Preview DKIM verification of a billing email without creating a spend or earning sats. Returns extracted invoice data (vendor, amount, date, DKIM status). The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes — the signature cannot be verified without them. The email is discarded after verification.
Parameters (2)
- apiKeystringrequired
Your Crinkl agent API key (crk_...).
- emlstringrequired
The raw billing email, base64-encoded. Required for DKIM signature verification.
submit-receipt
Submit a DKIM-verified billing email to mint a spend token and earn sats. The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes. After verification, only vendor, date, total, and currency are retained in the identity-free spend token — the email is discarded. Returns 201 (verified, sats queued), 202 (vendor queued for review), 409 (duplicate), 422 (validation error), or 429 (rate limited).
Parameters (2)
- apiKeystringrequired
Your Crinkl agent API key (crk_...).
- emlstringrequired
The raw billing email, base64-encoded. Required for DKIM signature verification.
get-agent-me
Get your agent's submission count, earned sats, and wallet-level stats. Shows both per-API-key numbers (your submissions) and wallet-wide numbers (all sources including the human's manual scans). Returns satsPerReceipt (current rate).
Parameters (1)
- apiKeystringrequired
Your Crinkl agent API key (crk_...).
README not available yet.
Install
claude_desktop_config.json
{
"mcpServers": {
"crinkl-commerce": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.crinkl.xyz/mcp"
]
}
}
}Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.