YieldSignal MCP Server

Real-time risk-weighted USDC lending APY across 6 protocols on Base, paid via x402

Local serverstdio

What is the YieldSignal MCP server?

Real-time risk-weighted USDC lending APY across 6 protocols on Base, paid via x402. Exposed over MCP by the yieldsignal mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Risk-weighted yield signals for autonomous agents, paid per call via the x402 protocol — no API key, no signup. First 3 calls/day per IP are free via ?trial=1.

Its toolset

Everything the assistant can do here goes through one of these:

  • score — directional: was the flagged protocol still the leader (or within 25bps) when scored against the market right now
  • windowedScore — each attestation judged over its own validity window, i.e. until the next attestation for that asset replaced it. medianWindowHours is the

Configuration

You will need 2 environment variables: CDP_API_KEY_ID, WALLET_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. YieldSignal's toolset — score, windowedScore — is a fair guide to whether it matches your workflow. It is maintained by Stakemate369; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against YieldSignal's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the yieldsignal mcp server does with a few real requests.

Available tools

ToolWhat it does
scoredirectional: was the flagged protocol still the leader (or within 25bps) **when scored against the market right now**.
windowedScoreeach attestation judged over **its own validity window**, i.e. until the next attestation for that asset replaced it. medianWindowHours is the practical answer to "how often should I re-check?" and it differs sharply per

How to install the YieldSignal MCP server

{
  "mcpServers": {
    "yieldsignal": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "CDP_API_KEY_ID": "your-value",
        "WALLET_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CDP_API_KEY_IDCredential the server authenticates with.Yes
WALLET_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use YieldSignal to score.
  • Use YieldSignal to windowedScore.

Frequently asked questions

It connects YieldSignal to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (score, windowedScore) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with YieldSignal directly.