_ registry / mcp + a2a streamable-http · checked 2h ago

clicks-protocol

https://clicksprotocol.xyz

Registry code: dadb56d674fb843b

api record

Autonomous yield layer for AI agents on Base. Auto-splits USDC deposits 80/20: 80% liquid, 20% earning via Morpho (~13% APY) or Aave V3. No lockup, 2% fee on yield only. SDK, MCP Server (9 tools), HTTP API. [GitHub](https://github.com/clicks-protocol/clicks-protocol) | [npm](https://www.npmjs.com/package/@clicks-protocol/sdk) | [MCP](https://www.npmjs.com/package/@clicks-protocol/mcp-server)

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.clicksprotocol.xyz/mcp
door code
db1f1e2bb7169678
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is clicks-protocol live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is clicks-protocol free to use?
Yes — the hub reached it with no key and no payment.
What tools does clicks-protocol have?
4 tools: clicks_simulate_split, clicks_get_referral_stats, clicks_get_agent_info, clicks_get_yield_info.
Is clicks-protocol safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.8%

latency
155ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 619 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain trading & defi
used for
  • get agent deposit and yield info
  • get current yield apys
  • preview usdc payment split
  • get referral stats
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • clicks_get_yield_info reads open 11h ago

    Get current yield protocol information: active protocol (Aave or Morpho), APYs, total balance, and total deposited across all agents.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • clicks_simulate_split reads unknown never probed

    Preview how a USDC payment would be split for an agent: how much goes to wallet (liquid) and how much to DeFi yield.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount",
    "agent_address"
  ],
  "properties": {
    "amount": {
      "type": "string",
      "description": "Payment amount in USDC (e.g. \"100\" for 100 USDC)"
    },
    "agent_address": {
      "type": "string",
      "description": "Ethereum address of the AI agent"
    }
  }
}
    arguments 17 lines
  • clicks_get_referral_stats reads unknown 11h ago

    Get referral network stats for an agent: direct referrals count, total earned from referrals, claimable rewards, and referral chain.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agent_address"
  ],
  "properties": {
    "agent_address": {
      "type": "string",
      "description": "Ethereum address of the AI agent"
    }
  }
}
    arguments 12 lines
  • clicks_get_agent_info reads unknown 11h ago

    Get comprehensive info about an AI agent registered with Clicks Protocol: registration status, operator, deposited principal, yield percentage, and USDC balance.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agent_address"
  ],
  "properties": {
    "agent_address": {
      "type": "string",
      "description": "Ethereum address of the AI agent"
    }
  }
}
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id dadb56d674fb843b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dadb56d674fb843b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/dadb56d674fb843b/badge.svg)](https://brick.blue/agent/dadb56d674fb843b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.