
YieldCave MCP server
Which MCP servers are YieldCave's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.yieldcave/yieldcaveverified in the MCP registry
The registry name sits under yieldcave.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools19
- Server calls itselfyieldcave
- Server version0.9.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 461 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- create_alert, delete_alert, create_api_key change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer517 ms
- Space in an agent's context≈ 2,969 tokensthe definitions of all its tools (19), which an agent carries on every turn
- Tool definitionsA · 97 of 100
- Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 19
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_alert, delete_alert, create_api_key
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_rwa_yieldsLists tokenized real-world asset deployments (tokenized US treasuries, credit, funds) with current APY and TVL, from public DefiLlama data. Filter by chain or kind. Information only, not advice.
get_rwa_assetReturns every deployment of one tokenized asset symbol (e.g. BUIDL, USDY, OUSG) across chains, with total TVL and curated description.
rwa_market_summaryTotals for the tokenized treasury market: distinct tokens, total TVL, median APY, top tokens by TVL, plus totals for other tokenized real-world assets.
compare_yield_to_tokenized_treasuriesGiven an APY the user currently earns (e.g. a bank savings rate), computes the simple-interest difference versus the highest-yielding liquid tokenized treasury over a horizon. Returns arithmetic and assumptions only; it does not recommend.
list_stablecoin_yieldsWhere USDC, USDT, DAI, USDe and other stablecoins earn yield right now: single-asset pools on lending markets and vaults (credit and basis venues on Pro) (DefiLlama data, excludes tokenized treasuries, which have their own tools). Each…
stablecoin_yield_summaryPer stablecoin: venues, total TVL, median APY, best venue overall and best collateralized-lending venue; totals by category group; and the median tokenized treasury APY for comparison. Pools with at least $10M TVL by default.
list_tokenized_equitiesTokenized equities on public chains (xStocks, bStocks, Ondo Global Markets, Robinhood, Dinari, Coinbase and others): token price, market cap, 24h volume, the underlying ticker, chains, and (on Pro) premium or discount to the latest…
get_tokenized_equityAll tokenized versions of one underlying stock (e.g. TSLA) across issuers: market caps, volumes, chains, the most liquid wrapper, and (on Pro) the premium/discount range versus the underlying quote.
tokenized_equity_summaryTotals for tokenized equities: token count, market cap and 24h volume; breakdown by issuer and by kind; top underlyings by combined market cap (top 5 on Free, 10 on Pro); on Pro, how many tokens have an underlying quote and the median…
rwa_issuer_termsHand-curated terms for a tokenized treasury token: who may invest (US persons?), minimum, structure (summary on Free; Pro adds what backs it, domicile, redemption method and timing, fees, yield mechanics and source URLs). Covers BUIDL…
rwa_historyDaily snapshots of total TVL and TVL-weighted APY for one symbol, optionally on one chain, over the last N days (default 30; Free and anonymous plans see 7, Pro the full history). universe "rwa" (tokenized assets, default) or "stablecoin"…
rwa_changesCompares the latest market with the snapshot from N days ago (default 1): APY and TVL change per deployment, biggest movers first, plus new and vanished deployments. universe "rwa" (default) or "stablecoin".
create_alertCreates a rule that is checked every hour after the data refresh. When any matching deployment crosses the threshold, YieldCave POSTs a JSON payload to your HTTPS webhook (Slack, Discord, Zapier, your own server). Fires at most once per…
list_alertsLists active alert rules (webhook hosts only, never full URLs).
delete_alertDeletes an alert by id.
create_api_keyCreates a free YieldCave API key (300 calls/day, 3 alerts, 7 days of history) tied to an email address. The key is shown once. Send it on every request as an x-api-key header or Authorization: Bearer. One key per email.
my_usageShows the caller's plan, calls used today, remaining allowance, alert allowance, depth limits, and what each plan includes.
upgradeReturns a checkout link for the Pro plan ($49/month: full history and changes, all stablecoin venues, full issuer terms, 100 alerts, 5000 calls/day). Needs an API key.
manage_subscriptionReturns a Stripe Billing Portal link to update payment details, see invoices, or cancel the Pro subscription. Needs an API key with a subscription.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"yieldcave": {
"type": "http",
"url": "https://mcp.yieldcave.com"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http yieldcave https://mcp.yieldcave.comclaude.ai, ChatGPT and other clients: add https://mcp.yieldcave.com as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.