_ registry / mcp streamable-http · checked 3h ago

satoshimacro

https://satoshimacro.com

Registry code: da89be4cd7052f65

api record

Live crypto market-cycle data from SatoshiMacro (satoshimacro.com): the SatoshiMacro Model (a 48-signal Bitcoin cycle score, plus an Ethereum variant), on-chain cycle indicators, Altcoin Season Index, US spot Bitcoin ETF flows, Australian (ASX) Bitcoin ETF assets, and the Crypto Fear & Greed Index. Readings refresh twice daily. Each result includes the satoshimacro.com page it comes from. Data is informational, not financial advice.

endpoint
https://satoshimacro.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is satoshimacro live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is satoshimacro free to use?
Yes — the hub reached it with no key and no payment.
What tools does satoshimacro have?
6 tools: get_bitcoin_etf_flows, get_cycle_indicators, get_cycle_model_reading, get_market_snapshot, get_altcoin_season, get_australian_bitcoin_etfs.
Is satoshimacro safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 98.7%· all time 98.7%

latency
139ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 383 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get bitcoin market cycle score
  • get bitcoin etf flows
  • get altcoin season index
  • get crypto fear and greed index
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 open 6 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_bitcoin_etf_flows reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 30,
          "minimum": 1,
          "description": "Number of recent daily totals to return (default 10)"
        }
      }
    }
    arguments 11 lines
  • get_cycle_indicators reads open 3h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_cycle_model_reading reads open 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "asset": {
          "enum": [
            "BTC",
            "ETH"
          ],
          "type": "string",
          "description": "BTC (default) or ETH"
        }
      }
    }
    arguments 13 lines
  • get_market_snapshot reads open 3h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_altcoin_season reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_australian_bitcoin_etfs reads open 9h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id da89be4cd7052f65.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/da89be4cd7052f65/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/da89be4cd7052f65/badge.svg)](https://brick.blue/agent/da89be4cd7052f65?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.