Blockmetric
REMOTE · API.BLOCKMETRIC.IO · 2 COMPONENTS
Read-only crypto market data: Hyperliquid liquidation heatmaps, liquidations, whales, funding, flow.
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- “get_liquidation_heatmap” reworded the description of “tf” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 20 Nov 26 +1
- 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 security
- Server version: 0.6.0 → 0.6.1 functional
- 19 Nov 26 0
- Server version: 0.5.0 → 0.6.0 functional
- “get_order_flow” reworded the description of “hours” cosmetic
- 18 Nov 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- “get_candles” added an optional parameter “price” cosmetic
- “get_candles” added an optional parameter “market” cosmetic
- “get_candles” reworded the description of “coin” cosmetic
- 17 Nov 26 74
First indexed and scored.
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 21 Nov 2026 · Probed https://api.blockmetric.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blockmetric.io | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d169eb29eb674854175348139f102e0667 |
| SANs: *.blockmetric.io, blockmetric.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.blockmetric.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| blockmetric.io. | DS published | 2371 | 13 | Verified |
| api.blockmetric.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com https://customer-portal.paddle.com https://sandbox-customer-portal.paddle.com https://accounts.google.com; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.blockmetric.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.blockmetric.io/mcp | HTTPS enforced | 301 | https://api.blockmetric.io/mcp |
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_api_status API status ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_candles Price candles ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | 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). |
No output schema declared.
No examples provided.
get_events Risk radar events ~162
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_exchange_flows Exchange flows ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_funding Funding rates ~97
Funding rates per coin across Hyperliquid and the exchanges the data licence allows (annualised, as fractions) and the spread between venues.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_large_trades Large-trade tape ~148
The newest large taker prints (trades above the tape threshold) with side, price, size and whether a tracked whale was the taker.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_liquidation_heatmap Liquidation heatmap ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | 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). |
No output schema declared.
No examples provided.
get_liquidation_map Liquidation map (now) ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| top | integer | – | Largest buckets per side (default 5). |
No output schema declared.
No examples provided.
get_liquidations Liquidations ~210
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_listed_wallets Listed wallets ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_long_short Long/short positioning ~94
Long/short positioning per coin: Hyperliquid from tracked positions (USD ratio) and, where the data licence allows, the account ratios the exchanges publish.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_movements Whale movements ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_my_limits Plan, limits and usage ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_order_flow Order flow (CVD) ~142
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | 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. |
No output schema declared.
No examples provided.
get_orderbook Order book and walls ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | 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). |
No output schema declared.
No examples provided.
get_screener Market screener ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_security_incidents Security incidents ~110
Hacks, exploits, depegs and other security incidents, newest first: detector events and curated incidents with the reported loss and primary-source links.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_smart_money Smart money ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_traders Trader leaderboard ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_wallet Wallet detail ~48
One tracked Hyperliquid wallet: account value, open positions with leverage and liquidation prices, totals and the latest position changes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x address (40 hex characters). |
No output schema declared.
No examples provided.
get_whales Whale leaderboard ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · api.blockmetric.io
claude mcp add --transport http io-blockmetric-mcp 'https://api.blockmetric.io/mcp'
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.