Crinkl Commerce MCP

xyz.crinkl.mcpPublished by mcp.crinkl.xyzOfficial publisherv1.1.0Updated Oct 24, 2026

Verified commerce data and proof-backed shopper activation tools for agents.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint offering verified commerce data and proof-backed shopper activation tools for AI agents.

What you can do
Crinkl Commerce MCP is a remote, streamable HTTP MCP server that provides verified commerce data and proof-backed shopper activation capabilities to an assistant. The registry describes it as offering commerce data and shopper activation tools, but no tool list, parameters, or usage details are published in the available material.
When to use it
Consider it when an assistant needs commerce data or shopper activation functionality and a hosted endpoint is acceptable. Because no tool list or documentation is available, evaluate it only after confirming its actual capabilities with the provider.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the endpoint at mcp.crinkl.xyz. The manifest declares no authentication, environment variables, or headers, and no packages are required.
Before you install
The manifest declares no authentication, so it is unclear how access is controlled or what data is exchanged. No tool list is published, so the exact actions the server can take, including any that write or send data, cannot be verified from the available material. Confirm data handling and permissions with the provider before use.

Installation

In SourceWeft

  1. Open Crinkl Commerce MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.crinkl.mcp%2Fcrinkl-commerce/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "crinkl-commerce": {
      "type": "http",
      "url": "https://mcp.crinkl.xyz/mcp"
    }
  }
}

Tools

22

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.

Takes 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.

ParametersasOfDatestartDate

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.

Parametersdaterequired

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.

Parametersdays

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.

Parameterslimit

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'.

Parameterscoderequired

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.

Takes 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.

Parametersdays

get-settlement-summary

Get reward settlement statistics for supported reward rails. Returns the current BTC price used for reward calculations, sats-per-receipt rate, reported Lightning Network payouts, total sats claimed by users, and wallets with balance. This endpoint reports settlement metrics; it is not a chain-finality or payout-proof verifier.

Takes 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.

ParametersspendIdrequired

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.

Parameterstokenrequired

verify-issued-gmv

Verify a supplied spend/GMV artifact bundle. 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 portable artifact verification; it does not by itself assert payout, chain finality, or validator quorum unless the supplied anchor or commitment artifacts are present and accepted by the route.

ParametersgmvTokenrequiredspendTokenrequiredbatchAnchorgmvInclusionProofrequiredrewardCommitmentTokenrequired

get-recent-issued-proofs

Get recent gateway-issued artifact bundles for portable spend/GMV verification. Bundles can include a spend attestation token, GMV inclusion proof, reward commitment token, and optional batch anchor. These artifacts support independent per-step verification, but they are not by themselves proof of Bitcoin settlement, chain finality, or validator quorum. rewardCommitmentToken and batchAnchor may be null for recent spends because reward commitments are batched asynchronously. Check the 'steps' array and 'ok' field for per-step verification results.

Parameterslimit

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.

Takes 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.

Takes no parameters.

get-agent-capabilities

Get Crinkl's canonical external agent capability catalog. Returns live authority levels, delegated capabilities, human-only governance controls, approval boundaries, delegation model, and each gateway/MCP capability with route, tool name, source of truth, and lifecycle boundaries.

Takes 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.

Takes 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.

ParametersdeviceTokenrequired

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.

ParameterscoderequireddeviceTokenrequired

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.

ParametersemlrequiredapiKeyrequired

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).

ParametersemlrequiredapiKeyrequired

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).

ParametersapiKeyrequired

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.