io.github.blocklens/blocklens-mcp-server
NPM · BLOCKLENS-MCP-SERVER · SCANNED SEP 20
Bitcoin on-chain analytics — 109 metrics: MVRV, SOPR, NUPL, HODL Waves, CDD, cycles & more
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 125 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2537 tokens (~158/item across 16 items; 15 tools + 1 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.blocklens/blocklens-mcp-server server?
io.github.blocklens/blocklens-mcp-server runs locally as an npm package, launched with npx -y blocklens-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · blocklens-mcp-server
claude mcp add blocklens-blocklens-mcp-server -- npx -y blocklens-mcp-server
{
"mcpServers": {
"blocklens-blocklens-mcp-server": {
"command": "npx",
"args": [
"-y",
"blocklens-mcp-server"
]
}
}
} {
"servers": {
"blocklens-blocklens-mcp-server": {
"command": "npx",
"args": [
"-y",
"blocklens-mcp-server"
]
}
}
} codex mcp add blocklens-blocklens-mcp-server -- npx -y blocklens-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"blocklens-blocklens-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"blocklens-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add blocklens-blocklens-mcp-server --command npx --arg -y --arg blocklens-mcp-server
mcp_servers:
blocklens-blocklens-mcp-server:
command: "npx"
args: ["-y", "blocklens-mcp-server"] {
"McpServers": {
"blocklens-blocklens-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"blocklens-mcp-server"
]
}
}
} assistant mcp add blocklens-blocklens-mcp-server -t stdio -c npx -a -y blocklens-mcp-server
{
"mcpServers": {
"blocklens-blocklens-mcp-server": {
"command": "npx",
"args": [
"-y",
"blocklens-mcp-server"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/blocklens-mcp-server@0.4.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_blockchain ~92
Get blockchain network metrics: block height or daily blocks mined.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| metric | string | yes | Blockchain metric: "block_height" or "blocks_mined" |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_categories ~39
List all metric categories with counts and metric IDs in each. Categories include: price, supply, valuation, profit. Useful for discovering what data is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_cohort_metrics ~207
Get age cohort metrics: supply (BTC), realized cap (USD), and realized price (USD) for a specific UTXO age bracket. 12 cohorts from <24h to 10y+. Used for HODL Waves analysis to track accumulation/distribution by coin age.
| Name | Type | Req | Description |
|---|---|---|---|
| cohort | string | yes | Age cohort: 24h, 1d_1w, 1w_1m, 1m_3m, 3m_6m, 6m_12m, 1y_2y, 2y_3y, 3y_5y, 5y_7y, 7y_10y, 10y_plus |
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_coindays ~118
Get Coin Days metrics: CDD, binary CDD, supply-adjusted CDD, liveliness, vaultedness, dormancy, dormancy flow, transferred price, and transfer volume. Coin Days measure the economic weight of Bitcoin transactions by accounting for both amount and holding time.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_cycle_performance ~129
Get Bitcoin cycle performance data. Shows price progression indexed from cycle reference points (lows, ATHs, halvings). Without type parameter returns aggregate cycle comparison; with type returns individual cycle tracks.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
| type | string | – | Cycle reference point type: "low", "ath", or "halving". Omit for aggregate comparison. |
No output schema declared.
No examples provided.
get_holder_profit ~110
Get Bitcoin profit metrics: LTH/STH Realized P/L (USD) and SOPR (Spent Output Profit Ratio). SOPR > 1 means coins moved at profit; < 1 means at loss. Requires Pro tier API key.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_holder_supply ~109
Get Bitcoin holder supply breakdown: Long-Term Holder (LTH) supply, Short-Term Holder (STH) supply, and circulating supply. LTH = held >155 days, STH = held <155 days. Values in BTC.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_holder_valuation ~127
Get Bitcoin valuation metrics: Realized Cap (USD), Realized Price (USD), LTH/STH Realized Cap and Price, MVRV ratio (Market Value / Realized Value), and Unrealized P/L. MVRV > 3.5 historically signals overheating; < 1 signals undervaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
No output schema declared.
No examples provided.
get_latest_metrics ~43
Get the most recent snapshot across all metric categories (price, supply, valuation, profit) in a single call. Ideal for a quick market overview without specifying date ranges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_metric ~78
Get the full definition of a single metric by its ID. Returns name, description, category, endpoint, unit, access tier, documentation, and related metrics. Use search_metrics or list_metrics first to find metric IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | string | yes | Metric identifier (e.g. "lth_supply", "price", "sth_sopr") |
No output schema declared.
No examples provided.
get_prices ~107
Get daily OHLC prices (open/high/low/close in USD), market cap, and 24h trading volume. Returns one row per day, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of daily data points to return |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days param when set. |
| symbol | string | – | Cryptocurrency symbol (default: BTC) |
No output schema declared.
No examples provided.
get_utxo_history ~127
Get UTXO set breakdown by age cohort. Shows token amounts (BTC) and USD values for each cohort date. Useful for analyzing coin dormancy and accumulation patterns — when dormant supply moves, it often precedes price action.
| Name | Type | Req | Description |
|---|---|---|---|
| cohort_end | string | – | End of cohort date range (YYYY-MM-DD) |
| cohort_start | string | – | Start of cohort date range (YYYY-MM-DD) |
| date_processed | string | – | Specific processing date (YYYY-MM-DD). Returns the UTXO snapshot for that day. |
| days | integer | – | Number of records to return |
No output schema declared.
No examples provided.
list_metrics ~43
List all available on-chain metrics with descriptions, categories, and tier requirements. Returns id, name, description, category, unit, endpoint, and access tier for each metric.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_chart ~1,123
Render a Bitcoin on-chain analytics chart as a PNG image. Supports single metrics, multiple metrics, templates, computed formulas, and full customization. Use this when the user asks to "show", "chart", "plot", "graph", or "visualize" any metric. Smart defaults: just provide metric IDs and you get a beautiful chart. Customize with optional params. Supports custom Y-axes with vertical zones (stack volume below price), domain clamping, reference lines, reference areas, and computed formula series. IMPORTANT — Multi-axis guidance for different units: When combining metrics with different units (e.g., BTC supply + USD price, or a dimensionless ratio + USD), ALWAYS place them on separate Y-axes. Otherwise one metric will appear as a flat line near zero due to scale mismatch. Use list_metrics to check the "unit" field and assign metrics with different units to different axes (left vs right). Examples: - Simple: render_chart({ metric: "price" }) - Multi-metric: render_chart({ metrics: ["lth_supply", "sth_supply"], days: 730, style: "area" }) - Template: render_chart({ template: "mvrv_ratio" }) - Custom: render_chart({ metrics: [{ id: "price", axis: "right" }, { id: "lth_mvrv", axis: "left" }], days: 365, title: "Price vs MVRV" }) - Multi-unit (separate axes): render_chart({ metrics: [{ id: "lth_supply", axis: "left" }, { id: "price", axis: "right" }], days: 365 }) - Vertical zones: render_chart({ metrics: [{ id: "price", y_axis_id: "ax-p" }, { id: "volume", y_axis_id: "ax-v", style: "bar" }], y_axes: [{ id: "ax-p", side: "right", range: [20, 100] }, { id: "ax-v", side: "left", range: [0, 20] }] }) - Reference line: render_chart({ metric: "lth_mvrv", reference_lines: [{ y: 3.5, label: "Overheated", stroke: "#ef4444", dash: "3 3" }] }) - Reference area: render_chart({ metric: "lth_mvrv", reference_areas: [{ y1: 0, y2: 0.85, label: "Undervalued", fill: "#22c55e", fill_opacity: 0.15 }] }) - Formula (ratio): render_chart({ metrics: [{ id: "lth_supply" }, { id: "sth_supply…
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days of history (default: 365) |
| end_date | string | – | End date (YYYY-MM-DD). Defaults to today. |
| format | string | – | Output format: png (image) or json (metadata) |
| formulas | array | – | Computed series derived from metric data. Formulas reference metrics by position (m1, m2, ...) and support arithmetic (+, -, *, /). Use together with metrics to add derived indicators. |
| height | integer | – | Image height in pixels |
| metric | string | – | Single metric ID (e.g., "price", "lth_supply", "lth_mvrv"). Use list_metrics to discover IDs. |
| metrics | – | – | Multiple metrics. Pass as string array ["price", "lth_supply"] for simple, or objects for customization. |
| overlay | string | – | Add BTC price overlay (subtle dashed line) |
| reference_areas | array | – | Shaded reference zones between two Y values. Example: highlight when MVRV < 0.85 |
| reference_lines | array | – | Horizontal reference lines on the chart |
| scale | string | – | Y-axis scale |
| start_date | string | – | Start date (YYYY-MM-DD). Overrides days. |
| style | string | – | Default chart style for all metrics |
| template | string | – | Chart template ID. Templates: price, price_volume, market_cap, holder_supply, mvrv_ratio, realized_price, realized_cap, unrealized_pl, realized_pl, sopr, block_height, realized_volatility, coindays_d… |
| theme | string | – | Color theme: light or dark |
| title | string | – | Chart title (auto-generated if omitted) |
| width | integer | – | Image width in pixels |
| y_axes | array | – | Custom Y-axes with vertical zones. Use range to stack axes (e.g. volume [0,20], price [20,100]). Use domain_min/domain_max to clamp axis bounds. |
No output schema declared.
No examples provided.
search_metrics ~70
Search available metrics by name or description. Returns matching metrics with their IDs, API endpoints, access tiers, and descriptions. Use this to discover which metrics are available before fetching data.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (e.g. "realized price", "supply", "MVRV") |
No output schema declared.
No examples provided.
What is the io.github.blocklens/blocklens-mcp-server server?
io.github.blocklens/blocklens-mcp-server is listed in the public MCP registry as io.github.blocklens/blocklens-mcp-server. Bitcoin on-chain analytics, 109 metrics: MVRV, SOPR, NUPL, HODL Waves, CDD, cycles & more. This page covers its npm package (blocklens-mcp-server).
Is the io.github.blocklens/blocklens-mcp-server server safe to use?
io.github.blocklens/blocklens-mcp-server scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.blocklens/blocklens-mcp-server server expose?
io.github.blocklens/blocklens-mcp-server exposes 15 tools: list_metrics, get_prices, get_holder_supply, get_holder_valuation, get_holder_profit, and 10 more. Their descriptions and schemas cost roughly 2,522 tokens of context every time the server is loaded.
Is the io.github.blocklens/blocklens-mcp-server server still maintained?
io.github.blocklens/blocklens-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.blocklens/blocklens-mcp-server server under?
io.github.blocklens/blocklens-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.