Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LiquidVision — Crypto Derivatives Data

REMOTE · LIQUIDVISION.APP

Crypto derivatives data and answers for AI agents: smart money, liquidations, funding, 13 venues

Available components

0 this week 80 Trust /100

Last scanned (23 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (7 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security66
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14595 tokens (~211/item across 69 items; 69 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 70 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
What we tested

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 →

Changelog

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.

  • 15 Nov 26 0
    • Tool “buy_day_pass” rewrote its description, which is the text the model reads security
    • “attest_snapshot” reworded the description of “params” cosmetic
    • “scan_rule” reworded the description of “rules” cosmetic
    • “test_rule” reworded the description of “rules” cosmetic
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “buy_day_pass” rewrote its description, which is the text the model reads security
    • Tool “get_hl_liquidation_map” rewrote its description, which is the text the model reads security
    • Tool “get_lighter_liquidation_map” rewrote its description, which is the text the model reads security
    • Tool “get_liquidation_heatmap” rewrote its description, which is the text the model reads security
    • Tool “get_liquidation_map” rewrote its description, which is the text the model reads security
    • Schema quality: 12896 → 14601 ▼ functional
    • New tool “create_watch” functional
    • New tool “get_watch” functional
    • New tool “get_x_mentions” functional
    • New tool “get_x_trends” functional
    • New tool “get_x_tweet” functional
    • New tool “get_x_user” functional
    • New tool “get_x_user_tweets” functional
    • New tool “pretrade_check” functional
  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ask” rewrote its description, which is the text the model reads security
    • Tool “explain_market” rewrote its description, which is the text the model reads security
    • Tool “get_crypto_twitter” rewrote its description, which is the text the model reads security
    • New tool “search_twitter” functional
    • Tool “ask” changed its title: Ask a derivatives question cosmetic
    • Tool “attest_snapshot” changed its title: Signed data snapshot cosmetic
    • Tool “buy_credits” changed its title: Buy prepaid credits cosmetic
    • Tool “buy_day_pass” changed its title: Buy a 24-hour key cosmetic
    • Tool “check_position” changed its title: Liquidation price of a position cosmetic
    • Tool “create_alert” changed its title: Create alert cosmetic
    • Tool “credits_balance” changed its title: Prepaid credit balance cosmetic
    • Tool “delete_alert” changed its title: Delete alert cosmetic
    • Tool “explain_market” changed its title: Market brief for a question cosmetic
    • Tool “get_accuracy” changed its title: Our numbers vs the exchanges cosmetic
    • Tool “get_api_key” changed its title: Get a free API key cosmetic
    • Tool “get_arbitrum_perps” changed its title: Arbitrum perps board cosmetic
    • Tool “get_cash_flows” changed its title: Cash flows cosmetic
    • Tool “get_crypto_twitter” changed its title: Crypto Twitter pulse cosmetic
    • Tool “get_cvd” changed its title: Cumulative volume delta cosmetic
    • Tool “get_defi_liquidations” changed its title: DeFi liquidation map (Morpho) cosmetic
    • Tool “get_detective_events” changed its title: Detective events cosmetic
    • Tool “get_fear_greed” changed its title: Derivatives fear & greed cosmetic
    • Tool “get_footprint” changed its title: Footprint cosmetic
    • Tool “get_funding_arbitrage” changed its title: Funding arbitrage cosmetic
    • Tool “get_funding_dispersion” changed its title: Funding dispersion cosmetic
    • Tool “get_funding_history” changed its title: Funding history cosmetic
    • Tool “get_funding_rates” changed its title: Funding rates cosmetic
    • Tool “get_funding_settlements” changed its title: Funding settlements cosmetic
    • Tool “get_hip3_markets” changed its title: Hyperliquid HIP-3 board cosmetic
    • Tool “get_history” changed its title: History cosmetic
    • Tool “get_hl_account” changed its title: Hyperliquid wallet lookup cosmetic
    • Tool “get_hl_builder_markets” changed its title: Hyperliquid builder markets cosmetic
    • Tool “get_hl_liquidation_map” changed its title: Hyperliquid liquidation map (measured) cosmetic
    • Tool “get_hl_top_traders” changed its title: Top Hyperliquid traders cosmetic
    • Tool “get_hl_whales” changed its title: Hyperliquid whale positions cosmetic
    • Tool “get_lighter_liquidation_map” changed its title: Lighter liquidation map (measured) cosmetic
    • Tool “get_lighter_whales” changed its title: Lighter whales cosmetic
    • Tool “get_liquidation_cascades” changed its title: Liquidation cascades cosmetic
    • Tool “get_liquidation_heatmap” changed its title: Liquidation heatmap cosmetic
    • Tool “get_liquidation_map” changed its title: Liquidation map (modeled) cosmetic
    • Tool “get_liquidations” changed its title: Liquidations cosmetic
    • Tool “get_liquidations_summary” changed its title: Liquidations summary cosmetic
    • Tool “get_long_short_ratio” changed its title: Long short ratio cosmetic
    • Tool “get_market_brief” changed its title: Market brief for a coin cosmetic
    • Tool “get_microstructure” changed its title: Microstructure cosmetic
    • Tool “get_oi_board” changed its title: Open interest board cosmetic
    • Tool “get_open_interest” changed its title: Open interest cosmetic
    • Tool “get_open_interest_history” changed its title: Open interest history cosmetic
    • Tool “get_orderbook_heatmap” changed its title: Orderbook heatmap cosmetic
    • Tool “get_positioning_regime” changed its title: Positioning regime cosmetic
    • Tool “get_precedents” changed its title: Past hours that resembled now cosmetic
    • Tool “get_prediction_markets” changed its title: Polymarket crypto odds cosmetic
    • Tool “get_smart_money” changed its title: Smart money on Hyperliquid cosmetic
    • Tool “get_spoofing” changed its title: Spoofing cosmetic
    • Tool “get_stocks” changed its title: Stocks cosmetic
    • Tool “get_token_unlocks” changed its title: Token unlocks cosmetic
    • Tool “get_tokenized_stocks” changed its title: Tokenized stocks cosmetic
    • Tool “get_top_traders” changed its title: Top traders cosmetic
    • Tool “get_trader_profile” changed its title: Hyperliquid trader profile cosmetic
    • Tool “list_alerts” changed its title: List alerts cosmetic
    • Tool “list_history_packages” changed its title: List history packages cosmetic
    • Tool “list_markets” changed its title: List markets and venues cosmetic
    • Tool “scan_rule” changed its title: Scan a rule across coins cosmetic
    • Tool “test_rule” changed its title: Test a trading rule on the archive cosmetic
  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_api_key” rewrote its description, which is the text the model reads security
    • Tool “get_hl_liquidation_map” rewrote its description, which is the text the model reads security
    • Tool “get_hl_whales” rewrote its description, which is the text the model reads security
    • Tool “get_liquidation_map” rewrote its description, which is the text the model reads security
    • Tool “get_precedents” rewrote its description, which is the text the model reads security
    • Tool “get_smart_money” rewrote its description, which is the text the model reads security
    • Tool “get_tokenized_stocks” rewrote its description, which is the text the model reads security
    • Tool “get_top_traders” rewrote its description, which is the text the model reads security
    • Tool “test_rule” rewrote its description, which is the text the model reads security
    • Schema quality: 10808 → 12600 ▼ functional
    • New tool “buy_day_pass” functional
    • New tool “get_defi_liquidations” functional
    • New tool “get_fear_greed” functional
    • New tool “get_hl_top_traders” functional
    • New tool “get_prediction_markets” functional
    • New tool “get_trader_profile” functional
    • New tool “get_crypto_twitter” functional
    • New tool “get_smart_money” functional
    • “create_alert” reworded the description of “metric” cosmetic
  • 11 Nov 26 0
    • Tool “create_alert” rewrote its description, which is the text the model reads security
    • Tool “get_funding_arbitrage” rewrote its description, which is the text the model reads security
    • New tool “scan_rule” functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
    • Tool “create_alert” rewrote its description, which is the text the model reads security
    • Schema quality: 8890 → 10355 ▼ functional
    • New tool “attest_snapshot” functional
    • New tool “buy_credits” functional
    • New tool “check_position” functional
    • New tool “credits_balance” functional
    • New tool “test_rule” functional
    • “create_alert” added an optional parameter “entry” cosmetic
    • “create_alert” added an optional parameter “leverage” cosmetic
    • “create_alert” added an optional parameter “notional_usd” cosmetic
    • “create_alert” added an optional parameter “side” cosmetic
    • “create_alert” added an optional parameter “venue” cosmetic
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 +3

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Authorization: unverified → fail ▼ critical
    • Tool “get_api_key” rewrote its description, which is the text the model reads security
    • Tool “delete_alert” is now declared destructive security
    • Schema quality: 151 → 193 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • “ask” reworded the description of “coin” cosmetic
    • “ask” reworded the description of “question” cosmetic
    • “create_alert” reworded the description of “api_key” cosmetic
    • “create_alert” reworded the description of “max_dist_pct” cosmetic
    • “create_alert” reworded the description of “metric” cosmetic
    • “create_alert” reworded the description of “min_usd” cosmetic
    • “create_alert” reworded the description of “op” cosmetic
    • “create_alert” reworded the description of “symbol” cosmetic
    • “create_alert” reworded the description of “threshold” cosmetic
    • “create_alert” reworded the description of “type” cosmetic
    • “create_alert” reworded the description of “url” cosmetic
    • “create_alert” reworded the description of “x_normal” cosmetic
    • “delete_alert” reworded the description of “api_key” cosmetic
    • “delete_alert” reworded the description of “id” cosmetic
    • “explain_market” reworded the description of “question” cosmetic
    • “explain_market” reworded the description of “symbol” cosmetic
    • “get_api_key” reworded the description of “email” cosmetic
    • “get_cvd” reworded the description of “minutes” cosmetic
    • “get_cvd” reworded the description of “symbol” cosmetic
    • “get_detective_events” reworded the description of “chain” cosmetic
    • “get_detective_events” reworded the description of “hours” cosmetic
    • “get_detective_events” reworded the description of “limit” cosmetic
    • “get_detective_events” reworded the description of “symbol” cosmetic
    • “get_detective_events” reworded the description of “type” cosmetic
    • “get_footprint” reworded the description of “minutes” cosmetic
    • “get_footprint” reworded the description of “step” cosmetic
    • “get_footprint” reworded the description of “symbol” cosmetic
    • “get_funding_arbitrage” reworded the description of “limit” cosmetic
    • “get_funding_arbitrage” reworded the description of “min_venues” cosmetic
    • “get_funding_dispersion” reworded the description of “limit” cosmetic
    • “get_funding_dispersion” reworded the description of “min_venues” cosmetic
    • “get_funding_dispersion” reworded the description of “window” cosmetic
    • “get_funding_history” reworded the description of “minutes” cosmetic
    • “get_funding_history” reworded the description of “symbol” cosmetic
    • “get_funding_settlements” reworded the description of “days” cosmetic
    • “get_funding_settlements” reworded the description of “exchange” cosmetic
    • “get_funding_settlements” reworded the description of “symbol” cosmetic
    • “get_hip3_markets” reworded the description of “dex” cosmetic
    • “get_hip3_markets” reworded the description of “limit” cosmetic
    • “get_hip3_markets” reworded the description of “sort” cosmetic
    • “get_history” reworded the description of “api_key” cosmetic
    • “get_history” reworded the description of “dataset” cosmetic
    • “get_history” reworded the description of “end” cosmetic
    • “get_history” reworded the description of “exchange” cosmetic
    • “get_history” reworded the description of “limit” cosmetic
    • “get_history” reworded the description of “start” cosmetic
    • “get_history” reworded the description of “symbol” cosmetic
    • “get_hl_account” reworded the description of “address” cosmetic
    • “get_hl_account” reworded the description of “api_key” cosmetic
    • “get_hl_liquidation_map” reworded the description of “range” cosmetic
    • “get_hl_liquidation_map” reworded the description of “symbol” cosmetic
    • “get_hl_whales” reworded the description of “coin” cosmetic
    • “get_hl_whales” reworded the description of “limit” cosmetic
    • “get_hl_whales” reworded the description of “max_dist_pct” cosmetic
    • “get_hl_whales” reworded the description of “min_usd” cosmetic
    • “get_hl_whales” reworded the description of “side” cosmetic
    • “get_hl_whales” reworded the description of “sort” cosmetic
    • “get_lighter_liquidation_map” reworded the description of “range” cosmetic
    • “get_lighter_liquidation_map” reworded the description of “symbol” cosmetic
    • “get_lighter_whales” reworded the description of “coin” cosmetic
    • “get_lighter_whales” reworded the description of “limit” cosmetic
    • “get_lighter_whales” reworded the description of “max_dist_pct” cosmetic
    • “get_lighter_whales” reworded the description of “min_usd” cosmetic
    • “get_lighter_whales” reworded the description of “side” cosmetic
    • “get_lighter_whales” reworded the description of “sort” cosmetic
    • “get_liquidation_cascades” reworded the description of “hours” cosmetic
    • “get_liquidation_cascades” reworded the description of “limit” cosmetic
    • “get_liquidation_heatmap” reworded the description of “exchange” cosmetic
    • “get_liquidation_heatmap” reworded the description of “range” cosmetic
    • “get_liquidation_heatmap” reworded the description of “symbol” cosmetic
    • “get_liquidation_map” reworded the description of “exchange” cosmetic
    • “get_liquidation_map” reworded the description of “range” cosmetic
Diagnostics

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://liquidvision.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=liquidvision.app CN=YE1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 57c61cef4d5908d5ee9e72a8008f84ebdee
SANs: *.liquidvision.app, liquidvision.app
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 liquidvision.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
liquidvision.app. DS published 2371 13 Verified
liquidvision.app. 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://liquidvision.app/mcp Verified 200
http (plaintext) http://liquidvision.app/mcp HTTPS enforced 301 https://liquidvision.app/mcp
MCP tools · 69 exposed · ~13,895 tokens

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 →

Tool Tokens
ask ~216

ONE CALL instead of five: ask in plain words ('where is leverage stacked on BTC', 'why did ETH drop', 'is SOL funding crowded', 'biggest whales near liquidation') and get `answer`: short statements with the numbers in them, `facts`: the same numbers as JSON, `sources`: which endpoints were read and how old their data is, `caveats`. The question is read for its topics (liquidations, funding, open interest, whales, levels, sentiment; English or Russian) and only those endpoints are fetched. No model involved: facts, not opinion, so you do the judging. Free, no key. For the base rate of the current state call get_precedents; for the full brief of a coin call get_market_brief.

NameTypeReqDescription
coinstring–Base asset, e.g. BTC, ETH, SOL (no USDT suffix).
questionstringyesThe question in plain words, English or Russian.

No output schema declared.

No examples provided.

attest_snapshot ~250

[receipt] A SIGNED snapshot: the wrapped endpoint's JSON plus an attestation (SHA-256 of the canonical JSON, server time, Ed25519 signature, key id). Anyone can verify it offline with the public key at /api/v1/attest/key, so an agent acting for someone else can prove what the exchanges reported when it decided. Free snapshots and conclusions only (no metered history). It certifies what LiquidVision served, not that the exchange was right. Priced: $0.05 per call (x402), 10 prepaid credits, or a key's daily quota; the public key at /attest/key is free.

NameTypeReqDescription
params––Query string for the wrapped path, e.g. 'q=why+did+BTC+drop&coin=BTC' or 'symbol=BTC&side=long&leverage=20'.
pathstringyesAPI path under /api/v1 to wrap, e.g. /funding, /oi, /liquidations, /oiboard/BTCUSDT, /liqmap/BTCUSDT, /answer, /position/check.

No output schema declared.

No examples provided.

buy_credits ~234

[payment] How an agent with a wallet buys a prepaid API key by itself, with ONE x402 USDC payment and no human, email or account. Returns the exact payment requirements (price, asset, payTo, network, the resource URL) for GET https://liquidvision.app/api/v1/credits/buy?usd=N. Send that GET with a PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header from your wallet and the answer is a key of tier 'prepaid' with the credits ($0.005 each; a row costs 1, a 12-venue position check 4, precedents or an attestation 10, a rule test 20); the same wallet always tops up the same key. Credits are spent per call by price class; every conclusion and live snapshot stays free. This tool itself moves no money.

NameTypeReqDescription
usdinteger–Pack size in USD: 1 (200 credits), 5 (1,000) or 20 (4,000).

No output schema declared.

No examples provided.

buy_day_pass ~156

[payment] A 24-hour API key for ONE x402 USDC payment of $1.00 (Base or Arbitrum), no email or account: liquidation maps and heatmaps at full resolution, plus 400 units a day of metered calls (a row 1, a rule test 20, a rule scan 200). Returns the exact payment requirements for GET https://liquidvision.app/api/v1/pass/day; send that GET with a PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header and the answer carries api_key and its expiry. The same wallet extends the same key. This tool itself moves no money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_position ~360

[measured + modeled] Your own position against the market in one call: the liquidation price on each venue from THAT venue's maintenance-margin tier at this notional (read from the exchanges' public tables, 'estimated' where none is published), the distance from the current mark, how much modeled CEX leverage and how much MEASURED Hyperliquid leverage sits between the mark and your liquidation price on your side, the funding cost per day at the venue's live rate, and how often in our hourly archive price moved at least that far against your side within 24 h and 72 h (a frequency, not a forecast). Assumes isolated margin and ignores fees, so the real level is slightly nearer the entry. ONE venue (venue= given) is free; the 12-venue comparison is an answer we price: $0.02 per call (x402), 4 prepaid credits, or a key's daily quota.

NameTypeReqDescription
coinstring–Base asset, e.g. BTC, ETH, SOL (no USDT suffix).
entrynumberyesEntry price in quote currency (USDT).
leveragenumberyesLeverage, e.g. 10 for 10x (isolated margin assumed).
notional_usdnumber–Position size in USD (price x quantity).
sidestringyesPosition side: long | short.
venue––Venue id (binance, bybit, okx, bitget, gate, kucoin, kraken, hyperliquid, htx, mexc, bingx, aster). Omit for every venue side by side.

No output schema declared.

No examples provided.

create_alert ~817

Subscribe an HTTPS URL to push alerts instead of polling (Pro: 3, Bot: 20 subscriptions). type='condition': YOUR OWN trigger on one symbol — fires when `metric` `op` `threshold` becomes true (edge-triggered: once per crossing, again only after it was false). metric = funding_apr_pct (median annualised funding across venues) | oi_chg_1h_pct | oi_chg_24h_pct (Binance+Bybit+OKX, in coins) | liq_1h_usd | liq_24h_usd | price_chg_1h_pct | price_chg_24h_pct (Binance mark) | long_pct (mean long share of accounts) — the SAME definitions test_rule backtests, so test a rule first and alert on it after; op = gt | lt. Example: symbol='BTC', metric='funding_apr_pct', op='gt', threshold=50. The payload carries the value, the threshold and every other metric as context. Checked every 60 s. type='position': YOUR OWN position (symbol, side, entry, leverage, notional_usd, venue) — fires when it is within max_dist_pct of its liquidation price, computed every 60 s from the venue's maintenance-margin tier and the live mark (same numbers as check_position); again only when it gets a whole percent closer. type='cascade': a liquidation cascade just ended, over min_usd and x_normal times the coin's normal minute. type='hl_near_liq': a Hyperliquid whale position over min_usd within max_dist_pct of its liquidation price. type='cluster_sweep': price reached one of the 10 largest modeled liquidation-map clusters (size over min_usd; no symbol = BTC, ETH, SOL), sent 3 min later with modeled vs actually liquidated USD. Returns the signing secret ONCE: verify header X-LiquidVision-Signature = hex HMAC-SHA256(secret, raw body). Needs a Pro or Bot key.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
entry––type=position: entry price (USDT).
leverage––type=position: leverage, e.g. 20.
max_dist_pctnumber–Only positions whose liquidation price is within this many percent of the mark price.
metric––Condition metric: funding_apr_pct | oi_chg_1h_pct | oi_chg_24h_pct | liq_1h_usd | liq_24h_usd | price_chg_1h_pct | price_chg_24h_pct | long_pct.
min_usdnumber–Only rows at or above this notional in USD.
notional_usd––type=position: position size in USD (default 10,000).
op––Comparison: gt (greater than) | lt (less than).
side––type=position: long | short.
symbol––Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
threshold––Threshold the metric is compared with, in the metric's own unit (percent or USD).
typestringyesType id, one of the values listed in the description.
urlstringyesHTTPS endpoint that will receive the POST deliveries.
venue––type=position: venue whose margin tiers and mark to use (default binance).
x_normalnumber–Minimum cascade size as a multiple of the coin's normal minute of liquidations.

No output schema declared.

No examples provided.

create_watch ~383

[alert] Buy a 30-day watch with ONE payment and no account, checked every 60 seconds: your own position within max_dist_pct of its liquidation price (type=position), a metric of a coin crossing a threshold (condition), a liquidation cascade ending (cascade), or a Hyperliquid whale near liquidation (hl_near_liq). Returns watch_id; read its events with get_watch (free). Priced: $0.20 (x402, MPP), 40 prepaid credits, or a key's daily units.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
entry––position: entry price.
leverage––position: leverage.
max_dist_pctnumber–position / hl_near_liq: alert within this % of liquidation.
metric––condition: funding_apr_pct | oi_chg_1h_pct | oi_chg_24h_pct | liq_1h_usd | liq_24h_usd | price_chg_1h_pct | price_chg_24h_pct | long_pct
min_usdnumber–cascade / hl_near_liq: minimum size in USD.
notional_usd––position: size in USD (optional).
op––condition: gt or lt.
side––position: long or short.
symbol––Coin or contract, e.g. BTC. Required except for cascade.
threshold––condition: the threshold.
typestringyesposition | condition | cascade | hl_near_liq
url––Optional HTTPS URL that also receives each event.
venue––position: one venue id (optional).

No output schema declared.

No examples provided.

credits_balance ~81

[account] Remaining prepaid credits on a key bought with buy_credits. Free/Pro/Bot keys are metered by daily quota instead (X-Raw-Quota-* headers) and return a note saying so.

NameTypeReqDescription
api_key––The prepaid key (lv_...). Omit when it is sent as X-API-Key on the connection.

No output schema declared.

No examples provided.

delete_alert ~167

Permanently delete one webhook alert subscription. DESTRUCTIVE and not reversible: deliveries to its URL stop at once and its signing secret is discarded (create_alert issues a new one). Only a subscription owned by the caller's API key can be deleted; an id belonging to another key returns {"deleted": false} and changes nothing. id: the number returned by create_alert or list_alerts. Needs a Pro or Bot key (X-API-Key header of the MCP connection, or api_key).

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
idintegeryesNumeric id of the subscription, from list_alerts or create_alert.

No output schema declared.

No examples provided.

explain_market ~173

The market brief behind a question such as 'Why did BTC drop 4%?': liquidations by window, funding extremes, open interest by venue, flows and risk zones for the coin, as one JSON for YOU to reason over. No language model runs on our side today, so `answer` is null and `brief` carries the facts (if a model is configured later, `answer` holds its short narrative). For a ready plain-words answer with no model, call ask.

NameTypeReqDescription
questionstringyesThe question in plain words, English or Russian.
symbolstring–Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_accuracy ~83

[measured] The public accuracy audit: our open interest and funding vs Binance, Bybit, OKX and Hyperliquid's own endpoints, sampled every 10 min (diff %, snapshot age, 24h mean/max), plus how the modeled liquidation map scored against realized liquidations. Read this before trusting any number here with money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_api_key ~193

Get a free LiquidVision API key for this agent's owner, by email, without a browser. Works for a NEW email only (an existing account's key is never returned; its owner sees it at liquidvision.app/data). Use the key as X-API-Key on REST or on this MCP endpoint: 120 req/min instead of the shared anonymous budget, plus 100 units a day of metered calls (history, positions: get_funding_history, get_open_interest_history, get_funding_settlements, get_hl_whales, get_history...), and to upgrade later to Pro/Bot (10,000 / 100,000 metered calls a day, exports, webhook alerts). Ask the user for the email first; do not invent one.

NameTypeReqDescription
emailstringyesThe owner's email address; the key is issued to it once.

No output schema declared.

No examples provided.

get_arbitrum_perps ~77

Arbitrum perps board: GMX v2 open interest per coin and its share of every tracked venue, GMX funding next to the CEX median (8h basis), on-chain liquidations over 24h. Ask this for 'how is Arbitrum positioned vs CEXs'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cash_flows ~48

Derivatives cash flow per exchange: net USD into/out of open interest over 1h/4h/24h windows, per core symbol. Positive = money flowing in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_crypto_twitter ~220

[measured + lexicon] Crypto Twitter pulse for one coin: the latest English posts on X with replies, retweets, spam and tiny accounts dropped; a bullish/bearish lean from -100 to +100 weighted by engagement and reach (a crypto word lexicon: rough, sarcasm fools it); posts per hour; the top posts with author and link; and next to them the coin's funding rate, open interest change and long/short positioning, with one sentence on whether talk and positioning agree. Cached 10 minutes. Always paid per call: $0.02 (x402, MPP or 4 prepaid credits); no key's daily allowance covers it, Pro and Bot included.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
coinstringyesBase asset, e.g. BTC, SOL, HYPE (no USDT suffix).

No output schema declared.

No examples provided.

get_cvd ~142

Cumulative volume delta split by trade size (retail <$10K, mid <$100K, large <$1M, whale >$1M). Whale-vs-retail divergence is the usual smart-money reading; buckets are per published row and only Binance aggregates taker orders, so compare buckets within one exchange (exchange=binance) rather than across venues.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.
symbolstring–Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_defi_liquidations ~178

[measured] DeFi lending liquidation map for Morpho Blue: borrowers nearest liquidation (health factor, the collateral price drop that liquidates them, debt), the debt that becomes liquidatable at a 1/2/5/10/15/20% drop per collateral asset, and pegged loops (stable/stable, ETH/LST) apart. Priced: $0.02 per call (x402), 4 credits, or a key's quota.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
chainstring–base, ethereum or arbitrum.
collateral––Only this collateral, e.g. cbBTC, WETH, wstETH.

No output schema declared.

No examples provided.

get_detective_events ~331

[measured] Detective: what the watched large holders did. Private wallets with a large share of a token's supply (Ethereum, Solana) and Hyperliquid accounts with a large share of a contract's open interest are watched live. Event types: to_exchange (a watched wallet sent tokens to a recognised exchange, custodian, market maker, DEX pool or bridge: a possible sale, reported at any size), large_move (at least $100k to an address we do not recognise), hl_position (a watched Hyperliquid position opened, closed or changed by a quarter and $1M+). Each event carries the sender's share of supply when it was added to the list, the destination label and its source, amount, best-effort USD and an explorer link. Filters: hours (1-720), chain (ethereum|solana|hyperliquid), type, symbol (coin). The watch list itself: GET https://liquidvision.app/api/v1/detective/watch.

NameTypeReqDescription
chain––Chain filter: ethereum | solana | hyperliquid. Omit for all.
hoursinteger–Look-back window in hours.
limitinteger–Maximum number of rows to return.
symbol––Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
type––Type id, one of the values listed in the description.

No output schema declared.

No examples provided.

get_fear_greed ~173

[measured] Crypto fear & greed from DERIVATIVES positioning, 0 extreme fear .. 100 extreme greed: funding rate, long/short accounts, open interest change and 7-day momentum (each the percentile of its current value in the coin's own hourly archive) and the share of 24h liquidations that hit shorts. Not news, not social media. Priced: $0.005 per call (x402), 1 credit, or a key's quota.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
coinstring–BTC, ETH, SOL ... or 'market' (the mean of BTC, ETH and SOL).

No output schema declared.

No examples provided.

get_footprint ~213

[measured] Footprint chart data: for each candle, taker BUY and taker SELL volume in USD and the trade count at each of 30 price levels, from the archived trade streams of Binance, Bybit, OKX, Bitget and Gate. Use it to see at which prices aggressive buyers or sellers were absorbed; for the net flow over time by trade size use get_cvd. symbol: BTCUSDT, ETHUSDT or SOLUSDT only. minutes: look-back window, 15 to 10080. step: candle size in minutes, 1 to 240.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.
stepinteger–Candle size in minutes, 1 to 240.
symbolstring–Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_funding_arbitrage ~245

[measured] Funding carry screener on REALIZED numbers, out of sample: for each coin, the venue pair a desk would have put on a week ago (short where funding WAS richest, long where it was cheapest, chosen on days 14-7 ago: selection_week_apr) and what that pair then earned from funding over the last 7 days (realized_7d_*, negative when the spread reversed) and 30 days, annualized; positive_share_7d = share of the week's hours the pair was net positive (0.5 is a coin flip); current_spread_apr = the same pair right now; mark_gap_bps = short-venue mark over long-venue mark (positive = entry in your favour). Use get_funding_dispersion for the live spread across all venues. Everything is gross: before taker fees, basis moves and two margin accounts. Not financial advice.

NameTypeReqDescription
limitinteger–Maximum number of rows to return.
min_venuesinteger–Only coins quoted on at least this many venues.

No output schema declared.

No examples provided.

get_funding_dispersion ~165

Coins ranked by how far funding disagrees ACROSS exchanges. For each coin: the spread in APR points between the venue charging the most and the one paying the most, plus which venue to hold the long on and which to hold the short on. Every leg is annualized with its own settlement cycle (1h / 4h / 8h), and the ranking uses the median rate over `window` minutes rather than the latest print, which is noisy for hourly contracts.

NameTypeReqDescription
limitinteger–Maximum number of rows to return.
min_venuesinteger–Only coins quoted on at least this many venues.
windowinteger–Aggregation window, as listed in the description.

No output schema declared.

No examples provided.

get_funding_history ~184

[measured] Funding rate over time for one contract, one row per venue per time bucket: ts (ms), exchange, funding_rate (per settlement interval, a fraction), mark_price and funding_hours (that contract's interval: 1, 4 or 8). Annualize as rate * 8760 / funding_hours. This is the LIVE predicted rate sampled over time; for the rates actually paid at each settlement (2 years back) use get_funding_settlements. symbol: BASEUSDT. minutes: 5 to 20160.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_funding_rates ~34

Latest perpetual funding rates and mark prices for every tracked exchange/symbol pair. Positive rate = longs pay shorts.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

get_funding_settlements ~184

Settled funding rates, one row per settlement, from Binance and Bybit history — up to 730 days for any pool coin (e.g. BTCUSDT). The backtest series; get_funding_history is the live 10-second archive since July 2026.

NameTypeReqDescription
daysinteger–Look-back window in days.
exchangestring–Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_hip3_markets ~320

[measured] The HIP-3 board: Hyperliquid's builder-deployed perp markets (equity indices, stocks, commodities, pre-IPO names; coins named dex:COIN such as xyz:SP500) with what the live list alone cannot tell you. Per dex: OI, share, 24h/7d OI change, 24h volume, liquidations. Per market: mark, 24h change, OI and its 24h/7d change, 24h volume and turnover (volume/OI), hourly funding and APR, liquidations 24h/7d (count, USD, long share), and gap_bps = HIP-3 mark vs the mean mark of other venues listing the same underlying (Lighter, Ostium, gTrade). `leaders` lists OI growth/decline, funding extremes, most liquidated, widest gap. dex filters to one builder (xyz, io, para...); sort = oi | volume | funding | liq | gap | oi_change; limit caps the markets list. OI changes are null until the archive is that old (started 2026-10-31). No key needed.

NameTypeReqDescription
dex––HIP-3 builder dex id. Omit for all builder markets.
limitinteger–Maximum number of rows to return.
sortstring–Sort order of the result, as listed in the description.

No output schema declared.

No examples provided.

get_history ~367

[measured] Historical rows as CSV, for backtests. dataset: liquidations | funding_settlements (since 2024-09) | funding_hourly | open_interest_hourly | hl_positions (Hyperliquid whale positions with liquidation prices). start/end are ISO dates (UTC). Without a key or on the free tier only the last 24 hours are available; Pro: any 31-day window; Bot: full history. The key is read from the MCP connection's X-API-Key header, or pass api_key. limit caps rows here (max 5000); for bulk use download_url with the same key.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
datasetstringyesDataset id: liquidations | funding_settlements | funding_hourly | open_interest_hourly | hl_positions | lighter_positions (see list_history_packages).
end––End of the window, ISO date (YYYY-MM-DD) or datetime, UTC.
exchange––Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.
limitinteger–Maximum number of rows to return.
start––Start of the window, ISO date (YYYY-MM-DD) or datetime, UTC.
symbol––Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_hl_account ~148

[measured] One Hyperliquid account by address: live positions (size, entry, mark, liquidation price, distance to liquidation, leverage, unrealized PnL), account value, and its archived position snapshots. History depth: 24 h free, 31 days Pro, everything since 2026-09-27 on Bot (key from the MCP connection's X-API-Key header, or api_key).

NameTypeReqDescription
addressstringyesHyperliquid account address (0x...).
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.

No output schema declared.

No examples provided.

get_hl_builder_markets ~138

[measured] Perp markets deployed on Hyperliquid by third parties (HIP-3 builder dexs): equity indices, single stocks, commodities and pre-IPO names such as xyz:SP500 or xyz:GOLD. For each dex: its markets (coin named dex:COIN), open interest in USD (one side), 24h volume, mark price, hourly funding and its APR. These are NOT in get_open_interest or get_funding_rates, which cover Hyperliquid's own crypto listing. Live from Hyperliquid, cached 2 minutes. No arguments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_hl_liquidation_map ~316

[measured, RISK AHEAD, Hyperliquid] REAL open positions on Hyperliquid binned by the liquidation price the exchange itself reports: the 10,000 largest accounts plus every account seen trading since the reader started (about 13,600 accounts, ~40-45% of venue open interest, stated in covered_long_pct/covered_short_pct). Not a model. Use this for Hyperliquid; use get_lighter_liquidation_map for Lighter and get_liquidation_map (modeled) for the CEXs. Returns long/short notional per bin, cumulative curves and the largest positions. range: 12h | 1d | 3d | 7d | max (±100%, recommended: large accounts run low leverage). PRICE: the full map is a metered call ($0.005, or a key). Without a key this tool returns the free summary: USD on each side of the price and the largest level on each side.

NameTypeReqDescription
rangestring–Price range around the current price: 12h | 1d | 3d | 7d (and 'max' where stated), the traded range of that window.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_hl_top_traders ~213

[measured] Top Hyperliquid traders worth following (copy trading): accounts in profit over the last week, month AND all time that traded this month, ranked by PnL (or sort=return), with PnL and volume per window and their open positions now. Then get_trader_profile on any address. Priced: $0.03 per call (x402), 6 credits, or a key's quota.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
limitinteger–How many traders, 1-100.
min_account_usdnumber–Minimum account value, USD.
sortstring–pnl (USD profit, default) or return (profit over account value).
windowstring–Rank by this window's PnL: day, week, month or allTime.

No output schema declared.

No examples provided.

get_hl_whales ~220

[measured] Leveraged positions of about 13,600 Hyperliquid accounts (the 10,000 largest plus every account seen trading) with the exchange-reported liquidation price, closest to liquidation first (sort='value' = largest first). Filters: coin (BTC), side (long|short), min_usd, max_dist_pct. Each row carries the account address; pass it to get_hl_account. Snapshot age is in age_s.

NameTypeReqDescription
coin––Base asset, e.g. BTC, ETH, SOL (no USDT suffix).
limitinteger–Maximum number of rows to return.
max_dist_pct––Only positions whose liquidation price is within this many percent of the mark price.
min_usdnumber–Only rows at or above this notional in USD.
side––Position side: long | short. Omit for both.
sortstring–Sort order of the result, as listed in the description.

No output schema declared.

No examples provided.

get_lighter_liquidation_map ~301

[measured, RISK AHEAD, Lighter] REAL open positions on Lighter (zk perp DEX; crypto plus equity indices, stocks, forex, commodities) binned by Lighter's own liquidation price. Not a model. Use this for Lighter; get_hl_liquidation_map for Hyperliquid; get_liquidation_map (modeled) for the CEXs. Accounts are discovered from the public trade stream, so coverage (covered_long_pct/covered_short_pct of venue open interest) grows with time. Returns long/short notional per bin, cumulative curves and the largest positions. range: 12h | 1d | 3d | 7d | max. PRICE: the full map is a metered call ($0.005, or a key). Without a key this tool returns the free summary: USD on each side of the price and the largest level on each side.

NameTypeReqDescription
rangestring–Price range around the current price: 12h | 1d | 3d | 7d (and 'max' where stated), the traded range of that window.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_lighter_whales ~196

[measured] Leveraged positions on Lighter with the exchange-reported liquidation price, closest to liquidation first (sort='value' = largest first). Filters: coin (BTC), side (long|short), min_usd, max_dist_pct. address is the Lighter account index, l1_address the wallet. Snapshot age is in age_s.

NameTypeReqDescription
coin––Base asset, e.g. BTC, ETH, SOL (no USDT suffix).
limitinteger–Maximum number of rows to return.
max_dist_pct––Only positions whose liquidation price is within this many percent of the mark price.
min_usdnumber–Only rows at or above this notional in USD.
side––Position side: long | short. Omit for both.
sortstring–Sort order of the result, as listed in the description.

No output schema declared.

No examples provided.

get_liquidation_cascades ~198

[measured, PAST] Liquidation CASCADES as discrete events: bursts of liquidations detected against each coin's own 7-day normal minute. Use it for "when did forced selling snowball and what did price do"; not for totals (get_liquidations_summary), raw orders (get_liquidations) or open positions at risk (*_liquidation_map). Each event: coin, which side broke, start, how long it ran, total and peak-minute USD, multiple of the coin's normal minute, the mark-price move during it and in the hour after. market_wide lists minutes when three or more unrelated coins cascaded together. hours: display window (baseline is always the last 7 days).

NameTypeReqDescription
hoursinteger–Look-back window in hours.
limitinteger–Maximum number of rows to return.

No output schema declared.

No examples provided.

get_liquidation_heatmap ~392

[modeled, RISK AHEAD, CEX, over time] The same estimated CEX map as get_liquidation_map but as a time series: grid[t][b] is the estimated USD of leveraged positions with their liquidation price in price bin b at time cols[t] (ms), bins[b] the bin's centre price (240 bins fitted to the traded range), price[t] the close. A level disappears once price trades through it. Call this only to see WHEN a cluster formed and whether it survived; for the current picture call get_liquidation_map (far smaller answer, split by leverage and exchange). The answer is large (about 35,000 numbers). symbol: BASEUSDT. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d. PRICE: the full map is a metered call ($0.005, or a key). Without a key this tool returns the free summary: USD on each side of the price and the largest level on each side.

NameTypeReqDescription
exchangestring–Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.
rangestring–Price range around the current price: 12h | 1d | 3d | 7d (and 'max' where stated), the traded range of that window.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_liquidation_map ~452

[modeled, RISK AHEAD, CEX, now] ESTIMATED open leveraged positions on Binance/Bybit/OKX per price bin at their liquidation price, from candles and open-interest deltas (the CEXs do not publish positions). Current snapshot only; for its evolution over time use get_liquidation_heatmap; for REAL positions use get_hl_liquidation_map (Hyperliquid) or get_lighter_liquidation_map (Lighter); for what already got liquidated use the PAST tools. Returns notional per bin split by leverage tier (5/10/20/25/50/100x) and by exchange, plus cumulative long/short curves from the current price outward. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d. It ranks levels ("if price reaches this level, how much is there": the top quarter of traded levels held 32% of liquidated USD against 25% by chance, 367 snapshots); it does NOT predict where price will go. Live scoring: get_accuracy. PRICE: the full map is a metered call ($0.005, or a key). Without a key this tool returns the free summary: USD on each side of the price and the largest level on each side.

NameTypeReqDescription
exchangestring–Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.
rangestring–Price range around the current price: 12h | 1d | 3d | 7d (and 'max' where stated), the traded range of that window.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_liquidations ~241

[measured, PAST] Individual liquidation ORDERS that already happened (side, price, qty), newest first, at most `limit` rows (max 2000). This is the raw feed: use it when you need the orders themselves. For totals use get_liquidations_summary; for cascades as events use get_liquidation_cascades; for where OPEN positions would be liquidated use a *_liquidation_map tool. Market-wide, 500 rows is only a few minutes of a busy hour: pass `symbol` (BTCUSDT) and/or `min_usd` to look further back. side=long means a long position was liquidated.

NameTypeReqDescription
limitinteger–Maximum number of rows to return.
min_usdnumber–Only rows at or above this notional in USD.
minutesinteger–Look-back window in minutes.
symbol––Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_liquidations_summary ~176

[measured, PAST] TOTALS of liquidations that already happened: rekt (USD liquidated in the last 1h/4h/12h/24h, split long/short), by_symbol and by_exchange over the last `minutes`, and series (30-minute buckets). The one to call for "how much was liquidated"; it does not return individual orders (get_liquidations) or events (get_liquidation_cascades), and says nothing about open positions (the *_liquidation_map tools). Totals are a floor: Binance and Bitget throttle their feeds. side=long means longs were liquidated. minutes: 1 to 1440.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.

No output schema declared.

No examples provided.

get_long_short_ratio ~22

Latest global long/short account ratio per exchange/symbol.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

get_market_brief ~139

Deterministic market brief for a perp symbol: 24h liquidations (totals, by exchange), current funding + 24h extremes per venue, OI by venue with 1h/4h/24h changes, net position flows, modeled liquidation risk zones above/below price, and top-trader positioning. Free, no LLM involved — ideal input for your own reasoning.

NameTypeReqDescription
symbolstring–Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_microstructure ~141

Cross-venue order book microstructure for BTC, ETH and SOL. Per venue: spread in bps, immediately-executable depth in USD and the bid share of it, measured over a band narrow enough that every venue's stream captured it, each venue around its own mid. Also the basis - how far apart venues price the same asset - plus a per-minute spread history. Does NOT answer "what moves price 0.5%": the streams only carry the innermost levels, so that would be extrapolation, not measurement.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.

No output schema declared.

No examples provided.

get_oi_board ~117

Per-venue open-interest ranking for a perp symbol (e.g. BTCUSDT): OI in coins and USD, market share %, 1h/4h/24h OI change % and USD flow, and OI / 24h-volume ratio per exchange, plus market totals.

NameTypeReqDescription
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_open_interest ~22

Latest open interest (contracts and USD) per exchange/symbol.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

get_open_interest_history ~186

[measured] Open interest over time for one contract, one row per venue per time bucket: ts (ms), exchange, oi (coins, one side), oi_usd. Use it to see how positioning built up or unwound; for the current snapshot with shares and 1h/4h/24h changes use get_oi_board, for every contract at once get_open_interest. symbol: BASEUSDT (BTCUSDT). minutes: look-back window, 5 to 20160 (14 days); snapped to a fixed set of windows.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_orderbook_heatmap ~254

[measured] Resting limit orders over time on ONE exchange: cells of (time bucket, price bucket, quantity in coins) from archived order-book snapshots, with price_min, price_max, price_step and time_step (seconds) describing the grid. Shows where bid and ask walls stood and when they were pulled; not liquidations (see get_liquidation_heatmap for those) and not trades (get_footprint). exchange: binance | bybit | okx. symbol: BTCUSDT, ETHUSDT or SOLUSDT only. minutes: 1 to 1440.

NameTypeReqDescription
exchangestringyesVenue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.
minutesinteger–Look-back window in minutes.
symbolstringyesContract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).

No output schema declared.

No examples provided.

get_positioning_regime ~121

Per-coin positioning regime from price direction crossed with open interest. price up + OI up = new longs; price up + OI down = short covering (a rally with no new buyers); price down + OI up = new shorts; price down + OI down = long flush. Returns a market summary (coins and net OI per regime) plus per coin the price change, OI change and current OI over the window.

NameTypeReqDescription
minutesinteger–Look-back window in minutes.

No output schema declared.

No examples provided.

get_precedents ~263

[measured] When did the market look like this before, and what did price do next? Scans our hourly archive for hours whose positioning resembled now (OI change 24h within 3 pp, funding APR within 15 points and same sign, long share within 5 pp, liquidation volume within x2.5), one per day, and returns the 24h and 72h price outcome of those look-alikes: count, share that went up, median and quartiles, worst and best, next to the unconditional base rate over the same archive. `verdict` says whether the sample is big enough to mean anything. Frequencies from our hourly archive (since 2026-07-18), NOT a forecast. Priced: $0.05 per call (x402), 10 prepaid credits, 10 of a free key's 100 daily units, or Pro/Bot.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
coinstring–Base asset, e.g. BTC, ETH, SOL (no USDT suffix).

No output schema declared.

No examples provided.

get_prediction_markets ~175

[measured] Polymarket crypto prediction markets for a coin: each market's probability, strike and its distance from the live price, 24h change, volume and liquidity; the market-implied median price of every 'above $X on <date>' ladder; and the coin's derivatives positioning now (funding, long share, OI change). Priced: $0.02 per call (x402), 4 credits, or a key's quota.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
coin––BTC, ETH, SOL ...; all crypto markets when omitted.
limitinteger–How many events, 1-50.

No output schema declared.

No examples provided.

get_smart_money ~275

[measured] Smart money on Hyperliquid: how whale wallets are positioned and what they did. Per coin: whale accounts long vs short, notional and leverage per side, notional within 5% of its liquidation price, and the flow over the window (what the same wallets added and cut, in coins valued at today's mark, so a price move is not counted as buying), plus the largest wallet moves with addresses. From hourly snapshots of about 13,600 accounts with exchange-reported liquidation prices. Large is not the same as right: positioning, not a signal. Look up any address from top_movers with get_hl_account. Priced: $0.03 per call (x402), 6 prepaid credits, or a key's quota.

NameTypeReqDescription
api_key––LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.
coin––One coin, e.g. BTC, ETH, HYPE; all coins when omitted.
min_account_usdnumber–A whale holds at least this much open notional, USD.
window_hinteger–Flow window in hours: 4, 24 or 72.

No output schema declared.

No examples provided.

Install

How do I install the LiquidVision — Crypto Derivatives Data MCP server?

LiquidVision — Crypto Derivatives Data is a hosted endpoint at https://liquidvision.app/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 · liquidvision.app

# add to Claude Code
claude mcp add --transport http app-liquidvision-derivatives 'https://liquidvision.app/mcp'
Common questions

What is the LiquidVision — Crypto Derivatives Data MCP server?

LiquidVision — Crypto Derivatives Data is an MCP server listed in the public MCP registry as app.liquidvision/derivatives. Crypto derivatives data and answers for AI agents: smart money, liquidations, funding, 13 venues. This page covers its hosted endpoint (https://liquidvision.app/mcp).

Is the LiquidVision — Crypto Derivatives Data MCP server safe to use?

LiquidVision — Crypto Derivatives Data scores 80 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 LiquidVision — Crypto Derivatives Data MCP server expose?

LiquidVision — Crypto Derivatives Data exposes 69 tools: list_markets, get_accuracy, get_funding_rates, get_microstructure, get_positioning_regime, and 64 more. Their descriptions and schemas cost roughly 13,895 tokens of context every time the server is loaded.

Does the LiquidVision — Crypto Derivatives Data MCP server require authentication?

No. We connected to LiquidVision — Crypto Derivatives Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LiquidVision — Crypto Derivatives Data MCP server still maintained?

LiquidVision — Crypto Derivatives Data 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 LiquidVision — Crypto Derivatives Data MCP server?

VerifyMCP ran 13 checks on LiquidVision — Crypto Derivatives Data, 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.