Clicks Protocol MCP Server

The io.github.clicksprotocol/mcp-server provides MCP tools for agent-commerce settlement routing and inspection on Base. It focuses on treasury setup, payment splits, yield, and attribution, and exposes Receipt V2 read and inspection capabilities for deterministic verification and reconciliation without transaction submission.

🛠️ Key Features

Receipt V2 read tools for settlement inspection on Base
clicks_verify_receipt: verifies deterministic Receipt V2 integrity
clicks_get_settlement_status: reads state, witnesses, and retry policy
clicks_reconcile_settlement: reads Base evidence and proposes a fail-closed state (no submission or retries)
clicks_replay_policy: compares a policy definition with the policy hash bound to a receipt
clicks_get_receipt_trail: reads matching versions from a configured local append-only l

🚀 Use Cases

Verifying agent-commerce settlement routing outcomes on Base
Reading settlement state, witnesses, and retry policy for receipt handling
Reconciling settlements using fail-closed proposals from on-chain evidence

⚡ Developer Benefits

Deterministic receipt integrity checks via clicks_verify_receipt
Policy hash validation for Receipt V2 replay via clicks_replay_policy
Local receipt trail inspection using clicks_get_receipt_trail

⚠️ Limitations

Reconciliation tool proposes fail-closed state but never submits or retries transactions.

Receipt V2 read tools

clicks_verify_receipt: verifies deterministic Receipt V2 integrity.

clicks_get_settlement_status: reads state, witnesses and retry policy.

clicks_reconcile_settlement: reads Base evidence and proposes a fail-closed state. It never submits or retries a transaction.

clicks_replay_policy: compares an exact policy definition with the policy hash bound to a receipt.

clicks_get_receipt_trail: reads matching versions from a configured local append-only ledger.

Set CLICKS_RECEIPT_LEDGER_PATH to use receipt-trail inspection. The other Receipt V2 tools accept a complete receipt JSON object directly and do not require a private key.

Safety boundary

Receipt hash validity proves object integrity only. It does not prove delivery or commercial intent. Missing RPC data is treated as unknown, not as proof that no transaction was submitted. Only the SDK state failed_before_transfer, established with independent evidence, can permit a bounded retry.

Write tools still require CLICKS_PRIVATE_KEY. Keep write-enabled MCP servers isolated from public or untrusted clients.

Install

Configuration

Environment variables

CLICKS_PRIVATE_KEYsecret

Private key for write operations (register, deposit, withdraw). Not needed for read-only tools.

CLICKS_RPC_URL

Base RPC URL. Defaults to https://mainnet.base.org

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@clicks-protocol/mcp-server@0.3.2"
      ],
      "env": {
        "CLICKS_PRIVATE_KEY": "<YOUR_CLICKS_PRIVATE_KEY>",
        "CLICKS_RPC_URL": "<YOUR_CLICKS_RPC_URL>"
      }
    }
  }
}

io.github.clicksprotocol/mcp-server

Clicks Protocol MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

Clicks Protocol MCP Server

Receipt V2 read tools

Safety boundary

Install

Configuration

Related servers