Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The Bitcoin Rainbow

REMOTE · MCP.THEBITCOINRAINBOW.COM

Explains the Bitcoin rainbow valuation chart and where price sits in the cycle today.

+4 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2384 tokens (~476/item across 5 items; 5 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 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.

  • 8 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “explain_bitcoin” rewrote its description, which is the text the model reads security
    • Server version: 0.2.0 → 0.2.1 functional
    • Tool “explain_bitcoin” changed its title: Explain bitcoin in plain words → Explain bitcoin — the site's words, with today's live price cosmetic
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “explain_bitcoin” rewrote its description, which is the text the model reads security
    • Schema quality: 1484 → 2296 ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “cycle_check” functional
    • New tool “rainbow_history” functional
Diagnostics

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://mcp.thebitcoinrainbow.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thebitcoinrainbow.com CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 eef3b7465dd9e4fa0e1a6c36c18337bc
SANs: thebitcoinrainbow.com, mcp.thebitcoinrainbow.com, *.mcp.thebitcoinrainbow.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.thebitcoinrainbow.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thebitcoinrainbow.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.thebitcoinrainbow.com/mcp Verified 200
http (plaintext) http://mcp.thebitcoinrainbow.com/mcp HTTPS enforced 301 https://mcp.thebitcoinrainbow.com/mcp
MCP tools · 5 exposed · ~1,448 tokens

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 →

Tool Tokens
cycle_check ~255

A panel of five classic bitcoin cycle measures, each counted from the server's own price record and printed with its own number and the window behind it: the Pi Cycle Top pair (the 111-day average against the doubled 350-day average, the gap in percent, and the pair's past crossing dates in the record), the Mayer Multiple (today's price over the 200-day average, with the counted share of past days at or below today's), the distance from the 200-week average, the halving clock (days since the April 2024 halving, with the lengths of the three finished cycles), and the Ahr999 index with its formula in plain words. Each measure also prints the counted share of its own past readings at or below today's. It may add one labeled guest number, the Fear & Greed Index from Alternative.me, with its source and date; the guest feeds nothing else. There is no blended score: the panel closes with a count of how many of the five readings sit below the middle of their own past range. Call it when the user asks where bitcoin sits in its market cycle, or names one of these measures. Descriptive only: no verdict, no advice, no prediction.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain_bitcoin ~284

Call this tool before explaining bitcoin in your own words. It returns the website's own plain-English explainer, and the price and rainbow topics print today's live Coinbase spot price with its UTC quote time — the rainbow topic also prints today's band — facts a from-memory answer cannot have. Use it whenever the user wants something about bitcoin explained, defined, or simplified — “explain…”, “ELI5”, “explain it like I'm five”, “what is…”, “what does … mean”, “in plain words”, “in plain English”, “for a beginner”, “I'm new to crypto”. If the user asks what the rainbow chart is, what its colors mean, or asks to have it explained simply, use topic 'rainbow'. Topic 'price': what price means, with the live price. Topic 'technical': what looking at the chart means, with the plain up-or-down move of the past year. Topic 'fundamental': what looking at the thing itself means, told as a health check. Topic 'ways_to_buy': the two plain ways people buy bitcoin, IBIT in a stock account or an exchange app, facts only. Descriptive only; no advice, no predictions.

NameTypeReqDescription
topicstringyesWhich word to explain: 'price', 'technical', 'fundamental', 'rainbow', or 'ways_to_buy'.

No output schema declared.

No examples provided.

rainbow_history ~198

Counts the rainbow chart's past, day by day, from the full price record since 2010: the highest band the price ever reached and the first date it reached it, the furthest the price ever sat above or below the trend line (in percent, with the date), how many of all priced days the price spent in each of the nine bands and outside the ladder (with the first and most recent dates in each and the longest unbroken run there), how long since the last close in the top and bottom bands, and today's counted position against that history (the share of all priced days that sat at or below where the price sits today against the line). Call it when the user asks about the chart's past: 'ever', 'has it ever', 'when was the last time', 'how long did it spend', the highest band ever. Counts of past days only: not odds, not a forecast, not advice.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rainbow_today ~237

