BitcoinYield
REMOTE · BITCOINYIELD.CO · SCANNED SEP 26
Live crypto yields for BTC, stablecoins and ETH across DeFi and CeFi, with A-D risk grades.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 266 tokens (~266/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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'
{
"mcpServers": {
"co-bitcoinyield-yields": {
"url": "https://bitcoinyield.co/api/mcp"
}
}
} {
"servers": {
"co-bitcoinyield-yields": {
"type": "http",
"url": "https://bitcoinyield.co/api/mcp"
}
}
} [mcp_servers.co-bitcoinyield-yields] url = "https://bitcoinyield.co/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-bitcoinyield-yields": {
"type": "remote",
"url": "https://bitcoinyield.co/api/mcp",
"enabled": true
}
}
} openclaw mcp add co-bitcoinyield-yields --url 'https://bitcoinyield.co/api/mcp' --transport streamable-http
mcp_servers:
co-bitcoinyield-yields:
url: "https://bitcoinyield.co/api/mcp" {
"McpServers": {
"co-bitcoinyield-yields": {
"Transport": "http",
"Url": "https://bitcoinyield.co/api/mcp"
}
}
} assistant mcp add co-bitcoinyield-yields -t streamable-http -u 'https://bitcoinyield.co/api/mcp'
{
"mcpServers": {
"co-bitcoinyield-yields": {
"type": "http",
"url": "https://bitcoinyield.co/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 73
First indexed and scored.
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 26 Sept 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=YR2,O=Let's Encrypt,C=US | 12 Aug 2026 | 10 Nov 2026 | RSA 2048 | SHA256-RSA | 6671e97634627cd680bc100b5a612cf84f0 |
| SANs: bitcoinyield.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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. | present | 7786 | 8 | Verified |
| bitcoinyield.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| 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 | Verified | 200 | |
| 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_yields List the best yield per asset ~192
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. Set max_risk to limit the pick to offers graded at or below that letter (A = lower risk, B = moderate). Rates are variable and not advice. No key required.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Filter to one asset by its symbol, e.g. BTC, USDC or USDE. |
| max_risk | string | – | Only consider offers graded at or below this letter: A (lower risk), B (moderate), C (elevated), D (higher). |
| stablecoin | string | – | Set to "true" to return only stablecoin assets. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| stale | boolean | – | – |
| updated_at | string|null | – | – |
| yields | array | yes | – |
No examples provided.
What is the BitcoinYield MCP server?
BitcoinYield is an MCP server listed in the public MCP registry as co.bitcoinyield/yields. Live crypto yields for BTC, stablecoins and ETH across DeFi and CeFi, with A-D risk grades. This page covers its hosted endpoint (https://bitcoinyield.co/api/mcp).
Is the BitcoinYield MCP server safe to use?
BitcoinYield scores 73 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 1 tool: list_yields. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.
Does the BitcoinYield MCP server require authentication?
No. We connected to BitcoinYield without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BitcoinYield MCP server still maintained?
BitcoinYield is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.