Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Crinkl Commerce MCP

REMOTE · MCP.CRINKL.XYZ · SCANNED AUG 3

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

Available components

+3 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2102 tokens (~95/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.crinkl.xyz

# add to Claude Code
claude mcp add --transport http xyz-crinkl-mcp-crinkl-commerce https://mcp.crinkl.xyz/mcp
# ~/.codex/config.toml
[mcp_servers.xyz-crinkl-mcp-crinkl-commerce]
url = "https://mcp.crinkl.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-crinkl-mcp-crinkl-commerce": {
      "type": "remote",
      "url": "https://mcp.crinkl.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-crinkl-mcp-crinkl-commerce --url https://mcp.crinkl.xyz/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-crinkl-mcp-crinkl-commerce:
    url: "https://mcp.crinkl.xyz/mcp"
// mcp.json
{
  "mcpServers": {
    "xyz-crinkl-mcp-crinkl-commerce": {
      "type": "http",
      "url": "https://mcp.crinkl.xyz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.crinkl.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=crinkl.xyz CN=WE1,O=Google Trust Services,C=US 14 Jun 2026 12 Sept 2026 ECDSA 256 ECDSA-SHA256 1d8c964bae52c67913d7d1bd14f8617a
SANs: crinkl.xyz, *.crinkl.xyz
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.crinkl.xyz. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
crinkl.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.crinkl.xyz/mcp Verified 200
http (plaintext) http://mcp.crinkl.xyz/mcp HTTPS enforced 301 https://mcp.crinkl.xyz/mcp
MCP tools — 22 exposed · ~2,102 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
claim-api-key ~91

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.

NameTypeReqDescription
codestringyesThe 4-character pairing code returned by pair-agent.
deviceTokenstringyesThe same deviceToken used in pair-agent.

No output schema declared.

No examples provided.

get-agent-capabilities ~59

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-agent-me ~76

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

NameTypeReqDescription
apiKeystringyesYour Crinkl agent API key (crk_...).

No output schema declared.

No examples provided.

get-cumulative-gmv ~128

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.

NameTypeReqDescription
asOfDatestringOptional ISO date to compute GMV as of (defaults to now)
startDatestringOptional ISO date (YYYY-MM-DD) to start counting from. The live beta cumulative feed uses 2026-01-27.

No output schema declared.

No examples provided.

get-daily-gmv ~79

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.

NameTypeReqDescription
datestringyesUTC date in YYYY-MM-DD format

No output schema declared.

No examples provided.

get-gmv-inclusion-proof ~96

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.

NameTypeReqDescription
spendIdstringyesThe spend ID (UUID) to get an inclusion proof for

No output schema declared.

No examples provided.

get-issuer-keys ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-merchant-summary ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-protocol-summary ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-recent-issued-proofs ~136

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.

NameTypeReqDescription
limitnumberNumber of recent proofs to return (default 10, max 50)

No output schema declared.

No examples provided.

get-reward-policy ~104

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-settlement-summary ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-spend-distribution ~77

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.

NameTypeReqDescription
daysnumberNumber of trailing days (default 7, max 90)

No output schema declared.

No examples provided.

get-spend-signals ~115

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.

NameTypeReqDescription
limitnumberNumber of recent signals to return (default 20, max 50)

No output schema declared.

No examples provided.

get-trailing-gmv ~72

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.

NameTypeReqDescription
daysnumberNumber of trailing days (default 7, max 90)

No output schema declared.

No examples provided.

get-vendors ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pair-agent ~77

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.

NameTypeReqDescription
deviceTokenstringyesA random 64-character hex string. Store this — needed to claim the API key.

No output schema declared.

No examples provided.

resolve-cbsa ~126

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

NameTypeReqDescription
codestringyesThe CBSA code to resolve (e.g. '35620' or 'non-metro:US-TX')

No output schema declared.

No examples provided.

submit-receipt ~152

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

NameTypeReqDescription
apiKeystringyesYour Crinkl agent API key (crk_...).
emlstringyesThe raw billing email, base64-encoded. Required for DKIM signature verification.

No output schema declared.

No examples provided.

verify-issued-gmv ~215

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.

NameTypeReqDescription
batchAnchorobjectOptional batch anchor artifact. When omitted, verification is portable artifact verification only.
gmvInclusionProofobjectyesThe Merkle inclusion proof
gmvTokenobjectyesThe observed GMV token for the spend's date
rewardCommitmentTokenobjectyesThe reward commitment token
spendTokenobjectyesThe spend attestation token

No output schema declared.

No examples provided.

verify-receipt ~120

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.

NameTypeReqDescription
apiKeystringyesYour Crinkl agent API key (crk_...).
emlstringyesThe raw billing email, base64-encoded. Required for DKIM signature verification.

No output schema declared.

No examples provided.

verify-reward-commitment ~81

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.

NameTypeReqDescription
tokenobjectyesThe full reward commitment token JSON object to verify

No output schema declared.

No examples provided.