Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/clicks-protocol/clicks-protocol/mcp-mcp-servergit clone --depth 1 https://github.com/clicks-protocol/clicks-protocolWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/clicks-protocol/clicks-protocol/mcp-mcp-server)<a href="https://agentmods.dev/mcp/clicks-protocol/clicks-protocol/mcp-mcp-server"><img src="https://agentmods.dev/badge/mcp/clicks-protocol/clicks-protocol/mcp-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicks-protocol/mcp-server"
],
"env": {
"CLICKS_PRIVATE_KEY": "",
"CLICKS_RPC_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 13 lines scan A 1064932913c6
mcp-server is an MCP server published in the GitHub repository clicks-protocol/clicks-protocol (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
flashbank
Fixed-fee P2P term loans (no oracles) and flash loans on Ethereum, Base, Arbitrum and Sepolia. Runs locally from the @flashbank/mcp npm package. Needs 3 environment variables to run.
mcp-blockchain
MCP server "mcp-blockchain" as configured in shubhamdusane/mcp-blockchain. Runs locally from the mcp-blockchain npm package.
aegis-defi
A safety layer for autonomous DeFi agents - MCP server + smart contracts that simulate, scan, and protect on-chain transactions before execution. Runs locally from the aegis-defi npm package.
warden402-mcp
Pre-execution safety for AI agents on Base. Guard a token, tx or address: block/review/clear. Runs locally from the warden402-mcp npm package. Needs 1 environment variable to run.
pumpclaw
Free token launcher on Base. Deploy ERC-20 tokens via Uniswap V4 with 80% creator fees. Runs locally from the pumpclaw-mcp npm package. Needs 2 environment variables to run.
base-wallet-toolkit
MCP server for Base wallet interactions: balances, gas, tokens, allowances, ENS. Runs locally from the base-wallet-toolkit-mcp npm package. Needs 1 environment variable to run.