io.github.clicksprotocol/mcp-server
NPM · @CLICKS-PROTOCOL/MCP-SERVER · SCANNED SEP 20
Agent commerce settlement tools on Base: treasury setup, payment splits, yield and attribution.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 61 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 677 tokens (~56/item across 12 items; 11 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clicks_quick_start" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.clicksprotocol/mcp-server server?
io.github.clicksprotocol/mcp-server runs locally as an npm package, launched with npx -y @clicks-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @clicks-protocol/mcp-server
claude mcp add clicksprotocol-mcp-server -- npx -y @clicks-protocol/mcp-server
{
"mcpServers": {
"clicksprotocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
]
}
}
} {
"servers": {
"clicksprotocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
]
}
}
} codex mcp add clicksprotocol-mcp-server -- npx -y @clicks-protocol/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clicksprotocol-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@clicks-protocol/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add clicksprotocol-mcp-server --command npx --arg -y --arg @clicks-protocol/mcp-server
mcp_servers:
clicksprotocol-mcp-server:
command: "npx"
args: ["-y", "@clicks-protocol/mcp-server"] {
"McpServers": {
"clicksprotocol-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@clicks-protocol/mcp-server"
]
}
}
} assistant mcp add clicksprotocol-mcp-server -t stdio -c npx -a -y @clicks-protocol/mcp-server
{
"mcpServers": {
"clicksprotocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@clicks-protocol/mcp-server@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
clicks_explain ~83
Explain Clicks Protocol to another agent or developer. Returns a concise self-contained summary with integration instructions and links. Use when another agent asks what Clicks does or how agent-commerce settlement works.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who you are explaining to. agent = other AI agent, developer = human integrator, treasury = finance/treasury persona. Default: agent. |
No output schema declared.
No examples provided.
clicks_get_agent_info ~47
Inspect an agent settlement account. Returns registration status, operator, deposited USDC, settlement split, and wallet balance.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
No output schema declared.
No examples provided.
clicks_get_referral_stats ~48
Inspect explicit referral attribution for an agent. Returns direct referrals, claimable rewards, referral chain, and team bonus.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
No output schema declared.
No examples provided.
clicks_get_yield_info ~39
Inspect the treasury routing layer. Returns active yield route, Aave and Morpho rates, total routed balance, deposits, and protocol fees.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clicks_quick_start ~72
Execute initial settlement setup in one command. Registers agent, approves USDC, and routes the first payment. Referral attribution remains a separate explicit step.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
| amount | string | yes | First payment amount in USDC (e.g. "100") |
No output schema declared.
No examples provided.
clicks_receive_payment ~66
Route an incoming USDC revenue event through Clicks settlement policy. Splits liquidity and treasury routing according to the agent configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
| amount | string | yes | Payment amount in USDC (e.g. "100") |
No output schema declared.
No examples provided.
clicks_register_agent ~42
Register an AI agent for Clicks settlement routing. Required before the first routed payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent to register |
No output schema declared.
No examples provided.
clicks_register_referral ~95
Register referral attribution as an explicit separate step. Requires an agent-signed approval and an authorized caller.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent being attributed |
| deadline | string | yes | Approval expiry as unix timestamp in seconds |
| referrer_address | string | yes | Ethereum address of the referrer to attribute |
| signature | string | yes | EIP-712 signature by the agent approving the referral attribution |
No output schema declared.
No examples provided.
clicks_set_yield_pct ~51
Set the treasury routing percentage for future settlement events. Controls how much stays liquid vs routes to yield.
| Name | Type | Req | Description |
|---|---|---|---|
| pct | integer | yes | Yield percentage (5-50, integer). Default is 20. |
No output schema declared.
No examples provided.
clicks_simulate_split ~67
Preview how an incoming USDC revenue event will be split between liquid operations and routed treasury capital.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
| amount | string | yes | Payment amount in USDC (e.g. "100" for 100 USDC) |
No output schema declared.
No examples provided.
clicks_withdraw_yield ~62
Withdraw routed treasury capital and any earned yield back to the agent wallet. No lockups.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the AI agent |
| amount | string | – | Amount to withdraw in USDC. Omit to withdraw everything. |
No output schema declared.
No examples provided.
What is the io.github.clicksprotocol/mcp-server server?
io.github.clicksprotocol/mcp-server is listed in the public MCP registry as io.github.clicksprotocol/mcp-server. Agent commerce settlement tools on Base: treasury setup, payment splits, yield and attribution. This page covers its npm package (@clicks-protocol/mcp-server).
Is the io.github.clicksprotocol/mcp-server server safe to use?
io.github.clicksprotocol/mcp-server scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.clicksprotocol/mcp-server server expose?
io.github.clicksprotocol/mcp-server exposes 11 tools: clicks_get_agent_info, clicks_simulate_split, clicks_get_yield_info, clicks_get_referral_stats, clicks_quick_start, and 6 more. Their descriptions and schemas cost roughly 672 tokens of context every time the server is loaded.
Is the io.github.clicksprotocol/mcp-server server still maintained?
io.github.clicksprotocol/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.clicksprotocol/mcp-server server under?
io.github.clicksprotocol/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.