Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • The install package comes from a different repo than this listing's
Own this project? Claim it
Clicks Protocol logo

Clicks Protocol

by clicks-protocol

Queries Base DeFi yield data, checks agent status, reads balances, and simulates projected earnings over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clicks Protocol

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-108": {
      "command": "npx",
      "args": [
        "-y",
        "hardhat"
      ],
      "env": {
        "CLICKS_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y hardhat

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The clicks-protocol/clicks-protocol MCP server exposes Clicks Protocol data and yield simulation capabilities for AI agents operating with USDC on Base. Its listed tools retrieve protocol statistics, verify agent registration, inspect an agent’s yield balance, and project earnings over time. Clicks routes payments through a configurable liquid/yield split and can use Aave V3 or Morpho for yield. Reach for it when an agent needs read-only visibility into Clicks treasury and yield activity or wants to estimate returns before taking action.

Use cases

  • Monitor Clicks Protocol TVL and APY
  • Check whether an agent is registered
  • Inspect an agent’s yield balance
  • Estimate earnings before routing funds

Key features

  • Query protocol TVL, APY, and agent count
  • Check agent registration status
  • Read agent yield balances
  • Simulate projected yield earnings
  • Designed for USDC flows on Base

Tools4

What Clicks Protocol lets your agent do. Expand a tool for its parameters.

Self-reported~41 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · hardhat (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads1.9MPackage downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Clicks Protocol works

What clicks-protocol/clicks-protocol MCP server does

The clicks-protocol/clicks-protocol MCP server gives an MCP-compatible agent access to Clicks Protocol information for USDC flows on Base. The listed interface focuses on protocol metrics, agent registration, yield balances, and earnings projections rather than general blockchain queries.

Clicks Protocol is designed to split received USDC between an agent’s liquid wallet balance and a yield route. Withdrawals are described as available at any time, with a 2% fee applied to yield rather than principal.

How it works

An MCP client starts the server and sends tool calls through the Model Context Protocol. The server then exposes Clicks-specific operations for reading protocol state and running simulations. get_protocol_stats returns TVL, APY, and agent-count information. get_agent_info checks whether an agent address is registered. get_yield_info reports the yield balance associated with an agent, while simulate_yield estimates earnings over a selected period.

The underlying Clicks system runs on Base and uses USDC. The repository also documents a TypeScript SDK with payment splitting, agent registration, withdrawals, and yield-percentage configuration. Those SDK capabilities are separate from the four tools listed for this directory entry, so verify the installed MCP package and its tool manifest before relying on transaction or management operations.

Setup and configuration

Install the MCP package with npm and start its command-line server:

Terminal
npm install @clicks-protocol/mcp-server
CLICKS_PRIVATE_KEY=0x... clicks-mcp

CLICKS_PRIVATE_KEY is the documented environment variable for starting the server. A private key is sensitive credential material; provide it through the client’s secret-management or environment configuration rather than embedding it in prompts or source files.

Tools and capabilities

The clicks-protocol/clicks-protocol MCP server lists these capabilities:

  • Retrieve TVL, APY, and total agent count.
  • Check whether an agent is registered.
  • Inspect an agent’s yield balance.
  • Simulate projected yield earnings over time.

These tools suit monitoring, eligibility checks, and pre-deposit estimation.

Limitations and notes

Results depend on Clicks Protocol state and the Base deployment. APY and TVL can change, so simulations should be treated as estimates rather than guaranteed returns. The repository describes Aave V3 and Morpho routing, but the supplied MCP tool descriptions do not specify which inputs control routing or which fields are returned in every response.

This listing explicitly identifies four tools; confirm the version and published manifest if those additional operations are required. The repository states that its license is MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clicks Protocol

clicks-protocol/clicks-protocol is an MCP server that connects AI agents to Clicks Protocol’s USDC yield system on Base. Its listed tools retrieve protocol TVL, APY, and agent counts, check agent registration, read an agent’s yield balance, and simulate projected earnings over time.

Install it with `npm install @clicks-protocol/mcp-server`, then start it with `CLICKS_PRIVATE_KEY=0x... clicks-mcp`. The documented command uses the private key environment variable to configure the server.

It can query protocol TVL, APY, agent count, registration status, and an agent’s yield balance. It also provides a tool for simulating projected earnings over time.

It also names Claude, LangChain, and other MCP-compatible clients, although this listing does not provide client-specific configuration steps.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClicks Protocol AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-server-108?style=directory)](https://allmcps.com/mcp/mcp-server-108)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-server-108"><img src="https://allmcps.com/api/badge/mcp-server-108?style=directory" alt="Clicks Protocol on AllMCPs" /></a>