Clicksprotocol
io.github.clicksprotocolPublished by GitHub account clicksprotocolv1.0.3Updated Oct 27, 2026
Agent commerce settlement tools on Base: treasury setup, payment splits, yield and attribution.
Overview
MCP server for inspecting and reconciling Clicks Protocol agent-commerce settlement receipts on Base, with optional write tools for treasury operations.
- What you can do
- Verify receipt integrity and compare a policy definition against the policy hash bound to a receipt
- Read settlement state, witnesses and retry policy, and reconcile Base evidence into a proposed fail-closed state
- Inspect matching receipt versions from a configured local append-only ledger
- Register, deposit and withdraw through write tools that require a private key
- When to use it
- Useful when an assistant needs to check or reconcile Clicks Protocol settlement receipts on Base, audit a receipt trail, or carry out treasury operations such as registration, deposits and withdrawals.
- Requirements
- Runs locally over stdio from the npm package, so Node.js is needed. Read-only receipt tools accept a receipt JSON object and need no key; receipt-trail inspection needs CLICKS_RECEIPT_LEDGER_PATH. Write tools need CLICKS_PRIVATE_KEY, and CLICKS_RPC_URL sets the Base RPC endpoint (defaults to the public Base mainnet URL).
Installation
In SourceWeft
- Open Clicksprotocol in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
Source: mcp-server/README.md at commit f692403
Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts