Skip to content

The Bitcoin Rainbow

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

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

3 tools: 2 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those 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 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 →

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.

3 tools

Changes things 2Claude Code: ask
  • 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
  • explain_bitcoinOne short plain-English explainer, the same text the website shows.Reads text others writeNo findings

    Why it is in this group

    • The name "explain_bitcoin" says "explain": 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
    One short plain-English explainer, the same text the website shows. Topic 'price': what price means, with the live price printed with its UTC quote time (the same shared quote the other tools print). 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 'rainbow': what the growth chart is and what its colors mean, with today's price printed with its UTC quote time. Topic 'ways_to_buy': the two plain ways people buy, IBIT in a stock account or an exchange app, facts only. Descriptive only; no advice.

    Annotations the server declares

    • title: Explain bitcoin in plain words
    • 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 write3
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 5, 2026, 03:19 UTC, unchanged since Nov 5, 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
2
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 2 tools that change things (2 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 3 tools to an anonymous client, including rainbow_today (write), simulate_dca (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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__explain_bitcoin"
    ],
    "ask": [
      "mcp__the-bitcoin-rainbow__rainbow_today",
      "mcp__the-bitcoin-rainbow__simulate_dca"
    ],
    "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 3 rules
  • mcp__the-bitcoin-rainbow__rainbow_today untrusted-input
  • mcp__the-bitcoin-rainbow__simulate_dca 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://anlyon.dev/api/v1/servers/com.thebitcoinrainbow/the-bitcoin-rainbow/verify?hash=73bd11e91918a39b32e2a8b26bd437ff1d0064a34e021bb741d2b75729c696b1" | jq -e '.changed == false'

Pinned hash 73bd11e91918, from Nov 5, 2026, 04:18 UTC.

Watch

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

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

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

Badge

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

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