Clicks Protocol MCP server
✓ VerifiedEnables AI agents to perform commerce settlement routing, receipt verification, and transaction inspection on the Base network.
Also known as clicks-protocol/clicks-protocol, @clicks-protocol/mcp-server
- Stars
- 2
- Tools
- 5
- Downloads, 30 days
- 232
- Latest version
- 1.0.3
- Last commit
- Jul 21, 2026
- License
- MIT
What is Clicks Protocol MCP?
Clicks Protocol enables AI agents to perform commerce settlement routing, receipt verification, and transaction inspection on the Base network. It exposes 5 tools, such as clicks_verify_receipt, clicks_get_settlement_status, clicks_reconcile_settlement.
Summary generated from the project's README
About Clicks Protocol MCP server
Managing commerce settlement and transaction inspection on the Base network becomes possible for AI agents using this server. It provides specialized tools to verify Receipt V2 integrity and inspect settlement statuses, including witnesses and retry policies. Developers can use these tools to reconcile settlements by reading Base evidence and proposing fail-closed states without the risk of the server automatically submitting or retrying transactions.
Users can configure a local append-only ledger by setting the CLICKS_RECEIPT_LEDGER_PATH environment variable to enable receipt trail inspection. While the read-only Receipt V2 tools function by accepting a complete receipt JSON object directly without needing a private key, write tools require a CLICKS_PRIVATE_KEY. Because of this requirement, it is important to keep write-enabled instances isolated from public or untrusted clients to maintain security boundaries.
Written from the project's README. Every use case is checked against a quote from it.
How to install Clicks Protocol MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Clicks Protocol MCP in Claude Code
$ claude mcp add --env 'CLICKS_PRIVATE_KEY=<YOUR_CLICKS_PRIVATE_KEY>' mcp-server -- npx -y @clicks-protocol/mcp-serverInstall Clicks Protocol MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
],
"env": {
"CLICKS_PRIVATE_KEY": "<YOUR_CLICKS_PRIVATE_KEY>"
}
}
}
}Install Clicks Protocol MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
],
"env": {
"CLICKS_PRIVATE_KEY": "<YOUR_CLICKS_PRIVATE_KEY>"
}
}
}
}Install Clicks Protocol MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@clicks-protocol/mcp-server"],"env":{"CLICKS_PRIVATE_KEY":"<YOUR_CLICKS_PRIVATE_KEY>"}}'Install Clicks Protocol MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
],
"env": {
"CLICKS_PRIVATE_KEY": "<YOUR_CLICKS_PRIVATE_KEY>"
}
}
}
}Install Clicks Protocol MCP in Codex
$ codex mcp add mcp-server --env 'CLICKS_PRIVATE_KEY=<YOUR_CLICKS_PRIVATE_KEY>' -- npx -y @clicks-protocol/mcp-serverInstall Clicks Protocol MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@clicks-protocol/mcp-server"] [mcp_servers.mcp-server.env] CLICKS_PRIVATE_KEY = "<YOUR_CLICKS_PRIVATE_KEY>"
Install Clicks Protocol MCP in Gemini CLI
$ gemini mcp add -s user -e 'CLICKS_PRIVATE_KEY=<YOUR_CLICKS_PRIVATE_KEY>' mcp-server npx -- -y @clicks-protocol/mcp-serverInstall Clicks Protocol MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
],
"env": {
"CLICKS_PRIVATE_KEY": "<YOUR_CLICKS_PRIVATE_KEY>"
}
}
}
}Clicks Protocol MCP tools 5
Detected from the READMEclicks_verify_receiptclicks_get_settlement_statusclicks_reconcile_settlementclicks_replay_policyclicks_get_receipt_trail
| clicks_verify_receipt | — | |
| clicks_get_settlement_status | — | |
| clicks_reconcile_settlement | — | |
| clicks_replay_policy | — | |
| clicks_get_receipt_trail | — |
Configuration
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
| Name | Description | |
|---|---|---|
| CLICKS_PRIVATE_KEY | Private key for write operations (register, deposit, withdraw). Not needed for read-only tools. | Secret |
| CLICKS_RPC_URL | Base RPC URL. Defaults to https://mainnet.base.org |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableclicks-protocol/clicks-protocol is public and reachablegithub.com/clicks-protocol/clicks-protocol ↗Pass
- Package names this repository as its source@clicks-protocol/mcp-server names clicks-protocol/clicks-protocol as sourcenpmjs.com/package/@clicks-protocol/mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-07-21github.com/clicks-protocol/clicks-protocol ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @clicks-protocol/mcp-serverPass
- No critical advisory in the package or its dependencies108 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model5 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubClicks 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.
Clicks Protocol MCP questions
How do I add Clicks Protocol MCP to Claude Code?
Run claude mcp add --env 'CLICKS_PRIVATE_KEY=<YOUR_CLICKS_PRIVATE_KEY>' mcp-server -- npx -y @clicks-protocol/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Clicks Protocol MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Clicks Protocol MCP provide?
It exposes 5 tools, including clicks_verify_receipt, clicks_get_settlement_status, clicks_reconcile_settlement, clicks_replay_policy, clicks_get_receipt_trail.
Do I need a private key for all tools?
No, the Receipt V2 tools accept a complete receipt JSON object directly and do not require a private key.
How can I use receipt-trail inspection?
You can enable receipt-trail inspection by setting the CLICKS_RECEIPT_LEDGER_PATH environment variable.
What is the safety boundary for receipt hashes?
A receipt hash only proves object integrity; it does not guarantee delivery or commercial intent.
Do write tools require authentication?
Yes, write tools require a CLICKS_PRIVATE_KEY and should be kept isolated from untrusted clients.