mcpbeat Sign in

YieldSignal MCP Server

not responding

YieldSignal is listed as active in the registry but did not answer our last check. It exposes 7 tools. Last commit 11 Aug 2026.

Yield & risk for agents: signal, decision, durability, capacity, sensitivity, exposure, persistence

Uptime history 48 days of history · worst day 0%
48 days agonow
60.4%
Uptime 24h
55 of 91 checks
7
Tools
read from the server
383 ms
Response time
average over 24h
0
Stars
last commit 11 Aug 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

10 Aug a tool appeared get_leadership_persistence

What the code does

We read the source, 22 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Long encoded blob in source src/favicon.ts:18
  "AAABAAEAICAAAAEAIACoEAAAFgAAACgAAAAgAAAAQAAAAAEAIAAAAAAAgBAAAAAAAAAAAAAAAAAAAAAAAAAOEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OEhj/DhIY/w4SGP8OE…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add yieldsignal --transport http https://yieldsignal.vercel.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "yieldsignal": {
      "url": "https://yieldsignal.vercel.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.yieldsignal]
url = "https://yieldsignal.vercel.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "yieldsignal": {
      "url": "https://yieldsignal.vercel.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "yieldsignal": {
      "url": "https://yieldsignal.vercel.app/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

yield
get_yield_decision
Buyer-side MOVE/HOLD decision (Layer 1 premium — sells the decision, not the raw datapoint). Given your current position, size, move cost and horizon, returns whether moving your capital to the best risk-adjusted protocol pays for itself now — with expected net gain, break-even days and a confidence tier. Deterministic from the underlying signal, which is EIP-712 signed and returned in a sibling content block (re-run the decision locally to reproduce it). Priced above the plain signal tool.
get_yield_durability
How much of the current APY survives if incentives stop. Splits each protocol's yield into base interest vs reward/incentive, reports the post-incentive floor, and says whether the leader changes without incentives. Only protocols whose source itemizes the reward component are decomposed — the rest are listed as undecomposable and NEVER assumed incentive-free, and no ranking claim is made when the current leader is one of them. Also returns bestVerifiableFloor: the highest yield provably independent of incentives. A stress test of readings taken now, not a forecast of when a campaign ends.
get_yield_signal
Real-time risk-weighted yield signal. USDC/WETH: lending APY on Base (Aave/Compound/Morpho read onchain, Moonwell/Euler/Fluid via DefiLlama). ETH_STAKING: liquid staking APY on Ethereum mainnet (Lido/Rocket Pool/Coinbase Wrapped Staked ETH/Frax Ether/Binance Staked ETH, all via DefiLlama) — a different chain and category from the lending signals, not a Base lending market. Source tagged per reading (never estimated). Result is signed (EIP-712 typed data) by the payment-receiving address, returned as a sibling content block for offline verification. That same address is registered on-chain as an ERC-8004 agent identity (agent-card.json) and periodically publishes EAS attestations of past readings (Base mainnet) — a public track record independent of this server's uptime.
exit
get_exit_capacity
Exit capacity for a Base lending market: per-protocol utilization and withdrawable liquidity read from the protocol's own books (Aave, Compound), plus — if you pass amountUsd — whether that size can be withdrawn right now and what share of the market it would be. High APY at high utilization means the market pays well and will not let you out; this tool separates the two. Protocols that do not expose borrowed-vs-supplied are marked unmeasured and are never recommended as executable. USDC only for USD figures; WETH returns utilization without USD (no price oracle in the paid path).
leadership
get_leadership_persistence
How long this service's own leadership calls actually hold, measured from its hourly on-chain attestations (EAS on Base). Returns the median duration a protocol stayed the best pick, survival rates at 6/24/72h, how much of the rotation is the same two protocols trading places, and what chasing the leader is worth per $10k before gas. Measured over 24 days: the WETH leader never changed once, the ETH staking leader changed every ~26h, the USDC leader every ~2h with half the switches being a round trip between the same pair — three assets sold at one price with wildly different reliability. Also answers, empirically, whether a wider lead lasts longer: it does not (Spearman -0.04 over 177 completed spells), so gap size is not a usable proxy for confidence. Every input is a public attestation UID: recompute it yourself from base.easscan.org and get the same number. Observed history with sample sizes attached, never a forecast — assets whose lead has not changed in the window are reported as a floor with a censoring flag, never as a median.
rate
get_rate_sensitivity
How close a Base lending market is to the kink where borrow rates explode. Returns, per protocol, the current utilization, the kink read from the protocol's own interest rate curve, the headroom in bps, and the borrow APY at points around the kink — plus how many times the borrow cost multiplies just past it. Measured on a live reading: Compound USDC sat 0.17 points below its kink, where borrow cost goes from ~4% to ~16%. Aave and Compound only: Morpho's adaptive IRM has no static curve to read and DefiLlama-sourced protocols expose none, so they are marked unmeasured and never assumed stable. Describes the current state of the curve, not a prediction that utilization will move.
shared
get_shared_exposure
Shared risk exposure across a declared portfolio. Give it your positions (protocol:usd pairs) and it returns, per factor, how much of your capital sits behind the same collateral, price oracle or vault curator — and through which venues it gets there. This is the question the market does not answer: depeg and hack alerts tell you an event happened, not whether you are two hops from it. In the Stream Finance collapse only 1 of ~320 MetaMorpho vaults held the broken asset directly, yet $93M of loss became $285M of contagion. Measured live: a Morpho USDC vault sits 93.7% behind cbBTC while Compound's USDC market is 43.1% — holding both is one risk in two wrappers. Morpho is attributed per isolated market and Compound by its real posted-collateral basket; Aave is reported unattributed, because a v3 supplier is exposed to the entire pool and splitting that across assets would imply diversification that does not exist. Structural shared exposure, not a correlation estimate.

Endpoints

URLTransportStateLatencyChecked
https://yieldsignal.vercel.app/mcp streamable-http answering 52 ms 14 min ago

Alternatives to YieldSignal

same job, measured the same way
MemorySync
by memorysync

Persistent memory for AI agents. Search and store durable facts, preferences and decisions.

answering
Knowledge MCP
by fulminate-io

Persistent memory graph for coding agents: hypotheses, evidence, and decisions survive sessions.

local only
Project Human
by humanity4ai

9 humanity skills for AI agents — crisis detection, WCAG 2.2, empathy, cultural sensitivity

64 installs/wk local only
Routescore
by routescore

Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.

47 installs/wk 11 tools answering
MCP State Sidecar
by askadvaith

MCP State Sidecar: durable state persistence for multi-agent AI workflows

62 installs/wk local only
Warmplane
by warmplane

Local MCP control plane for persistent sessions and compact capability discovery.

local only
Cathedral — Persistent Memory for AI Agents
by ailife1

Persistent memory and drift detection for AI agents across session restarts.

99 installs/wk answering
Solmachina X402
by imnotamob

Solana & Base DeFi intelligence for AI agents over x402: decisions, risk, signed receipts.

74 installs/wk 25 tools answering

YieldSignal — questions

Answers built from our own checks of this server.

What can YieldSignal do?
It exposes 7 tools, read directly from the server on our last check. Among them: get_exit_capacity, get_leadership_persistence, get_rate_sensitivity, get_shared_exposure, get_yield_decision, get_yield_durability and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is YieldSignal working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 55 of 91 checks got a reply (60.4%), average response time 383 ms. The bar chart above shows every period we have measured.
The registry lists YieldSignal as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect YieldSignal?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does YieldSignal need an API key?
No. YieldSignal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is YieldSignal?
It answers our handshake in 383 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is YieldSignal open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.