# Blockmetric (remote · api.blockmetric.io)

Read-only crypto market data: Hyperliquid liquidation heatmaps, liquidations, whales, funding, flow.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.blockmetric.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-blockmetric-mcp/api.md), [page](https://verifymcp.io/servers/io-blockmetric-mcp/api)
- npm · `blockmetric-mcp`: 66/100, [markdown](https://verifymcp.io/servers/io-blockmetric-mcp/blockmetric-mcp.md), [page](https://verifymcp.io/servers/io-blockmetric-mcp/blockmetric-mcp)

## Channel facts

- Endpoint: `https://api.blockmetric.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3091 tokens (~147/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Blockmetric MCP server?

Blockmetric is a hosted endpoint at https://api.blockmetric.io/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.

### Claude

```bash
claude mcp add --transport http io-blockmetric-mcp 'https://api.blockmetric.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-blockmetric-mcp": {
      "url": "https://api.blockmetric.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-blockmetric-mcp": {
      "type": "http",
      "url": "https://api.blockmetric.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-blockmetric-mcp]
url = "https://api.blockmetric.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-blockmetric-mcp": {
      "type": "remote",
      "url": "https://api.blockmetric.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-blockmetric-mcp --url 'https://api.blockmetric.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-blockmetric-mcp:
    url: "https://api.blockmetric.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-blockmetric-mcp": {
      "Transport": "http",
      "Url": "https://api.blockmetric.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-blockmetric-mcp -t streamable-http -u 'https://api.blockmetric.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-blockmetric-mcp": {
      "type": "http",
      "url": "https://api.blockmetric.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, 0)

- [cosmetic] “get_liquidation_heatmap” reworded the description of “tf”

### 2026-11-20 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_whales” rewrote its description, which is the text the model reads
- [functional] Server version: 0.6.0 → 0.6.1

### 2026-11-19 (score 74, 0)

- [functional] Server version: 0.5.0 → 0.6.0
- [cosmetic] “get_order_flow” reworded the description of “hours”

### 2026-11-18 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_candles” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “get_candles” added an optional parameter “price”
- [cosmetic] “get_candles” added an optional parameter “market”
- [cosmetic] “get_candles” reworded the description of “coin”

### 2026-11-17 (score 74)

First indexed and scored.

## MCP tools (21)

### `get_liquidation_heatmap` (~286 tokens)

Liquidation heatmap

Where liquidations WOULD happen for one coin: the liquidation heatmap over time built from real tracked Hyperliquid positions. Returns the largest clusters of liquidatable positions above the mark (shorts) and below it (longs) in the newest snapshot, with USD at risk and the distance from the mark. Use it for "where are the liquidation levels / magnets for BTC?". For liquidations that already happened use get_liquidations.

Input parameters:

- `coin` (string, required): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `end` (string): End of the window (default now). Set it to look at the heatmap of an earlier time.
- `hours` (integer): Look-back window in hours (default 24; capped by the plan history).
- `tf` (string): Column interval (default: chosen from hours: 15m up to 7 days, 1h up to 30 days, then 4h / 12h). Every key opens 5m to 1d within its plan history; without a key 5m, 15m and 1h over 24 hours; 1m needs…
- `top` (integer): Clusters per side (default 5).

### `get_liquidation_map` (~104 tokens)

Liquidation map (now)

Current liquidation levels of one coin from tracked Hyperliquid positions: USD of long and short positions per price bucket right now, with totals. A snapshot; for the history over time use get_liquidation_heatmap.

Input parameters:

- `coin` (string, required): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `top` (integer): Largest buckets per side (default 5).

### `get_liquidations` (~210 tokens)

Liquidations

Liquidations that HAPPENED: totals of the last hours (long/short USD, per venue, top coins, largest single liquidation) plus the latest individual liquidations the data licence allows, optionally only large ones (min_usd) or one side. Use it for "how much got liquidated today?" or "latest big liquidations".

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `hours` (integer): Window in hours (default 24; capped by the plan).
- `limit` (integer): Number of latest liquidations (default 5, at most 50).
- `min_usd` (integer): Only liquidations of at least this many USD in the latest list.
- `side` (string): Only liquidated longs or shorts in the latest list.
- `venue` (string): Only this venue for the latest liquidations list.

### `get_whales` (~160 tokens)

Whale leaderboard

Largest tracked Hyperliquid wallets with labels (and the label source), open notional, all-time PnL, largest position and its distance to liquidation. Use sort=near_liq for whales close to liquidation.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `labelled` (boolean): Only wallets with a public label from a cited source.
- `limit` (integer): Number of wallets (default 10, at most 50).
- `sort` (string): size = open notional (default), pnl = all-time PnL, near_liq = closest to liquidation, liquidated = most liquidations.

### `get_wallet` (~48 tokens)

Wallet detail

One tracked Hyperliquid wallet: account value, open positions with leverage and liquidation prices, totals and the latest position changes.

Input parameters:

- `address` (string, required): 0x address (40 hex characters).

### `get_funding` (~97 tokens)

Funding rates

Funding rates per coin across Hyperliquid and the exchanges the data licence allows (annualised, as fractions) and the spread between venues.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `limit` (integer): Number of coins, by Hyperliquid open interest (default 10, at most 50).

### `get_long_short` (~94 tokens)

Long/short positioning

Long/short positioning per coin: Hyperliquid from tracked positions (USD ratio) and, where the data licence allows, the account ratios the exchanges publish.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `limit` (integer): Number of coins (default 10, at most 50).

### `get_events` (~162 tokens)

Risk radar events

Risk radar events, newest first: whale moves, whales near liquidation, big liquidations, cascades, funding extremes and flips, open interest spikes, records, exploits/hacks, stablecoin depegs, TVL drops, exchange outflows. Use it for "what just happened?".

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `kinds` (array): Only these event kinds (default all).
- `limit` (integer): Number of events (default 10, at most 50).
- `min_severity` (integer): 1 info, 2 notable, 3 major, 4 critical (default 1).

### `get_candles` (~288 tokens)

Price candles

OHLC price candles of one coin (UTC-aligned) with volume: the price change, high and low over the window plus the newest candles. Use it for price context next to positioning or liquidation data. Optional: price oracle for the Hyperliquid oracle reference price (not a trade price), market spot for the trade candles of a Hyperliquid USDC spot pair.

Input parameters:

- `coin` (string, required): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). With market spot also a spot token name (UBTC, PURR) or a spot pair key (@142).
- `from` (string): Start (default: `limit` candles before `to`).
- `limit` (integer): Number of candles (default 24, at most 200).
- `market` (string): perp (default) or spot = trade candles of the Hyperliquid spot pair quoted in USDC. A coin without such a pair answers not_found.
- `price` (string): oracle = Hyperliquid oracle price candles of the perp market instead of the default series: a reference price, not a trade price, without volume. Not combinable with market spot.
- `tf` (string): Candle interval (default 1h).
- `to` (string): End, exclusive (default now).

### `get_screener` (~159 tokens)

Market screener

Every coin in one table: price and open-interest change, funding now and predicted, long/short, liquidations in 24 h, nearest liquidation cluster, RSI and volatility. Sort to find movers, crowded trades or extreme funding.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `dir` (string): desc (default) or asc.
- `limit` (integer): Number of coins (default 15, at most 50).
- `min_oi_usd` (integer): Only coins with at least this open interest (USD).
- `sort` (string): Sort column (default oi = open interest).

### `get_orderbook` (~123 tokens)

Order book and walls

Order book liquidity of one coin: depth within bands around the mid (bids vs asks, imbalance) and the largest walls with their status (active, pulled before the price arrived, filled). Use it for support / resistance from resting orders.

Input parameters:

- `coin` (string, required): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `venue` (string): Only this venue (default every venue the licence allows).
- `walls` (integer): Walls to list (default 8).

### `get_order_flow` (~142 tokens)

Order flow (CVD)

Taker flow of one coin over a window: buy vs sell volume, delta and cumulative volume delta in total, per venue, by print size and for tracked whales, plus the volume profile (point of control, value area). Use it for "who is buying BTC?".

Input parameters:

- `coin` (string, required): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `hours` (integer): Window in hours (default 24; clamped to the order-flow history of the plan: free keys and no key 24).
- `venue` (string): Only this venue.

### `get_large_trades` (~148 tokens)

Large-trade tape

The newest large taker prints (trades above the tape threshold) with side, price, size and whether a tracked whale was the taker.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `limit` (integer): Number of prints (default 20, at most 50).
- `min_usd` (integer): Only prints of at least this many USD.
- `minutes` (integer): Look-back window in minutes (default 60).
- `side` (string): Side of the taker.
- `venue` (string): Only this venue.

### `get_movements` (~153 tokens)

Whale movements

Large on-chain transfers and whale moves, newest first: exchange in/outflows, transfers between wallets, stablecoin mints and burns, bridges, DEX swaps and large Hyperliquid positions and trades, with labels where a source names the wallet.

Input parameters:

- `asset` (string): Asset symbol, e.g. BTC, ETH, USDT.
- `chain` (string): Only this chain.
- `labelled` (boolean): Only movements with a labelled sender or receiver.
- `limit` (integer): Number of movements (default 15, at most 50).
- `min_usd` (integer): Only movements of at least this many USD.
- `types` (array): Only these movement types (default all).

### `get_traders` (~100 tokens)

Trader leaderboard

Hyperliquid trader leaderboard: PnL and ROI per window, account value, observed win rate, drawdown, Sharpe and style tags. Use it to find consistently profitable wallets; follow up with get_wallet.

Input parameters:

- `limit` (integer): Number of traders (default 10, at most 50).
- `sort` (string): Sort (default pnl_month).
- `style` (string): Only traders with this style tag (paid plans).

### `get_smart_money` (~100 tokens)

Smart money

What the most profitable tracked wallets do: convergence events (several top wallets opening the same side of a coin within a short window) and their current net positioning per coin.

Input parameters:

- `coin` (string): Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive).
- `limit` (integer): Number of events and coins (default 10, at most 50).

### `get_security_incidents` (~110 tokens)

Security incidents

Hacks, exploits, depegs and other security incidents, newest first: detector events and curated incidents with the reported loss and primary-source links.

Input parameters:

- `chain` (string): Only this chain.
- `limit` (integer): Number of incidents (default 10, at most 50).
- `min_severity` (integer): 1 info, 2 notable, 3 major, 4 critical (default 1).
- `origin` (string): all (default), detector or curated.

### `get_listed_wallets` (~194 tokens)

Listed wallets

Wallets an official source lists (OFAC SDN list, FBI / IC3 announcements, official incident post-mortems), each as "Listed as <category> by <source>, <date>" with a link. With an address: its listings, balances and tracked on-chain movements (404 when it is not listed). The other side of a movement is never labelled by us.

Input parameters:

- `address` (string): One address (EVM, Bitcoin, Tron …): its listings and movements.
- `category` (string): Only this category (sanctioned, stolen_funds, exploit …).
- `limit` (integer): Number of wallets or movements (default 10, at most 50).
- `network` (string): Only this address family (evm, bitcoin, tron …).
- `source` (string): Only this source: ofac_sdn, fbi_ic3 or incident.

### `get_exchange_flows` (~110 tokens)

Exchange flows

On-chain flows into and out of exchange wallets over a window: inflow, outflow and net per exchange and asset (stablecoins, BTC, ETH). Net outflows often mean coins moving to self-custody, inflows coins ready to sell.

Input parameters:

- `asset` (string): Only this asset family, e.g. USDT, BTC.
- `exchange` (string): Only this exchange, e.g. Binance.
- `hours` (integer): Window in hours (default 24).

### `get_my_limits` (~71 tokens)

Plan, limits and usage

The plan behind this server's key (or keyless public access): requests per minute and per day and how many are left, the history window, heatmap intervals and whether commercial use is allowed. Use it before a large research task or when a tool reports a rate limit. Not counted against the limits.

### `get_api_status` (~51 tokens)

API status

Whether the Blockmetric API and its data feeds are healthy right now: overall status, API version, feeds that are delayed or down, and open incidents. Use it when data looks stale or a tool fails.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-blockmetric-mcp/api#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 74

## Common questions

### What is the Blockmetric MCP server?

Blockmetric is an MCP server listed in the public MCP registry as io.blockmetric/mcp. Read-only crypto market data: Hyperliquid liquidation heatmaps, liquidations, whales, funding, flow. This page covers its hosted endpoint (https://api.blockmetric.io/mcp).

### Is the Blockmetric MCP server safe to use?

Blockmetric scores 75 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 Blockmetric MCP server expose?

Blockmetric exposes 21 tools: get_liquidation_heatmap, get_liquidation_map, get_liquidations, get_whales, get_wallet, and 16 more. Their descriptions and schemas cost roughly 2,910 tokens of context every time the server is loaded.

### Does the Blockmetric MCP server require authentication?

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

### Is the Blockmetric MCP server still maintained?

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

### What did VerifyMCP test on the Blockmetric MCP server?

VerifyMCP ran 13 checks on Blockmetric, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.blockmetric.io/mcp
- Website: https://blockmetric.io/docs/api/agents
- Changelog RSS feed: https://verifymcp.io/servers/io-blockmetric-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-blockmetric-mcp/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-blockmetric-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/io-blockmetric-mcp/api
