Model Context Protocol (MCP) server for freee API integration
Blockmetric is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read-only crypto market data: Hyperliquid liquidation heatmaps, liquidations, whales, funding, flow.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user blockmetric-mcp '--' npx -y blockmetric-mcp
# 2 — ask your agent for something these tools do
# get_liquidation_heatmap, get_liquidation_map, get_liquidations and 18 more
Blockmetric costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user blockmetric-mcp '--' npx -y blockmetric-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://api.blockmetric.io/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http blockmetric-mcp https://api.blockmetric.io/mcpNothing is required, but it can take BLOCKMETRIC_API_KEY (Optional Blockmetric API key (bm_live_...) for your plan's history and limits. Without it the server uses keyless public access: 24 h of history, 10 requests per minute and 300 per day per IP address.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 happ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| hours | integer | no | Look-back window in hours (default 24; capped by the plan history). |
| tf | string | no | Column interval (default: chosen from hours: 15m up to 7 days, 1h up to 30 days, then 4h / 12h). Intervals outside the plan answer plan_required. |
| end | string | no | End of the window (default now). Set it to look at the heatmap of an earlier time. |
| top | integer | no | Clusters per side (default 5). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| top | integer | no | Largest buckets per side (default 5). |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | Window in hours (default 24; capped by the plan). |
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| venue | string | no | Only this venue for the latest liquidations list. |
| side | string | no | Only liquidated longs or shorts in the latest list. |
| min_usd | integer | no | Only liquidations of at least this many USD in the latest list. |
| limit | integer | no | Number of latest liquidations (default 5, at most 50). |
Largest tracked Hyperliquid wallets with public 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | size = open notional (default), pnl = all-time PnL, near_liq = closest to liquidation, liquidated = most liquidations. |
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| labelled | boolean | no | Only wallets with a public label from a cited source. |
| limit | integer | no | Number of wallets (default 10, at most 50). |
One tracked Hyperliquid wallet: account value, open positions with leverage and liquidation prices, totals and the latest position changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | 0x address (40 hex characters). |
Funding rates per coin across Hyperliquid and the exchanges the data licence allows (annualised, as fractions) and the spread between venues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| limit | integer | no | Number of coins, by Hyperliquid open interest (default 10, at most 50). |
Long/short positioning per coin: Hyperliquid from tracked positions (USD ratio) and, where the data licence allows, the account ratios the exchanges publish.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| limit | integer | no | Number of coins (default 10, at most 50). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kinds | array | no | Only these event kinds (default all). |
| min_severity | integer | no | 1 info, 2 notable, 3 major, 4 critical (default 1). |
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| limit | integer | no | Number of events (default 10, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| tf | string | no | Candle interval (default 1h). |
| limit | integer | no | Number of candles (default 24, at most 200). |
| from | string | no | Start (default: limit candles before to). |
| to | string | no | End, exclusive (default now). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | Sort column (default oi = open interest). |
| dir | string | no | desc (default) or asc. |
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| min_oi_usd | integer | no | Only coins with at least this open interest (USD). |
| limit | integer | no | Number of coins (default 15, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| venue | string | no | Only this venue (default every venue the licence allows). |
| walls | integer | no | Walls to list (default 8). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| hours | integer | no | Window in hours (default 24; free keys 1). |
| venue | string | no | Only this venue. |
The newest large taker prints (trades above the tape threshold) with side, price, size and whether a tracked whale was the taker.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| venue | string | no | Only this venue. |
| side | string | no | Side of the taker. |
| min_usd | integer | no | Only prints of at least this many USD. |
| minutes | integer | no | Look-back window in minutes (default 60). |
| limit | integer | no | Number of prints (default 20, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| types | array | no | Only these movement types (default all). |
| chain | string | no | Only this chain. |
| asset | string | no | Asset symbol, e.g. BTC, ETH, USDT. |
| min_usd | integer | no | Only movements of at least this many USD. |
| labelled | boolean | no | Only movements with a labelled sender or receiver. |
| limit | integer | no | Number of movements (default 15, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | Sort (default pnl_month). |
| style | string | no | Only traders with this style tag (paid plans). |
| limit | integer | no | Number of traders (default 10, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin name as on Hyperliquid, e.g. BTC, ETH, kPEPE, xyz:TSLA (case-insensitive). |
| limit | integer | no | Number of events and coins (default 10, at most 50). |
Hacks, exploits, depegs and other security incidents, newest first: detector events and curated incidents with the reported loss and primary-source links.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | all (default), detector or curated. |
| chain | string | no | Only this chain. |
| min_severity | integer | no | 1 info, 2 notable, 3 major, 4 critical (default 1). |
| limit | integer | no | Number of incidents (default 10, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | One address (EVM, Bitcoin, Tron …): its listings and movements. |
| category | string | no | Only this category (sanctioned, stolen_funds, exploit …). |
| source | string | no | Only this source: ofac_sdn, fbi_ic3 or incident. |
| network | string | no | Only this address family (evm, bitcoin, tron …). |
| limit | integer | no | Number of wallets or movements (default 10, at most 50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | Window in hours (default 24). |
| exchange | string | no | Only this exchange, e.g. Binance. |
| asset | string | no | Only this asset family, e.g. USDT, BTC. |
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.
No parameter schema on file.
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.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Blockmetric or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_liquidation_heatmap | no tags | |
| get_liquidation_map | no tags | |
| get_liquidations | no tags | |
| get_whales | no tags | |
| get_wallet | no tags | |
| get_funding | no tags | |
| get_long_short | no tags | |
| get_events | no tags | |
| get_candles | no tags | |
| get_screener | no tags | |
| get_orderbook | no tags | |
| get_order_flow | no tags | |
| get_large_trades | no tags | |
| get_movements | no tags | |
| get_traders | no tags | |
| get_smart_money | no tags | |
| get_security_incidents | no tags | |
| get_listed_wallets | no tags | |
| get_exchange_flows | no tags | |
| get_my_limits | no tags | |
| get_api_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.6.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Blockmetric can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.