YieldCave MCP server
online · 100% uptimecom.yieldcave/yieldcave·v0.9.1Tokenized asset data for agents: treasury yields, stablecoin rates, tokenized stocks, alerts.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed YieldCave yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
YieldCave tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How YieldCave compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 579 ms
- faster than 25% of 30,031 servers
Release history: 2 versions in the registry since 2026-10-12, latest 2026-10-16, typically one every 3 days.
Install YieldCave in Claude Code, Cursor or VS Code
claude mcp add --transport http yieldcave https://mcp.yieldcave.com
What the publisher says
From the YieldCave repository's README, as published. We do not edit it. Read it on GitHub
YieldCave
Machine-readable tokenized-finance data for AI agents: tokenized treasuries, stablecoin yield venues, and tokenized stocks.
YieldCave is an MCP server. Add it to Claude Desktop, Claude Code or Cursor and your agent can answer questions like:
- "What tokenized US treasuries are on Solana right now, and what do they yield?"
- "How much more would $25k earn in the best liquid tokenized treasury than in my 0.4% savings account?"
- "Summarize the tokenized RWA market."
- "Where does USDC earn the most on a collateralized lending market with at least $50M behind it?"
- "Which tokenized NVIDIA token is the most liquid, and is it trading at a premium to the stock?"
It is read-only. It never touches a wallet, never moves money and never recommends. That is the point: an index, not a broker.
Data comes from DefiLlama's public API. No API key is needed.
1. Run it locally (5 minutes)
You need Node 20 or newer (node --version).
cd ~/yieldcave && npm installSee the data in your terminal:
npm run demoRun the unit tests (no network needed):
npm testRun the end-to-end checks, which start the real MCP server and call it the way Claude would, over stdio and over HTTP:
npm run smoke && npm run smoke:http2. Add it to Claude Desktop
Open this file (create it if it does not exist):
~/Library/Application Support/Claude/claude_desktop_config.jsonAdd YieldCave under mcpServers. If the file already has other servers, add just the "yieldcave" block inside the existing object.
{
"mcpServers": {
"yieldcave": {
"command": "node",
"args": ["/Users/bjf/yieldcave/src/server.js"]
}
}
}Quit and reopen Claude Desktop. You should see a tools icon with four YieldCave tools. Try: "Use YieldCave to summarize the tokenized treasury market."
3. Add it to Claude Code
claude mcp add yieldcave -- node /Users/bjf/yieldcave/src/server.js3b. Use it from claude.ai in a browser (hosted version)
YieldCave also runs in the cloud on Supabase, so claude.ai (and anyone else) can reach it without your Mac being on.
https://ccvhvxbqtvqbhexhrjnj.supabase.co/functions/v1/mcpIn claude.ai: Customize → Connectors → Add → Add custom connector → paste that URL, no sign-in. The hosted version serves data from Postgres, which a scheduled job refreshes every hour, and it keeps one snapshot per day. That history powers the fifth tool, rwa_history.
How the hosted version is put together, all inside the supabase/ folder:
supabase/functions/_shared/ the real code: data.js, tools.js, mcp.js (src/ re-exports these)
supabase/functions/mcp/ public MCP endpoint, reads market_latest and snapshots from Postgres
supabase/functions/refresh/ fetches DefiLlama + CoinGecko + quotes, writes market_latest + today's snapshot, fires alerts; needs REFRESH_SECRET header
supabase/functions/enrich/ fills chain metadata for tokenized equities, 15 per run, every 10 minutes
supabase/functions/stripe-webhook/ upgrades/downgrades keys on Stripe events
supabase/functions/site/ serves the landing page (pages.js is generated from site/)
supabase/migrations/ tables (market, snapshots, alerts, api_keys, usage_daily), RLS on, hourly pg_cron job, public site bucket
scripts/ configure-stripe.sh, publish-site.shTo redeploy after a change:
supabase functions deploy mcp --no-verify-jwt --use-api && supabase functions deploy refresh --no-verify-jwt --use-apiCheck a deployment end to end (tools, history, and an alert that creates, fires, and deletes itself):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
YieldCave: common questions
- Is YieldCave MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the YieldCave safety report
- How do I install YieldCave?
- It runs remotely at mcp.yieldcave.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does YieldCave need an API key?
- Yes. The registry entry asks for
x-api-key. - Is YieldCave maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.9.1.
- Is YieldCave up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does YieldCave compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 579 ms (faster than 25% of 30,031 servers). Full comparison.