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.

SatoshiMacro Market Data

REMOTE · SATOSHIMACRO.COM

Live crypto cycle data: 48-signal Bitcoin cycle model, Bitcoin ETF flows, ASX ETFs, altseason

Available components

+2 this week 84 Trust /100

Last scanned (5 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 979 tokens (~163/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • Manipulation not yet verified: only 1 of 7 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

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 5 Nov 2026 · Probed https://satoshimacro.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=satoshimacro.com CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA256 6e43f236f99eb9ce1332dfec4d0feb77
SANs: satoshimacro.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 satoshimacro.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
satoshimacro.com. absent 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://satoshimacro.com/mcp Verified 200
http (plaintext) http://satoshimacro.com/mcp HTTPS enforced 301 https://satoshimacro.com/mcp
MCP tools · 6 exposed · ~878 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
get_altcoin_season ~134

Current Altcoin Season Index (0-100: share of the top 50 coins by market cap, stablecoins and wrapped tokens excluded, that beat Bitcoin over the trailing 90 days; 75 or above is altcoin season, 25 or below is Bitcoin season) with the count of outperforming coins, Bitcoin's 90-day change and the last 12 month-end readings. Use this when the user asks whether it is altcoin season or how altcoins are performing against Bitcoin. Refreshed daily; history is month-end only, computed point-in-time from that date's top-50 ranking.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_australian_bitcoin_etfs ~114

Month-end assets under management (AUD millions) of the spot Bitcoin ETFs quoted on the ASX (VBTC, BTXX, QBTC, IBIT), by fund with issuer and management fee, plus the previous month's total. Use this for questions about Australian Bitcoin ETFs, their size or fees. Monthly data from the ASX Investment Products report, published a few weeks after month end, so it lags; it does not cover US-listed ETFs (use get_bitcoin_etf_flows).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_bitcoin_etf_flows ~144

Net daily flows into US spot Bitcoin ETFs in USD millions: the latest trading day split by fund (IBIT, FBTC, GBTC and others), 5-day and 30-day sums, and up to 30 recent daily totals (set days, default 10). Use this when the user asks about ETF inflows or outflows, institutional demand or a specific fund's flow. US trading days only, so weekends and US holidays have no entry; the latest day usually lags one US session. Flows only, not fund holdings or prices.

NameTypeReqDescription
daysinteger–Number of recent daily totals to return (default 10)

No output schema declared.

No examples provided.

get_cycle_indicators ~153

Latest readings of four individual Bitcoin cycle indicators (MVRV Z-Score using a 4-year moving-average proxy, Risk Metric, 200-week moving average rate of change, Pi Cycle Bottom ratio), each with a percentile zone from the full price history and its own date, plus the latest BTC price in AUD and USD. Use this when the user asks about a specific on-chain or valuation indicator or wants the components behind a cycle view; use get_cycle_model_reading for the combined 48-signal score. Daily and monthly indicators are mixed, so check each reading's date. USD price is derived from AUD at the daily AUDUSD rate and can differ from global USD quotes by 1-2%.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cycle_model_reading ~209

Current SatoshiMacro Model (SMM) score for Bitcoin or Ethereum: a 0-100 market-cycle confluence score built from weighted percentile-ranked signals in six tiers (cycle timing, valuation, sentiment, rotation, miner, macro; Bitcoin uses 48 signals, Ethereum fewer). Returns the zone (Deep Value, Accumulation, Neutral, Caution, Distribution, Cycle Top), 7- and 30-day change, the six tier scores and 30 days of daily history. Use this when the user asks where Bitcoin or Ethereum sits in its market cycle, how the cycle score has moved recently, or which tier is driving it; use get_market_snapshot instead for a one-line overview of everything. Daily reading, refreshed twice a day (about 07:30 and 13:30 Sydney time); the date field is the last completed day. Descriptive data, not a price forecast or trading signal.

NameTypeReqDescription
assetstring–BTC (default) or ETH

No output schema declared.

No examples provided.

get_market_snapshot ~124

One-call overview of the whole dataset: Bitcoin and Ethereum SMM scores and zones, BTC price (AUD/USD), Altcoin Season Index, the latest US spot Bitcoin ETF daily flow, ASX Bitcoin ETF assets and the Crypto Fear & Greed Index (the only tool that returns Fear & Greed). Use this for broad questions like 'how is the crypto market looking' or when the user wants several readings at once; call the specific tool instead when the user needs history, per-fund detail or tier breakdowns. Each line carries its own date and source page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the SatoshiMacro Market Data MCP server?

SatoshiMacro Market Data is a hosted endpoint at https://satoshimacro.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 · satoshimacro.com

# add to Claude Code
claude mcp add --transport http com-satoshimacro-market-data 'https://satoshimacro.com/mcp'
Common questions

What is the SatoshiMacro Market Data MCP server?

SatoshiMacro Market Data is an MCP server listed in the public MCP registry as com.satoshimacro/market-data. Live crypto cycle data: 48-signal Bitcoin cycle model, Bitcoin ETF flows, ASX ETFs, altseason. This page covers its hosted endpoint (https://satoshimacro.com/mcp).

Is the SatoshiMacro Market Data MCP server safe to use?

SatoshiMacro Market Data scores 84 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 SatoshiMacro Market Data MCP server expose?

SatoshiMacro Market Data exposes 6 tools: get_cycle_model_reading, get_cycle_indicators, get_altcoin_season, get_bitcoin_etf_flows, get_australian_bitcoin_etfs, get_market_snapshot. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.

Does the SatoshiMacro Market Data MCP server require authentication?

No. We connected to SatoshiMacro Market Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SatoshiMacro Market Data MCP server still maintained?

SatoshiMacro Market Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.