Skip to content

BitcoinYield MCP server

co.bitcoinyield/yieldsbitcoinyield.costreamable-httpv1.13.0Scanned

Best live crypto yield at each A-D risk grade on BTC, ETH, SOL and stablecoins, DeFi and CeFi.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the BitcoinYield MCP server can do

The BitcoinYield MCP server is published by bitcoinyield.co, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.13.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • list_offersThe 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 l…No findings

    Why it is in this group

    • The name "list_offers" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_yieldsOne 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 BitcoinYiel…No findings

    Why it is in this group

    • The name "list_yields" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
410
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 410.

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none
  2. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.13.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http yields https://bitcoinyield.co/api/mcp
claude mcp add --transport http yields https://bitcoinyield.co/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__yields__list_yields",
      "mcp__yields__list_offers"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yields. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.bitcoinyield/yields/verify?hash=84086bf9a11944db7a46914f80259df117cab6ef42f7fa3e797fc0512420e805" | jq -e '.changed == false'

Pinned hash 84086bf9a119, from Nov 9, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.bitcoinyield/yields/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.bitcoinyield/yields
[![Anlyon Radar](https://radar.anlyon.com/badge/co.bitcoinyield/yields.svg)](https://radar.anlyon.com/servers/co.bitcoinyield/yields)

Source: MCP Registry. Synced Nov 18, 2026, 08:17 UTC.

BitcoinYield MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BitcoinYield MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the BitcoinYield MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BitcoinYield MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BitcoinYield MCP server have?

2 tools: 2 read. list_yields and list_offers.

Does the BitcoinYield MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the BitcoinYield MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BitcoinYield MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 27, 2026. Every change is on this page and in its Atom feed.