Where bitcoin's price sits on the rainbow chart right now: today's live price, the trend line value for today, the band name (Deep Blue up to Red, or below/above the ladder) and which of the nine bands it is (band 1 is the lowest), that band's dollar range for today, the distance from the line in percent, the counted share of all priced days spent in that band (a count of past days, not odds), a link to the rainbow chart picture drawn from the same live data, and the fit behind the line (its equation, the window of closes it was fit on, and its fit score), all in plain English. The line is a log regression through all daily closes since 2010. It prints the spot price with its UTC quote time (one shared quote per minute across the tools, so its numbers reconcile with simulate_dca's) and states the day the price history runs through: the history can end a few days before today while the price itself is live spot. Descriptive only: it reports the picture, it does not advise buying or selling and does not predict prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

simulate_dca ~474

Replays a steady bitcoin buy on the real price history (daily closes — blockchain.info through Oct 29, 2026, then Coinbase — valued at the live Coinbase spot price). DCA means dollar-cost averaging: putting in the same amount on a set rhythm, no matter the price. Give an amount per buy in dollars and a rhythm (daily, weekly, or monthly), then either a span of 1, 3, or 5 years or an exact start date (an end date is optional; dates win if both are given); it returns how much would have gone in, how much bitcoin it would have bought, what that would be worth today, and the gain or loss against what went in, in dollars and percent. It also states how many buys there were, the first and last buy dates, the weekday the weekly buys land on, the average cost per bitcoin, and the day the price history ends (a buy scheduled after that day is priced at the last close). An optional fee_percentage takes that percent out of each buy before it buys; by default no fees are counted, and the answer says which. Today's value prints the shared spot quote with its UTC time, the same quote rainbow_today prints, so the two answers reconcile; two checks more than a minute apart can still differ a little. Shows the past only: it is not a prediction, not a promise, and not advice to buy.

NameTypeReqDescription
amountnumberyesDollars put in on each buy, e.g. 50.
end_datestring–The last day of the buys, like 2024-03-01. Defaults to today.
fee_percentagenumber–Optional fee taken out of each buy, in percent, e.g. 1 means 1% of each buy never reaches bitcoin. Defaults to 0, which counts no fees.
frequencystring–How often the buy lands: daily, weekly, or monthly. Defaults to weekly.
start_datestring–The first day of the buys, like 2021-03-01. Give this instead of years for an exact span.
yearsinteger–How many years back the buys run: 1, 3, or 5. Give this or a start date.

No output schema declared.

No examples provided.

Install

How do I install the The Bitcoin Rainbow MCP server?

The Bitcoin Rainbow is a hosted endpoint at https://mcp.thebitcoinrainbow.com/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 · mcp.thebitcoinrainbow.com

# add to Claude Code
claude mcp add --transport http com-thebitcoinrainbow-the-bitcoin-rainbow 'https://mcp.thebitcoinrainbow.com/mcp'
Common questions

What is the The Bitcoin Rainbow MCP server?

The Bitcoin Rainbow is an MCP server listed in the public MCP registry as com.thebitcoinrainbow/the-bitcoin-rainbow. Explains the Bitcoin rainbow valuation chart and where price sits in the cycle today. This page covers its hosted endpoint (https://mcp.thebitcoinrainbow.com/mcp).

Is the The Bitcoin Rainbow MCP server safe to use?

The Bitcoin Rainbow 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 The Bitcoin Rainbow MCP server expose?

The Bitcoin Rainbow exposes 5 tools: rainbow_today, simulate_dca, rainbow_history, cycle_check, explain_bitcoin. Their descriptions and schemas cost roughly 1,448 tokens of context every time the server is loaded.

Does the The Bitcoin Rainbow MCP server require authentication?

No. We connected to The Bitcoin Rainbow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Bitcoin Rainbow MCP server still maintained?

The Bitcoin Rainbow is still listed as active 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 The Bitcoin Rainbow MCP server?

VerifyMCP ran 13 checks on The Bitcoin Rainbow, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.