MCP servers › com.yieldcave › yieldcave

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

com.yieldcave/yieldcave

Tokenized asset data for agents: treasury yields, stablecoin rates, tokenized stocks, alerts. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedPricing: freemium · AI-classifiedversion 0.9.1JavaScriptstreamable HTTP19 tools

Summary

com.yieldcave/yieldcave is a remote MCP server listed in the official MCP registry at version 0.9.1. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 19 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 19
Described as changing data: 5 of 19 toolsAI-classified
Topic: finance-and-paymentsAI-classified
Pricing: freemiumAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (create_alert, delete_alert, create_api_key). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

5 tools are described as changing something (create_alert, delete_alert, create_api_key, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.9.1, published 2026-10-16 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-12 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-12 to 2026-10-16; 2 in the 90 days before the 2026-10-23 snapshot.

Most recent 2 versions

0.9.1 · 2026-10-16
0.9.0 · 2026-10-12

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-22

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.9.1 (published 2026-10-16).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

19tools

0resources

0prompts

5 of 19 tools are described as changing something (creating, editing, deleting, sending or running).

list_rwa_yieldsreads or searches
“Lists tokenized real-world asset deployments (tokenized US treasuries, credit, funds) with current APY and TVL, from public DefiLlama data.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- chainstring“Blockchain name, e.g.”
- kindstring“"treasury" = tokenized US government debt / money-market style”
- minTvlUsdnumber“Minimum total value locked in USD (default 1,000,000)”
- limitinteger“Max rows (default 20)”
- sortBystring“Sort key (default tvlUsd)”
get_rwa_asseton 1 other serverreads or searches
“Returns every deployment of one tokenized asset symbol (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- symbolstringrequired“Token symbol, e.g.”
rwa_market_summaryreads or searches
“Totals for the tokenized treasury market: distinct tokens, total TVL, median APY, top tokens by TVL, plus totals for other tokenized real-world assets.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
compare_yield_to_tokenized_treasuriescalculates or converts
“Given an APY the user currently earns (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- currentApyPercentnumberrequired“APY the user earns today, in percent, e.g.”
- amountUsdnumber“Amount in USD (default 10,000)”
- horizonDaysinteger“Horizon in days (default 365)”
- minTvlUsdnumber“Liquidity floor for candidates (default 50,000,000)”
list_stablecoin_yieldsreads or searches
“Where 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 treasurie…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- symbolstring“Stablecoin symbol, e.g.”
- chainstring“Blockchain name, e.g.”
- groupstring“Risk/category group”
- majorOnlyboolean“Only major stablecoins (USDC, USDT, DAI, USDS, USDe, PYUSD, ...)”
- minTvlUsdnumber“Minimum pool TVL in USD (default 10,000,000)”
- sortBystring“Default apy”
- limitinteger“Max rows (default 20)”
stablecoin_yield_summaryreads or searches
“Per 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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- minTvlUsdnumber“Pool TVL floor (default 10,000,000)”
list_tokenized_equitiesreads or searches
“Tokenized 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) p…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- issuerstring“Issuer name or part of it, e.g.”
- kindstring
- underlyingstring“Underlying ticker, e.g.”
- chainstring“Chain name as CoinGecko lists it, e.g.”
- minMarketCapUsdnumber“Default 1,000,000”
- sortBystring“Default marketCap; premium sorts by absolute premium”
- limitinteger“Max rows (default 20; Free and anonymous up to 10, Pro up to 100)”
get_tokenized_equityreads or searches
“All tokenized versions of one underlying stock (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- underlyingstringrequired“Underlying ticker, e.g.”
tokenized_equity_summaryreads or searches
“Totals 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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
rwa_issuer_termsreads or searches
“Hand-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 mecha…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- symbolstringrequired“Token symbol, e.g.”
rwa_historyreads or searches
“Daily 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).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- symbolstringrequired“Symbol, e.g.”
- chainstring“Restrict to one chain”
- daysinteger“How many days back (default 30)”
- universestring“Default rwa”
rwa_changesreads or searches
“Compares 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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- daysinteger“How many days back to compare against (default 1)”
- kindstring“Default "treasury" (rwa universe only)”
- universestring“Default rwa”
- limitinteger“Max movers (default 15)”

Show 7 more tools

create_alerton 17 other serverscreates or changes datadescribed as changing data
“Creates a rule that is checked every hour after the data refresh.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
8 inputs, 4 required
- universestring“Default rwa”
- metricstringrequired“"apy" in percent, "tvl" in USD”
- operatorstringrequired
- thresholdnumberrequired“e.g.”
- webhookUrlstringrequired“Where to POST when the alert fires”
- symbolstring“One token, e.g.”
- chainstring“Restrict to one chain”
- labelstring“Free text shown in the payload”
list_alertson 26 other serversreads or searches
“Lists active alert rules (webhook hosts only, never full URLs).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
delete_alerton 15 other serversdeletesdescribed as changing data
“Deletes an alert by id.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- idstringrequired
create_api_keyon 34 other serverscreates or changes datadescribed as changing data
“Creates a free YieldCave API key (300 calls/day, 3 alerts, 7 days of history) tied to an email address.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- emailstringrequired“Where to reach you about the key”
my_usageon 2 other serversreads or searches
“Shows the caller's plan, calls used today, remaining allowance, alert allowance, depth limits, and what each plan includes.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
upgradeon 15 other serversdescribed as changing data
“Returns a checkout link for the Pro plan ($49/month: full history and changes, all stablecoin venues, full issuer terms, 100 alerts, 5000 calls/day).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
Takes no inputs.
manage_subscriptionon 2 other serversdescribed as changing data
“Returns a Stripe Billing Portal link to update payment details, see invoices, or cancel the Pro subscription.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 19 tools
Says what it returns: 89% of 18 tools
States limits, defaults or errors: 33% of 18 tools
Says when to use it: 22% of 18 tools
Items covered per tool: 2.4 of 4 on average

Counted from the listing

Parameters with a description: 93% of 45
Tools with a description: 100% of 19
Typical description length: 221 characters

The tool set

Counted from the listing

Tools: 19
Size of the list: about 4,025 tokens for an agent to load (characters ÷ 4)
Naming: 18 of 19 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 19 of 19 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.yieldcave.com/

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yieldcave": {
      "url": "https://mcp.yieldcave.com/"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "yieldcave": {
      "type": "http",
      "url": "https://mcp.yieldcave.com/"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"yieldcave","type":"http","url":"https://mcp.yieldcave.com/"}'

Claude Code

claude mcp add --transport http yieldcave https://mcp.yieldcave.com/

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.yieldcave.com/ --transport http

Optional settings the entry also lists (left out above): x-api-key.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.yieldcave.com/	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/yieldcave/yieldcave	Opens publicly	matches	api.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: com.yieldcave
GitHub owner: an organization (yieldcave)

Repository: github.com/yieldcave/yieldcave
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.yieldcave/yieldcave

Answered from the data above

Is com.yieldcave/yieldcave safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 5 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is com.yieldcave/yieldcave free to use?

Its website (yieldcave.com/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does com.yieldcave/yieldcave need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.yieldcave/yieldcave been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can com.yieldcave/yieldcave do?

It lists 19 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can com.yieldcave/yieldcave change or delete data?

5 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does com.yieldcave/yieldcave publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.yieldcave/yieldcave?

In github.com/yieldcave/yieldcave, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.longsizhuo/openinvestopenInvestalso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one
com.ausca/agent-servicesAuscaalso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one
io.github.manganate006/openlmnpOpenLMNPalso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one
io.github.aibtcdev/mcp-serveralso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one
io.github.lightningfaucet/lightning-wallet-mcpLightning Walletalso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one
io.github.lightningfaucet/mcp-serveralso has tools that calculates or converts, creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,602 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 19 tools, 0 resources, 0 prompts.
5,156 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified · 2026-10-23

Pricing modelAI-classified

freemium

read from yieldcave.com/ · 2026-10-23

“Live data is free.”

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-22

Maintenance

active

api.github.com · 2026-10-22

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.yieldcave/yieldcave: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.yieldcave/yieldcave

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.yieldcave/yieldcave)](https://protocolprobe.com/mcp/servers/com.yieldcave/yieldcave)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology