Skip to content

BTC Intel MCP server

org.btcintel/btc-intelbtcintel.orgstreamable-httpv1.1.0Scanned

Understand where Bitcoin is today, compared with its own history: 0–100 Score and stats since 2011.

13 tools: 13 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 BTC Intel MCP server can do

The BTC Intel MCP server is published by btcintel.org, a domain the MCP Registry verified. It has 13 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (get_calendar and get_plan_rules); 1 tool brings in text other people can write (get_score_live).

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

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

Last scanned Nov 21, 2026, version 1.1.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.

13 tools

Only reads 13Show 13 read-only tools
  • get_areaUse for one named area of the market ("how is on-chain?", "what is liquidity saying?"), as its Analysis page shows it today: the read, how confident it is and when it last changed,…No findings

    Why it is in this group

    • The name "get_area" says "get": a word for reading.
    Description, as the server wrote it
    Use for one named area of the market ("how is on-chain?", "what is liquidity saying?"), as its Analysis page shows it today: the read, how confident it is and when it last changed, the read by horizon (days, weeks, months), the reasoning in plain English (what holds it up, what could change it) and the state of each of its parts. Areas: technical, on-chain, market-structure, sentiment and macro (the five areas of the read), and cross-market (how the five line up), liquidity (the price levels where forced buying and selling sit, funding and the next big options expiry) and cycle (where Bitcoin is in its four-year cycle). For every area at once with the price and the forces use get_bitcoin_today; for the parts of all five areas side by side get_market_detail. Free.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_bitcoin_todayUse for "what is Bitcoin doing and why", first: one morning briefing from BTC Intel's published Brief and Analysis Summary.No findings

    Why it is in this group

    • The name "get_bitcoin_today" says "get": a word for reading.
    Description, as the server wrote it
    Use for "what is Bitcoin doing and why", first: one morning briefing from BTC Intel's published Brief and Analysis Summary. It gives the price now with its 24-hour, 3-day and 12-month moves and the distance from the cycle high; the market read in one sentence; the five areas (Technical, On-chain, Market structure, Sentiment, Macro) with each one's reason and last change; the forces moving the market, each with the figures behind it (for example stablecoin supply, funding, ETF flows, VIX); what changed today, this week and this month; what would change the read; and the events coming up. detail "full" adds the full reasoning and 14 days of calendar instead of 7. For the calendar alone use get_calendar, for one area in depth get_area, for the BTC Intel Score get_score_for_day. The Brief is published at 6 AM ET; the price is rolling. Free.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_calendarUse for the events ahead that can move Bitcoin: macro releases (CPI, jobs, the Fed), options expiries, the difficulty adjustment and Bitcoin dates, each with its date, Eastern time…Reads private dataNo findings

    Why it is in this group

    • The name "get_calendar" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_calendar" says "get" and "calendar": it reads calendars.
    Description, as the server wrote it
    Use for the events ahead that can move Bitcoin: macro releases (CPI, jobs, the Fed), options expiries, the difficulty adjustment and Bitcoin dates, each with its date, Eastern time and one line on why it matters. Example: days 3 lists what lands before the weekend. For today's read and its forces use get_bitcoin_today. Free.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_classification_historyUse for the periods the Score spent in each classification (Low, Moderate-low, Neutral, Elevated, High): the start, end and length in days of each, newest first, 100 a page, each m…No findings

    Why it is in this group

    • The name "get_classification_history" says "get": a word for reading.
    Description, as the server wrote it
    Use for the periods the Score spent in each classification (Low, Moderate-low, Neutral, Elevated, High): the start, end and length in days of each, newest first, 100 a page, each marked live or backtested. Choose it to see when a classification last held and for how long; for daily values use get_score_history, for shares and counts across the record get_score_statistics. Free through the Delayed date (the free cut-off, three months before the latest published day). A later "to", or live = true, costs $0.25 in bitcoin over Lightning, one payment for every page of that query, no subscription: the first call returns an invoice instead of data (steps under payment).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_market_detailUse for the five market areas broken into their published components: each area (Technical, On-chain, Market structure, Sentiment, Macro) with its state on the five-step scale (Adv…No findings

    Why it is in this group

    • The name "get_market_detail" says "get": a word for reading.
    Description, as the server wrote it
    Use for the five market areas broken into their published components: each area (Technical, On-chain, Market structure, Sentiment, Macro) with its state on the five-step scale (Adverse, Cautionary, Neutral, Constructive, Supportive), explanation, last change and edition time, and its components (26 in all), each with its state and position (Sentiment's Public mood also gives the crowd's mood in plain words and what that level has meant historically). Choose it for component-level detail; for today's read with its forces use get_bitcoin_today, for one area in depth get_area; for the live Score with the five areas use get_score_live. Free. The published market read, as on the Analysis pages. The market components describe the published market read. The BTC Intel Score is computed separately.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_methodologyUse for definitions, not data: what the Score is, its five classifications, the record's dates, how it is published and checked, and what live, backtested, historical position and …No findings

    Why it is in this group

    • The name "get_methodology" says "get": a word for reading.
    Description, as the server wrote it
    Use for definitions, not data: what the Score is, its five classifications, the record's dates, how it is published and checked, and what live, backtested, historical position and the Delayed date mean. The method itself is private. For Score values use get_score_for_day or get_score_live; for the Intel DCA rules get_plan_rules. Free, no arguments; one text document.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_plan_rulesUse for the published Intel DCA ladder: what each plan (Defensive, Balanced, Growth) does on contribution day in each Score band (buy, save, or sell a set share once), word for wor…Reads private dataNo findings

    Why it is in this group

    • The name "get_plan_rules" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    Use for the published Intel DCA ladder: what each plan (Defensive, Balanced, Growth) does on contribution day in each Score band (buy, save, or sell a set share once), word for word from btcintel.org/intel-dca/, with the notes under the ladder. Example: plan Balanced with score 34 returns the 20 to 39 band of the Balanced plan and its contribution day action there. Rules only: no personal plan, no advice, no backtest. For the Score to read the ladder against use get_score_for_day or get_score_live; for what the classifications mean get_methodology. Free.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_read_for_dayUse for a past day's record, by date: the Analysis Summary and the five market areas with their state words (Adverse, Cautionary, Neutral, Constructive or Supportive) as stored tha…No findings

    Why it is in this group

    • The name "get_read_for_day" says "get": a word for reading.
    Description, as the server wrote it
    Use for a past day's record, by date: the Analysis Summary and the five market areas with their state words (Adverse, Cautionary, Neutral, Constructive or Supportive) as stored that day, and for the latest stored day the Brief's headline. Choose it to look up what the read was on a given day; for today use get_bitcoin_today, for the areas' 26 components get_market_detail, for the Score get_score_for_day. The stored reads begin in October 2026, so free answers start in early January 2027. Free through the Delayed date (the free cut-off, three months before the latest published day). A later date, or live = true for the latest day with its headline, costs $0.25 in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_score_for_dayUse for the Score on one day: its value (0–100), its classification (Low, Moderate-low, Neutral, Elevated or High) and whether the day is live or backtested (daily since July 18, 2…No findings

    Why it is in this group

    • The name "get_score_for_day" says "get": a word for reading.
    Description, as the server wrote it
    Use for the Score on one day: its value (0–100), its classification (Low, Moderate-low, Neutral, Elevated or High) and whether the day is live or backtested (daily since July 18, 2011, backtested with the current method before live publication). Choose it for a single day; for today's Score with its historical position and the five market areas use get_score_live, for a run of days get_score_history, for recent change get_score_momentum. Free through the Delayed date (the free cut-off, three months before the latest published day). A later day, or live = true, costs $0.25 in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_score_historyUse for the raw daily series: one row per day with the Score, its classification and a live or backtested mark (daily since July 18, 2011, backtested with the current method before…No findings

    Why it is in this group

    • The name "get_score_history" says "get": a word for reading.
    Description, as the server wrote it
    Use for the raw daily series: one row per day with the Score, its classification and a live or backtested mark (daily since July 18, 2011, backtested with the current method before live publication), as JSON or CSV, 100 rows a page. Choose it to chart or export values; for one day use get_score_for_day, for summaries get_score_statistics, for classification periods get_classification_history. Free through the Delayed date (the free cut-off, three months before the latest published day). A later "to", or live = true, costs $0.25 in bitcoin over Lightning, one payment for every page of that query, no subscription: the first call returns an invoice instead of data (steps under payment). Example: from 2024-01-01, to 2024-03-31 and format csv return that quarter as one table; a range longer than a page comes back in parts, so repeat the same call with page = next_page until next_page is null.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_score_liveUse for today's complete live picture in one paid call: the latest published BTC Intel Score (0–100) and its classification, its historical position (the share of recorded days bel…Reads text others writeNo findings

    Why it is in this group

    • The name "get_score_live" says "get": 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
    Use for today's complete live picture in one paid call: the latest published BTC Intel Score (0–100) and its classification, its historical position (the share of recorded days below and above it, daily since July 2011, backtested with the current method before live publication), and the five market areas (Technical, On-chain, Market structure, Sentiment, Macro), each with its state, position on the five-step scale and last change. Not for a past day (use get_score_for_day), a range of days (get_score_history), statistics (get_score_statistics) or the market areas alone (free: get_bitcoin_today or get_market_detail). Context, not a forecast. $0.25 per call in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment). Research, not investment advice.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_score_momentumUse for recent change: how many points the Score moved over 1, 7, 30 and 90 days, and how many days it has held its current classification.No findings

    Why it is in this group

    • The name "get_score_momentum" says "get": a word for reading.
    Description, as the server wrote it
    Use for recent change: how many points the Score moved over 1, 7, 30 and 90 days, and how many days it has held its current classification. Choose it to see whether the Score is rising or falling; for the values themselves use get_score_history, for averages and distributions get_score_statistics, for past classification periods get_classification_history. Free through the Delayed date (the free cut-off, three months before the latest published day). live = true reaches the latest published day and costs $0.25 in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment). Changes describe the past, not what comes next.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_score_statisticsUse for a summary of the record: the historical position (the share of recorded days below and above the latest reading), mean, median and range, days per 10-point band, the share …No findings

    Why it is in this group

    • The name "get_score_statistics" says "get": a word for reading.
    Description, as the server wrote it
    Use for a summary of the record: the historical position (the share of recorded days below and above the latest reading), mean, median and range, days per 10-point band, the share of days per classification, and counts of stretches and moves between classifications. Choose it to see how unusual a reading is; for the stretches themselves use get_classification_history, for daily values get_score_history, for recent change get_score_momentum. Free through the Delayed date (the free cut-off, three months before the latest published day). A later "to", or live = true, costs $0.25 in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment). The historical position describes where today's Score sits in the record, not what comes next.

    Annotations the server declares

    • readOnlyHint: 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 outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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 21, 2026, 19:22 UTC, unchanged since Nov 7, 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
