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
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.
We read the source, 22 h ago · tools taken from the live server · rules 3dff92dd89df
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.
"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.
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.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
claude mcp add yieldsignal --transport http https://yieldsignal.vercel.app/mcp
{
"mcpServers": {
"yieldsignal": {
"url": "https://yieldsignal.vercel.app/mcp"
}
}
}
[mcp_servers.yieldsignal]
url = "https://yieldsignal.vercel.app/mcp"
{
"mcpServers": {
"yieldsignal": {
"url": "https://yieldsignal.vercel.app/mcp"
}
}
}
{
"mcpServers": {
"yieldsignal": {
"url": "https://yieldsignal.vercel.app/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_yield_decision
get_yield_durability
get_yield_signal
get_exit_capacity
get_leadership_persistence
get_rate_sensitivity
get_shared_exposure
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://yieldsignal.vercel.app/mcp | streamable-http | answering | 52 ms | 14 min ago |
Persistent memory for AI agents. Search and store durable facts, preferences and decisions.
Persistent memory graph for coding agents: hypotheses, evidence, and decisions survive sessions.
9 humanity skills for AI agents — crisis detection, WCAG 2.2, empathy, cultural sensitivity
Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.
MCP State Sidecar: durable state persistence for multi-agent AI workflows
Local MCP control plane for persistent sessions and compact capability discovery.
Persistent memory and drift detection for AI agents across session restarts.
Solana & Base DeFi intelligence for AI agents over x402: decisions, risk, signed receipts.
Answers built from our own checks of this server.