mcpField
C
Clicks Protocol

Clicks Protocol

Local
github.com/clicks-protocolDeveloper Tools2Updated 14w ago
Repository

About Clicks Protocol

Clicks Protocol provides MCP tools for inspecting and reconciling agent-commerce settlements on Base. Developers can verify receipts and review settlement evidence without exposing a private key to read-only operations.

Key features

  1. 01Verify Receipt V2 integrity
  2. 02Inspect settlement status and witnesses
  3. 03Reconcile Base evidence without submitting
  4. 04Compare receipt-bound policy hashes
  5. 05Inspect configured receipt ledger

Use cases

  1. 01Check whether a settlement receipt is intact
  2. 02Review evidence before retrying a settlement
  3. 03Compare a receipt with its policy definition

MCP support

The MCP server exposes nine tools, including Receipt V2 read tools for verification, status, reconciliation, policy comparison, and ledger inspection. Write tools require CLICKS_PRIVATE_KEY; read tools accept receipt JSON and do not require a private key.

#defi#yield#usdc#base#ai-agents#x402#morpho#aave#mcp#crypto

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "clicks-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@clicks-protocol/mcp-server"
      ],
      "env": {
        "CLICKS_PRIVATE_KEY": "<CLICKS_PRIVATE_KEY>",
        "CLICKS_RPC_URL": "<CLICKS_RPC_URL>"
      }
    }
  }
}
Run commandnpx -y @clicks-protocol/mcp-server
Environment variables to set
CLICKS_PRIVATE_KEYSecretPrivate key for write operations (register, deposit, withdraw). Not needed for read-only tools.
CLICKS_RPC_URLBase RPC URL. Defaults to https://mainnet.base.org

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@clicks-protocol/mcp-server0.3.2

Tools

11

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
agent_addressstringYesEthereum address of the AI agent

Details

From the project README

Clicks Protocol MCP Server

MCP tools for agent-commerce settlement routing and inspection on Base.

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.