0
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

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. Tools6 added, 5 removed, 7 changed.+6 added−5 removed~7 changedView diff
  2. Tools8 added, 1 removed, 4 changed.+8 added−1 removed~4 changedView diff

Install

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

claude mcp add --transport http btc-intel https://btcintel.org/mcp
claude mcp add --transport http btc-intel https://btcintel.org/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__btc-intel__get_bitcoin_today",
      "mcp__btc-intel__get_calendar",
      "mcp__btc-intel__get_area",
      "mcp__btc-intel__get_plan_rules",
      "mcp__btc-intel__get_score_live",
      "mcp__btc-intel__get_score_for_day",
      "mcp__btc-intel__get_score_momentum",
      "mcp__btc-intel__get_score_statistics",
      "mcp__btc-intel__get_score_history",
      "mcp__btc-intel__get_classification_history",
      "mcp__btc-intel__get_read_for_day",
      "mcp__btc-intel__get_methodology",
      "mcp__btc-intel__get_market_detail"
    ],
    "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 btc-intel. Review it before you use it.

Capability tags behind 3 rules
  • mcp__btc-intel__get_calendar private-data
  • mcp__btc-intel__get_plan_rules private-data
  • mcp__btc-intel__get_score_live 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/org.btcintel/btc-intel/verify?hash=08f880f5719850c7eb0eead43b04cf942cf6754fc37e4568ef6fb248041791ff" | jq -e '.changed == false'

Pinned hash 08f880f57198, from Nov 21, 2026, 23:17 UTC.

Watch

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

https://radar.anlyon.com/servers/org.btcintel/btc-intel/changes.xml

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

Badge

Anlyon Radar badge for org.btcintel/btc-intel
[![Anlyon Radar](https://radar.anlyon.com/badge/org.btcintel/btc-intel.svg)](https://radar.anlyon.com/servers/org.btcintel/btc-intel)

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

BTC Intel MCP server: questions and answers

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

Is the BTC Intel MCP server safe?

No scan can promise that. What its definitions show: 13 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 BTC Intel MCP server delete data?

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

Can the BTC Intel 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 BTC Intel MCP server have?

13 tools: 13 read. get_bitcoin_today, get_calendar, get_area, get_plan_rules, get_score_live, get_score_for_day, get_score_momentum, get_score_statistics and 5 more.

Does the BTC Intel MCP server need sign-in or OAuth?

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

Does the BTC Intel MCP server send data to outside services?

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

Has the BTC Intel MCP server changed its tools?

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