21btc.cc Bitcoin Data
REMOTE · 21BTC.CC
Live Bitcoin price, ETF flows, treasuries, on-chain metrics, fees, derivatives & wiki search.
Available components
Last scanned (1 hour ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 954 tokens (~68/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 71
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 5 Nov 2026 · Probed https://21btc.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=21btc.cc | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 67ce963bffcdbc30dda1efaff7841650043 |
| SANs: 21btc.cc, www.21btc.cc | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 21btc.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| 21btc.cc. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://21btc.cc/mcp | Verified | 200 | |
| http (plaintext) | http://21btc.cc/mcp | HTTPS enforced | 301 | https://21btc.cc/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 →
get_changelog Site changelog ~45
Recent shipped changes to 21btc.cc with dates and links. Same data as the /changelog page and its RSS feed. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_derivatives Bitcoin derivatives: open interest, funding, liquidations ~89
BTC perpetual futures on Binance, Bybit, OKX and Deribit: open interest (BTC and USD), mark price, funding rate per interval and annualised, a 30-day Binance open interest history and recent OKX liquidations. Public keyless exchange APIs, cached 60 seconds. Liquidations cover one exchange only; no free all-exchange total exists. Not advice. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_etf_flows Spot Bitcoin ETF flows ~50
US spot Bitcoin ETFs: BTC held, fee, latest/5d/20d/cumulative flows (USD millions). Same data as GET /api/v1/etf. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_events Upcoming Bitcoin conferences and events ~80
Upcoming Bitcoin-only conferences with dates, city, official URL, ticket offer (price only where verified on the official page) and the 21btc.cc event page where one exists. Dates in the venue's local time. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Filter by country name in English, e.g. Switzerland |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_fees Bitcoin transaction fees ~46
Recommended Bitcoin transaction fees in sat/vB (fastest, 30 minutes, 1 hour, economy, minimum) and mempool size, from mempool.space. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_holder_distribution Bitcoin addresses by balance (shrimp to humpback) ~73
How many Bitcoin addresses hold at least 0.1, 1, 10, 100, 1,000 and 10,000 BTC and how coins split across holder classes. Addresses, not people. Source: BitInfoCharts and four cross-checks, with an as-of date. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_holders Bitcoin holders: companies, funds, governments ~39
Bitcoin holders: companies, funds, governments (BTC, 7-day change). Same data as GET /api/v1/holders. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_network_stats Bitcoin network stats ~57
Bitcoin network now: block height, hashrate (EH/s), difficulty and the next difficulty adjustment, mempool size, average block time, halving countdown. Sources: mempool.space, blockchain.info, Blockchair. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_price Bitcoin price ~38
Live BTC price in USD and 7 other currencies (official FX reference rates). Same data as GET /api/v1/price. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rainbow_model Rainbow model (a model, not a forecast) ~41
Rainbow model fit parameters and today's deviation (a model, not a forecast). Same data as GET /api/v1/rainbow. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_risk_score Risk On/Off score ~43
Risk On/Off composite score (0–100) with every input, formula and source. Same data as GET /api/v1/risk. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stock_to_flow Stock-to-flow model (a model, not a forecast) ~46
Stock-to-flow ratio and PlanB 2019 model value (a model, not a forecast). Same data as GET /api/v1/stock-to-flow. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_volatility Bitcoin volatility ~42
Annualised realised volatility over 7/30/90/365 days and by year. Same data as GET /api/v1/volatility. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_site Search 21btc.cc (pages, glossary, wiki, blog) ~106
Search the site's pages, Bitcoin glossary terms, wiki articles, blog posts, videos, pools, wallets and hacks. Matches English and Russian. Returns title, kind, URL and a short summary. Use kind=glossary for definitions. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Limit to one kind of result |
| language | string | – | Language of titles and summaries |
| limit | integer | – | – |
| query | string | yes | Words to look for, English or Russian |
No output schema declared.
No examples provided.
How do I install the 21btc.cc Bitcoin Data MCP server?
21btc.cc Bitcoin Data is a hosted endpoint at https://21btc.cc/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 · 21btc.cc
claude mcp add --transport http cc-21btc-bitcoin-data 'https://21btc.cc/mcp'
What is the 21btc.cc Bitcoin Data MCP server?
21btc.cc Bitcoin Data is an MCP server listed in the public MCP registry as cc.21btc/bitcoin-data. Live Bitcoin price, ETF flows, treasuries, on-chain metrics, fees, derivatives & wiki search. This page covers its hosted endpoint (https://21btc.cc/mcp).
Is the 21btc.cc Bitcoin Data MCP server safe to use?
21btc.cc Bitcoin Data scores 75 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 21btc.cc Bitcoin Data MCP server expose?
21btc.cc Bitcoin Data exposes 14 tools: get_price, get_etf_flows, get_risk_score, get_volatility, get_holders, and 9 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.
Does the 21btc.cc Bitcoin Data MCP server require authentication?
No. We connected to 21btc.cc Bitcoin Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 21btc.cc Bitcoin Data MCP server still maintained?
21btc.cc Bitcoin Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.