# Crinkl Commerce MCP (remote · mcp.crinkl.xyz)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.crinkl.xyz`: 67/100 (this document), [markdown](https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp.md), [page](https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp)

## Channel facts

- Endpoint: `https://mcp.crinkl.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2102 tokens (~95/item across 22 items; 22 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http xyz-crinkl-mcp-crinkl-commerce https://mcp.crinkl.xyz/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-crinkl-mcp-crinkl-commerce --url https://mcp.crinkl.xyz/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-crinkl-mcp-crinkl-commerce:
    url: "https://mcp.crinkl.xyz/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +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.

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +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.

### 2026-07-28 (score 65, +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.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (22)

### `get-protocol-summary` (~55 tokens)

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.

### `get-cumulative-gmv` (~128 tokens)

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.

Input parameters:

- `asOfDate` (string): Optional ISO date to compute GMV as of (defaults to now)
- `startDate` (string): Optional ISO date (YYYY-MM-DD) to start counting from. The live beta cumulative feed uses 2026-01-27.

### `get-daily-gmv` (~79 tokens)

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.

Input parameters:

- `date` (string, required): UTC date in YYYY-MM-DD format

### `get-trailing-gmv` (~72 tokens)

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.

Input parameters:

- `days` (number): Number of trailing days (default 7, max 90)

### `get-spend-signals` (~115 tokens)

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.

Input parameters:

- `limit` (number): Number of recent signals to return (default 20, max 50)

### `resolve-cbsa` (~126 tokens)

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

Input parameters:

- `code` (string, required): The CBSA code to resolve (e.g. '35620' or 'non-metro:US-TX')

### `get-merchant-summary` (~55 tokens)

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.

### `get-spend-distribution` (~77 tokens)

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.

Input parameters:

- `days` (number): Number of trailing days (default 7, max 90)

### `get-settlement-summary` (~70 tokens)

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.

### `get-gmv-inclusion-proof` (~96 tokens)

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.

Input parameters:

- `spendId` (string, required): The spend ID (UUID) to get an inclusion proof for

### `verify-reward-commitment` (~81 tokens)

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.

Input parameters:

- `token` (object, required): The full reward commitment token JSON object to verify

### `verify-issued-gmv` (~215 tokens)

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.

Input parameters:

- `batchAnchor` (object): Optional batch anchor artifact. When omitted, verification is portable artifact verification only.
- `gmvInclusionProof` (object, required): The Merkle inclusion proof
- `gmvToken` (object, required): The observed GMV token for the spend's date
- `rewardCommitmentToken` (object, required): The reward commitment token
- `spendToken` (object, required): The spend attestation token

### `get-recent-issued-proofs` (~136 tokens)

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.

Input parameters:

- `limit` (number): Number of recent proofs to return (default 10, max 50)

### `get-issuer-keys` (~70 tokens)

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.

### `get-reward-policy` (~104 tokens)

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.

### `get-agent-capabilities` (~59 tokens)

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.

### `get-vendors` (~48 tokens)

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.

### `pair-agent` (~77 tokens)

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.

Input parameters:

- `deviceToken` (string, required): A random 64-character hex string. Store this — needed to claim the API key.

### `claim-api-key` (~91 tokens)

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.

Input parameters:

- `code` (string, required): The 4-character pairing code returned by pair-agent.
- `deviceToken` (string, required): The same deviceToken used in pair-agent.

### `verify-receipt` (~120 tokens)

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.

Input parameters:

- `apiKey` (string, required): Your Crinkl agent API key (crk_...).
- `eml` (string, required): The raw billing email, base64-encoded. Required for DKIM signature verification.

### `submit-receipt` (~152 tokens)

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

Input parameters:

- `apiKey` (string, required): Your Crinkl agent API key (crk_...).
- `eml` (string, required): The raw billing email, base64-encoded. Required for DKIM signature verification.

### `get-agent-me` (~76 tokens)

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

Input parameters:

- `apiKey` (string, required): Your Crinkl agent API key (crk_...).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://mcp.crinkl.xyz/mcp
- Website: https://www.crinkl.xyz/developers
- Changelog RSS feed: https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/xyz-crinkl-mcp-crinkl-commerce/mcp