xyz.crinkl.mcp/crinkl-commerce

Est-ce que xyz.crinkl.mcp/crinkl-commerce est sûr ?

Au dernier audit MCP Hub, le serveur MCP « xyz.crinkl.mcp/crinkl-commerce » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 22 outils

• claim-api-key≈ 155 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • code · string · requis
    The 4-character pairing code returned by pair-agent.
  • deviceToken · string · requis
    The same deviceToken used in pair-agent.

  Exemple d'appel

  {"name": "claim-api-key", "arguments": {"code": "texte", "deviceToken": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-agent-capabilities≈ 110 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-agent-capabilities", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-agent-me≈ 130 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).

  Paramètres, retour & exemple (1)

  Paramètres

  • apiKey · string · requis
    Your Crinkl agent API key (crk_...).

  Exemple d'appel

  {"name": "get-agent-me", "arguments": {"apiKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-cumulative-gmv≈ 195 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "get-cumulative-gmv", "arguments": {"asOfDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-daily-gmv≈ 134 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    UTC date in YYYY-MM-DD format

  Exemple d'appel

  {"name": "get-daily-gmv", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-gmv-inclusion-proof≈ 156 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • spendId · string · requis
    The spend ID (UUID) to get an inclusion proof for

  Exemple d'appel

  {"name": "get-gmv-inclusion-proof", "arguments": {"spendId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-issuer-keys≈ 107 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-issuer-keys", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-merchant-summary≈ 105 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-merchant-summary", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-protocol-summary≈ 96 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-protocol-summary", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-recent-issued-proofs≈ 211 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · number · optionnel
    Number of recent proofs to return (default 10, max 50)

  Exemple d'appel

  {"name": "get-recent-issued-proofs", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-reward-policy≈ 141 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-reward-policy", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-settlement-summary≈ 122 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-settlement-summary", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-spend-distribution≈ 137 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · number · optionnel
    Number of trailing days (default 7, max 90)

  Exemple d'appel

  {"name": "get-spend-distribution", "arguments": {"days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-spend-signals≈ 178 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · number · optionnel
    Number of recent signals to return (default 20, max 50)

  Exemple d'appel

  {"name": "get-spend-signals", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-trailing-gmv≈ 125 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · number · optionnel
    Number of trailing days (default 7, max 90)

  Exemple d'appel

  {"name": "get-trailing-gmv", "arguments": {"days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-vendors≈ 93 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get-vendors", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pair-agent≈ 138 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • deviceToken · string · requis
    A random 64-character hex string. Store this — needed to claim the API key.

  Exemple d'appel

  {"name": "pair-agent", "arguments": {"deviceToken": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve-cbsa≈ 157 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'.

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    The CBSA code to resolve (e.g. '35620' or 'non-metro:US-TX')

  Exemple d'appel

  {"name": "resolve-cbsa", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit-receipt≈ 216 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).

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "submit-receipt", "arguments": {"eml": "texte", "apiKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify-issued-gmv≈ 363 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.

  Paramètres, retour & exemple (5)

  Paramètres

  • gmvToken · object · requis
    The observed GMV token for the spend's date
  • spendToken · object · requis
    The spend attestation token
  • batchAnchor · object · optionnel
    Optional batch anchor artifact. When omitted, verification is portable artifact verification only.
  • gmvInclusionProof · object · requis
    The Merkle inclusion proof
  • rewardCommitmentToken · object · requis
    The reward commitment token

  Exemple d'appel

  {"name": "verify-issued-gmv", "arguments": {"gmvToken": {}, "spendToken": {}, "gmvInclusionProof": {}, "rewardCommitmentToken": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify-receipt≈ 194 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "verify-receipt", "arguments": {"eml": "texte", "apiKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify-reward-commitment≈ 162 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • token · object · requis
    The full reward commitment token JSON object to verify

  Exemple d'appel

  {"name": "verify-reward-commitment", "arguments": {"token": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.crinkl.xyz/mcp