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

explore21-mcp

https://data.explore21.com

Registry code: a628965e787df386

api record

Bitcoin on-chain data from Explore21 (realized price, MVRV, HODL waves and more), computed from our own Bitcoin Core node. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user. Start with long_term_snapshot for "where are we now".

endpoint
https://data.explore21.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 explore21-mcp live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is explore21-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does explore21-mcp have?
5 tools: get_metric, explain_metric, search_learn, long_term_snapshot, list_metrics.
Is explore21-mcp 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 100%· all time 100%

latency
200ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • long_term_snapshot open 8h ago

    Where Bitcoin stands today for a long-term holder: BTC daily close (USD); MVRV ratio; MVRV Z-Score; Realized price (USD); Short-term holder realized price (USD); % of supply in profit; Mayer Multiple; 200-week moving average (USD); Price vs 200-week moving average (%); Puell Multiple; Hashrate, 7-day average (H/s); Mining difficulty; Average block interval per epoch (seconds). Each comes with its Percentile Rank in its own history and its value at past cycle tops and lows. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_metrics open 8h ago

    Every Bitcoin metric Explore21 publishes, with its id and what it measures. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_metric unknown 34h ago

    One metric's daily values as CSV, oldest first. Without from/to it returns the last 365 days; pass from (and to) as yyyy-MM-dd for other ranges. Use list_metrics for the ids. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "bitcoin-mvrv-z-score",
            "bitcoin-price",
            "bitcoin-mayer-multiple",
            "bitcoin-200-week-moving-average",
            "bitcoin-hodl-waves",
            "bitcoin-hashrate",
            "bitcoin-mining-difficulty",
            "bitcoin-puell-multiple",
            "bitcoin-block-interval",
            "bitcoin-block-size",
            "bitcoin-transactions-per-day",
            "bitcoin-mvrv-ratio",
            "bitcoin-realized-price",
            "bitcoin-percent-supply-in-profit",
            "bitcoin-realized-cap",
            "bitcoin-realized-profit-loss"
          ],
          "type": "string",
          "description": "The metric id, e.g. bitcoin-mvrv-ratio."
        },
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Last UTC day, yyyy-MM-dd."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First UTC day, yyyy-MM-dd."
        }
      }
    }
    arguments 41 lines
  • explain_metric unknown 2d ago

    What a metric measures, its columns and units, its method version and every change to how it is computed, and its chart page. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "bitcoin-mvrv-z-score",
            "bitcoin-price",
            "bitcoin-mayer-multiple",
            "bitcoin-200-week-moving-average",
            "bitcoin-hodl-waves",
            "bitcoin-hashrate",
            "bitcoin-mining-difficulty",
            "bitcoin-puell-multiple",
            "bitcoin-block-interval",
            "bitcoin-block-size",
            "bitcoin-transactions-per-day",
            "bitcoin-mvrv-ratio",
            "bitcoin-realized-price",
            "bitcoin-percent-supply-in-profit",
            "bitcoin-realized-cap",
            "bitcoin-realized-profit-loss"
          ],
          "type": "string",
          "description": "The metric id, e.g. bitcoin-realized-price."
        }
      }
    }
    arguments 31 lines
  • search_learn unknown 8h ago

    Find Explore21's teaching pages: the course «Биткойн от нулата» (Bitcoin from zero), the guides and the glossary words, in English and Bulgarian. Returns titles, links and a short excerpt; link the page rather than retelling it. Show the closing "Source:" line to the user.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "bg"
          ],
          "type": "string",
          "description": "Which language comes first; guessed from the query if left out."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "The words to search for, in English or Bulgarian."
        }
      }
    }
    arguments 23 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 a628965e787df386.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a628965e787df386/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/a628965e787df386/badge.svg)](https://brick.blue/agent/a628965e787df386?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
90%

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.