MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Payments & trading

BTC Intel

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

Checks passed
13 / 22

1 failed · 8 not measured

Median response
60 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
13

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 60 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name btc-intel.

  • Pass
    Lists tools

    tools/list returned 13 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 60 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 60 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    31 of 31 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-07T17:03:59.661514Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using BTC Intel

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http btc-intel https://btcintel.org/mcp

Capabilities

Tools 13

get_area

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.

Discovered
get_bitcoin_today

Use for "what is Bitcoin doing and why", first: one morning briefing from BTC Intel's published Brief and Full Read. 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.

Discovered
get_calendar

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.

Discovered
get_classification_history

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

Discovered
get_market_detail

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

Discovered
get_methodology

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.

Discovered
get_plan_rules

Use for the published Intel DCA ladder: what each plan (Defensive, Balanced, Growth) does on payday 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 payday 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.

Discovered
get_read_for_day

Use for a past day's record, by date: the Full Read 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).

Discovered
get_score_for_day

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

Discovered
get_score_history

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.

Discovered
get_score_live

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.

Discovered
get_score_momentum

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.

Discovered
get_score_statistics

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected60 ms13