Blocklens MCP Server

Bitcoin on-chain analytics: 85+ metrics including MVRV, SOPR, realized price, holder data. Exposed over MCP by the blocklens mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP (Model Context Protocol) server for Blocklens Bitcoin on-chain analytics. Connect your AI agent to 127 on-chain metrics computed from raw blockchain data — no API wrappers, no delays.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• list_metrics — List all 127 available metrics with categories and tiers
• search_metrics — Search metrics by keyword
• get_metric — Get full definition of a single metric
• get_categories — List metric categories with counts
• get_prices — BTC daily OHLC, market cap, volume, drawdown, realized volatility (1W–1Y)
• get_holder_supply — LTH/STH supply breakdown, circulating supply
• get_holder_valuation — Realized cap/price, MVRV, thermo cap, delta cap, balanced price, investor cap
• get_holder_profit — NUPL, realized/unrealized P/L, SOPR — LTH/STH breakdowns (Pro tier)
• get_cohort_metrics — Age cohort supply, realized cap, realized price (12 age brackets)
• get_utxo_history — UTXO set breakdown by age cohort
• get_coindays — Coin Days Destroyed, liveliness, vaultedness, dormancy, dormancy flow
• get_blockchain — Block height, blocks mined

Configuration

You will need one environment variable: BLOCKLENS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Blocklens.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the blocklens mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Blocklens's toolset — list_metrics, search_metrics, get_metric and 11 more — is a fair guide to whether it matches your workflow. It is maintained by blocklens; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.