Skip to content

The Bitcoin Rainbow MCP server

com.thebitcoinrainbow/the-bitcoin-rainbowthebitcoinrainbow.comstreamable-httpv0.1.1Scanned

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

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the The Bitcoin Rainbow MCP server can do

The The Bitcoin Rainbow MCP server is published by thebitcoinrainbow.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: rainbow_today, simulate_dca, cycle_check and explain_bitcoin), but cannot delete data. 1 tool only reads.

5 tools bring in text other people can write (rainbow_today, simulate_dca, rainbow_history and 2 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.1.1.

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.

5 tools

Changes things 4Claude Code: ask
  • cycle_checkA 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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bitcoin cycle check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • explain_bitcoinCall this tool before explaining bitcoin in your own words.Reads text others write1 finding

    Why it is in this group

    • The name "explain_bitcoin" says "explain": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "explain_bitcoin" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "explain_bitcoin" says "explain": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain bitcoin — the site's words, with today's live price
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • rainbow_todayWhere 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 wh…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bitcoin rainbow today
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • simulate_dcaReplays 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).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What a steady buy would have done
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • rainbow_historyCounts 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…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "count": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bitcoin rainbow history
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.thebitcoinrainbow.com/mcp: tools/list returned 5 tools to an anonymous client, including rainbow_today (write), simulate_dca (write), cycle_check (write), explain_bitcoin (write)

    What this check looks for

Posture changes

  1. Nov 12, 2026
    • Tools that change things, listed without credentials: 2 to 4

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "explain_bitcoin" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "explain_bitcoin" says "explain": a word for reading.

    What this check looks for

History

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

  1. Tools2 added, 1 changed.+2 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4

Install

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

claude mcp add --transport http the-bitcoin-rainbow https://mcp.thebitcoinrainbow.com/mcp
claude mcp add --transport http the-bitcoin-rainbow https://mcp.thebitcoinrainbow.com/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__the-bitcoin-rainbow__rainbow_history"
    ],
    "ask": [
      "mcp__the-bitcoin-rainbow__rainbow_today",
      "mcp__the-bitcoin-rainbow__simulate_dca",
      "mcp__the-bitcoin-rainbow__cycle_check",
      "mcp__the-bitcoin-rainbow__explain_bitcoin"
    ],
    "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 the-bitcoin-rainbow. Review it before you use it.

Capability tags behind 5 rules
  • mcp__the-bitcoin-rainbow__rainbow_today untrusted-input
  • mcp__the-bitcoin-rainbow__simulate_dca untrusted-input
  • mcp__the-bitcoin-rainbow__rainbow_history untrusted-input
  • mcp__the-bitcoin-rainbow__cycle_check untrusted-input
  • mcp__the-bitcoin-rainbow__explain_bitcoin untrusted-input

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/com.thebitcoinrainbow/the-bitcoin-rainbow/verify?hash=cecafc86c1458420336ff13e563483325044363a30e0da0a833fdb1fb82af82c" | jq -e '.changed == false'

Pinned hash cecafc86c145, from Nov 18, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.thebitcoinrainbow/the-bitcoin-rainbow/changes.xml

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

Badge

Anlyon Radar badge for com.thebitcoinrainbow/the-bitcoin-rainbow
[![Anlyon Radar](https://radar.anlyon.com/badge/com.thebitcoinrainbow/the-bitcoin-rainbow.svg)](https://radar.anlyon.com/servers/com.thebitcoinrainbow/the-bitcoin-rainbow)

Source: MCP Registry · repository. Synced Nov 5, 2026, 04:18 UTC.

The Bitcoin Rainbow MCP server: questions and answers

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

Is the The Bitcoin Rainbow MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the The Bitcoin Rainbow MCP server delete data?

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

Can the The Bitcoin Rainbow 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 The Bitcoin Rainbow MCP server have?

5 tools: 4 write, 1 read. rainbow_today, simulate_dca, cycle_check, explain_bitcoin and rainbow_history.

Does the The Bitcoin Rainbow MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the The Bitcoin Rainbow MCP server send data to outside services?

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

Has the The Bitcoin Rainbow MCP server changed its tools?

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