BitcoinYield
REMOTE · BITCOINYIELD.CO
Best live crypto yield at each A-D risk grade on BTC, ETH, SOL and stablecoins, DeFi and CeFi.
Available components
Last scanned (16 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: BitcoinYield is offline: this server, its site and its API are no longer available.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 451. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 −56
- Endpoint reachability: unreachable → not serving MCP ▼ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 451. security
- 12 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 72 to 75.
- 10 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 75 to 72.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +4
No change was recorded against any check on this day. Stability & Change Management went from 50 to 75.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_offers” rewrote its description, which is the text the model reads security
- Tool “list_yields” rewrote its description, which is the text the model reads security
- Server version: 1.12.0 → 1.13.0 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://bitcoinyield.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bitcoinyield.co | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 649e93d10cc605c6f9ece3fa333c861d3aa |
| SANs: bitcoinyield.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bitcoinyield.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| bitcoinyield.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 451 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bitcoinyield.co/api/mcp | HTTP error | 451 | |
| http (plaintext) | http://bitcoinyield.co/api/mcp | HTTPS enforced | 308 | https://bitcoinyield.co/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_offers List the top live offers for one asset ~361
The top live yield offers for one asset (5 by default, up to 20) in BitcoinYield's own order: rate and risk together, with offers that have a month of steady history and $10M+ of liquidity first. Each offer carries its platform, chain, product type, rate (a percent, with rate_text, the figure to quote: "0.17% APY"), organic versus incentive split, 30-day average, liquidity, A-D risk grade with its main reasons, US availability, investor access, the platform's own deposit link and the page to cite. Filter by chain or a risk ceiling. Use it to compare options; list_yields gives one pick per asset. Rates are variable and not advice. No key required. When nothing matches, the answer says why: the filters, a dollar that lost its peg, or no live quote on the asset.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset's symbol, e.g. BTC, USDC or USDE. For a token an asset is held as, give the asset: BTC for WBTC, ETH for stETH, DAI for USDS or sUSDS, SOL for jitoSOL (the tokens themselves are also read a… |
| chain | string | – | Only offers on this chain, e.g. Ethereum, Base, Arbitrum or Solana (case-insensitive). Centralized (CeFi) offers have no chain. |
| limit | integer | – | How many offers to return, 1 to 20 (default 5). |
| max_risk | string | – | Only offers graded at or below this letter: A (lower risk), B (moderate), C (elevated), D (higher). |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| count | integer | yes | – |
| degraded_sources | array | – | The sources missing from this snapshot, if any. |
| offers | array | yes | – |
| partial | boolean | – | True when a data source was missing from this snapshot. |
| stale | boolean | – | True when part of this snapshot is over 6 hours old (a scheduled refresh was missed). |
| updated_at | string|null | – | When the feed was last refreshed (ISO 8601). It refreshes every 3 hours. |
| url | string | yes | The asset's full comparison on BitcoinYield. |
No examples provided.
list_yields List the best yield per asset ~531
One entry per asset (Bitcoin, ETH, SOL, USDC, USDT and every other tracked stablecoin, tokenized Treasury and L1) with its best current yield across DeFi and CeFi under BitcoinYield's risk-weighted ranking, its A-D risk grade, and a link to the full comparison. by_grade gives the best proven rate at grade A, B and C (A = lower risk), the tradeoff a holder chooses between: a grade is null when nothing proven at it pays materially more (at least 0.05 points and 5%) than a safer grade. best_apy and each by_grade rate are in percent (0.17 means 0.17%), as the asset page shows them (today's rate, or its 7-day average when that is lower); quote best_rate_text and each by_grade rate_text, which print them with their unit, APY or APR. To answer 'what is the best yield on X', quote by_grade, the lowest-risk grade first: best_apy is the by_grade step the risk-weighted ranking puts first and can be a higher-risk one, or one closed to US residents. An asset with no proven offer has no pick: best_apy is null and no_pick_reason says why its top-ranked offer is not one. Set max_risk to limit every pick to offers graded at or below that letter. Rates are variable and not advice. No key required. With no asset or stablecoin filter this tool answers the headline assets (BTC, ETH, SOL, USDC, USDT, DAI, USDe, USD1, USDG, PYUSD, RLUSD); set all to true for every asset with a live yield.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Set to true for every asset with a live yield (about 60 entries, a large answer) instead of the headline assets. Ignored when asset or stablecoin is set. |
| asset | string | – | Filter to one asset by its symbol, e.g. BTC, USDC or USDE. For a token an asset is held as, give the asset: BTC for WBTC, ETH for stETH, DAI for USDS or sUSDS, SOL for jitoSOL (the tokens themselves… |
| max_risk | string | – | Only consider offers graded at or below this letter: A (lower risk), B (moderate), C (elevated), D (higher). |
| stablecoin | boolean | – | Set to true to return only stablecoin assets. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| degraded_sources | array | – | The sources missing from this snapshot, if any. |
| partial | boolean | – | True when a data source was missing from this snapshot. |
| stale | boolean | – | True when part of this snapshot is over 6 hours old (a scheduled refresh was missed). |
| updated_at | string|null | – | When the feed was last refreshed (ISO 8601). It refreshes every 3 hours. |
| yields | array | yes | – |
No examples provided.
How do I install the BitcoinYield MCP server?
BitcoinYield is a hosted endpoint at https://bitcoinyield.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bitcoinyield.co
claude mcp add --transport http co-bitcoinyield-yields 'https://bitcoinyield.co/api/mcp'
What is the BitcoinYield MCP server?
BitcoinYield is an MCP server listed in the public MCP registry as co.bitcoinyield/yields. Best live crypto yield at each A-D risk grade on BTC, ETH, SOL and stablecoins, DeFi and CeFi. This page covers its hosted endpoint (https://bitcoinyield.co/api/mcp).
Is the BitcoinYield MCP server safe to use?
BitcoinYield scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BitcoinYield MCP server expose?
BitcoinYield exposes 2 tools: list_yields, list_offers. Their descriptions and schemas cost roughly 892 tokens of context every time the server is loaded.
Does the BitcoinYield MCP server require authentication?
Its publisher declares no required credentials for BitcoinYield. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BitcoinYield MCP server still maintained?
BitcoinYield is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BitcoinYield MCP server?
VerifyMCP ran 5 checks on BitcoinYield, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about BitcoinYield: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.