Skip to content

LiquidVision — Crypto Derivatives Data MCP server

app.liquidvision/derivativesliquidvision.appstreamable-httpv1.4.0Scanned

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

60 tools: 1 can delete or cancel things, 2 do something that can't be undone, 7 change things and 50 only read.

Tools: 1 delete, 2 irreversible, 7 write, 50 read.
  • Reads private data · 1
  • Reads text others write · 60
  • Can send data out · 1
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LiquidVision — Crypto Derivatives Data MCP server can do

The LiquidVision — Crypto Derivatives Data MCP server is published by liquidvision.app, a domain the MCP Registry verified. It has 60 tools. It can delete or cancel things (1 tool: delete_alert), do things that cannot be undone, such as sending, paying or publishing (buy_credits and buy_day_pass) and create or change data (7 tools: ask, test_rule, scan_rule, check_position and 3 more). 50 tools only read.

1 tool reads private data (get_api_key); 60 tools bring in text other people can write (list_markets, get_accuracy, get_funding_rates and 57 more); 1 tool can send data out of your system (create_alert). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

60 tools

Deletes or cancels 1Claude Code: deny
  • delete_alertPermanently delete one webhook alert subscription.Reads text others writeNo findings

    Why it is in this group

    • The name "delete_alert" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 2Claude Code: ask
  • buy_credits[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.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "buy_credits" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • buy_day_pass[payment] A 24-hour Pro API key for ONE x402 USDC payment of $1.00 (Base or Arbitrum), no email or account: liquidation maps and heatmaps at full resolution without the hourly cap,…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "buy_day_pass" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    [payment] A 24-hour Pro API key for ONE x402 USDC payment of $1.00 (Base or Arbitrum), no email or account: liquidation maps and heatmaps at full resolution without the hourly cap, 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 7Claude Code: ask
  • askONE 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`:…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 a narrative with an LLM call explain_market.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_position[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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • create_alertSubscribe an HTTPS URL to push alerts instead of polling (Pro: 3, Bot: 20 subscriptions).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "create_alert" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • credits_balance[account] Remaining prepaid credits on a key bought with buy_credits.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_api_keyGet a free LiquidVision API key for this agent's owner, by email, without a browser.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_api_key" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "get" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "get_api_key" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_api_key" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • scan_rule[measured] One rule tested on up to 100 coins in a single call: on which coins it was true in our hourly archive, what price did over the next 24 h and 72 h per coin (share up, med…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] One rule tested on up to 100 coins in a single call: on which coins it was true in our hourly archive, what price did over the next 24 h and 72 h per coin (share up, median, worst, best) next to each coin's base rate, the POOLED outcome across coins with the number of distinct days behind it (coins move together, so days, not episodes, are the sample), and `true_now`: the coins the rule is true on right now. Use it to find where a setup has occurred and where it is live, instead of calling test_rule per coin. Frequencies from our archive, NOT a forecast; the note explains why the best of many scans is not an edge. Priced: $1.00 per call (x402, USDC on Base or Arbitrum), 200 prepaid credits (one $1 pack), or a Pro/Bot key. Takes 10-40 s on a cold cache.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • test_rule[measured] Test a trigger against our hourly archive BEFORE acting on it or alerting on it: when was this rule true before, and what did price do next?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] Test a trigger against our hourly archive BEFORE acting on it or alerting on it: when was this rule true before, and what did price do next? Returns matched hours, independent episodes (one per 24 h) with each one's 24 h and 72 h return, the outcome statistics (share up, median, quartiles, worst, best), the unconditional base rate over the same hours, whether the rule is true right now, and a `verdict` on sample size. The rule syntax is the condition-alert syntax, so a rule that tests well becomes create_alert(type= 'condition', ...) with the same metric/op/threshold. Frequencies from our archive (hourly, since 2026-07 for BTC/ETH/SOL), NOT a forecast. Priced: $0.10 per call (x402), 20 prepaid credits, a free key's daily quota (20 of its 100 units), or Pro/Bot.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 50Show 50 read-only tools
  • attest_snapshot[receipt] A SIGNED snapshot: the wrapped endpoint's JSON plus an attestation (SHA-256 of the canonical JSON, server time, Ed25519 signature, key id).Reads text others writeNo findings

    Why it is in this group

    • The name "attest_snapshot" says "snapshot": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • explain_marketAI risk-intelligence answer: ask e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "explain_market" says "explain": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    AI risk-intelligence answer: ask e.g. 'Why did BTC drop 4%?' and get a concise grounded explanation (liquidation cascades, funding extremes, where the positions sit, next risk zone) computed from live derivatives data across 13 venues (CEXs, Hyperliquid and GMX).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_accuracy[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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_accuracy" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_arbitrum_perpsArbitrum 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_arbitrum_perps" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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'.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_cash_flowsDerivatives cash flow per exchange: net USD into/out of open interest over 1h/4h/24h windows, per core symbol.Reads text others writeNo findings

    Why it is in this group

    • The name "get_cash_flows" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Derivatives cash flow per exchange: net USD into/out of open interest over 1h/4h/24h windows, per core symbol. Positive = money flowing in.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_crypto_twitter[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 +1…Reads text others writeNo findings

    Why it is in this group

    • The name "get_crypto_twitter" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    [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. Priced: $0.02 per call (x402), 4 prepaid credits, or a key's quota.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_cvdCumulative volume delta split by trade size (retail <$10K, mid <$100K, large <$1M, whale >$1M).Reads text others writeNo findings

    Why it is in this group

    • The name "get_cvd" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_defi_liquidations[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 …Reads text others writeNo findings

    Why it is in this group

    • The name "get_defi_liquidations" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_detective_events[measured] Detective: what the watched large holders did.Reads text others writeNo findings

    Why it is in this group

    • The name "get_detective_events" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_fear_greed[measured] Crypto fear & greed from DERIVATIVES positioning, 0 extreme fear ..Reads text others writeNo findings

    Why it is in this group

    • The name "get_fear_greed" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_footprint[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,…Reads text others writeNo findings

    Why it is in this group

    • The name "get_footprint" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_funding_arbitrage[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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_funding_arbitrage" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_funding_dispersionCoins ranked by how far funding disagrees ACROSS exchanges.Reads text others writeNo findings

    Why it is in this group

    • The name "get_funding_dispersion" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_funding_history[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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_funding_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_funding_ratesLatest perpetual funding rates and mark prices for every tracked exchange/symbol pair.Reads text others writeNo findings

    Why it is in this group

    • The name "get_funding_rates" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Latest perpetual funding rates and mark prices for every tracked exchange/symbol pair. Positive rate = longs pay shorts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_funding_settlementsSettled funding rates, one row per settlement, from Binance and Bybit history — up to 730 days for any pool coin (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "get_funding_settlements" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hip3_markets[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 l…Reads text others writeNo findings

    Why it is in this group

    • The name "get_hip3_markets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_history[measured] Historical rows as CSV, for backtests.Reads text others writeNo findings

    Why it is in this group

    • The name "get_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hl_account[measured] One Hyperliquid account by address: live positions (size, entry, mark, liquidation price, distance to liquidation, leverage, unrealized PnL), account value, and its arch…Reads text others writeNo findings

    Why it is in this group

    • The name "get_hl_account" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hl_builder_markets[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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_hl_builder_markets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hl_liquidation_map[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 s…Reads text others writeNo findings

    Why it is in this group

    • The name "get_hl_liquidation_map" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hl_top_traders[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),…Reads text others writeNo findings

    Why it is in this group

    • The name "get_hl_top_traders" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hl_whales[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 li…Reads text others writeNo findings

    Why it is in this group

    • The name "get_hl_whales" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_lighter_liquidation_map[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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_lighter_liquidation_map" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_lighter_whales[measured] Leveraged positions on Lighter with the exchange-reported liquidation price, closest to liquidation first (sort='value' = largest first).Reads text others writeNo findings

    Why it is in this group

    • The name "get_lighter_whales" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_liquidation_cascades[measured, PAST] Liquidation CASCADES as discrete events: bursts of liquidations detected against each coin's own 7-day normal minute.Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidation_cascades" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_liquidation_heatmap[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 liqu…Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidation_heatmap" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_liquidation_map[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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidation_map" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_liquidations[measured, PAST] Individual liquidation ORDERS that already happened (side, price, qty), newest first, at most `limit` rows (max 2000).Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidations" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_liquidations_summary[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`,…Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidations_summary" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_long_short_ratioLatest global long/short account ratio per exchange/symbol.Reads text others writeNo findings

    Why it is in this group

    • The name "get_long_short_ratio" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Latest global long/short account ratio per exchange/symbol.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_market_briefDeterministic 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 flo…Reads text others writeNo findings

    Why it is in this group

    • The name "get_market_brief" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_microstructureCross-venue order book microstructure for BTC, ETH and SOL.Reads text others writeNo findings

    Why it is in this group

    • The name "get_microstructure" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_oi_boardPer-venue open-interest ranking for a perp symbol (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "get_oi_board" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_open_interestLatest open interest (contracts and USD) per exchange/symbol.Reads text others writeNo findings

    Why it is in this group

    • The name "get_open_interest" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Latest open interest (contracts and USD) per exchange/symbol.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_open_interest_history[measured] Open interest over time for one contract, one row per venue per time bucket: ts (ms), exchange, oi (coins, one side), oi_usd.Reads text others writeNo findings

    Why it is in this group

    • The name "get_open_interest_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_orderbook_heatmap[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, pr…Reads text others writeNo findings

    Why it is in this group

    • The name "get_orderbook_heatmap" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_positioning_regimePer-coin positioning regime from price direction crossed with open interest.Reads text others writeNo findings

    Why it is in this group

    • The name "get_positioning_regime" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_precedents[measured] When did the market look like this before, and what did price do next?Reads text others writeNo findings

    Why it is in this group

    • The name "get_precedents" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_prediction_markets[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-imp…Reads text others writeNo findings

    Why it is in this group

    • The name "get_prediction_markets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_smart_money[measured] Smart money on Hyperliquid: how whale wallets are positioned and what they did.Reads text others writeNo findings

    Why it is in this group

    • The name "get_smart_money" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_spoofingOrder-book wall lifecycle heuristic: large levels classified as active_wall / absorbed / pulled_wall / suspected_spoof based on whether trades executed into them before they vanish…Reads text others writeNo findings

    Why it is in this group

    • The name "get_spoofing" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Order-book wall lifecycle heuristic: large levels classified as active_wall / absorbed / pulled_wall / suspected_spoof based on whether trades executed into them before they vanished.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_stocksCrypto-related equities (COIN, MSTR, miners) and spot BTC/ETH ETF quotes: price, day change %, range, volume.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stocks" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Crypto-related equities (COIN, MSTR, miners) and spot BTC/ETH ETF quotes: price, day change %, range, volume. ~15-min delayed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_token_unlocksUpcoming token unlock events for pool coins, nearest first: next unlock timestamp and token amount per public vesting schedule.Reads text others writeNo findings

    Why it is in this group

    • The name "get_token_unlocks" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Upcoming token unlock events for pool coins, nearest first: next unlock timestamp and token amount per public vesting schedule.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_tokenized_stocks[measured] Tokenized stocks, indices, ETFs, commodities, FX, rates and pre-IPO names traded as PERPS on DEXs (Lighter, Hyperliquid builder markets, Ostium and gTrade): one row per …Reads text others writeNo findings

    Why it is in this group

    • The name "get_tokenized_stocks" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] Tokenized stocks, indices, ETFs, commodities, FX, rates and pre-IPO names traded as PERPS on DEXs (Lighter, Hyperliquid builder markets, Ostium and gTrade): one row per underlying (NVDA, TSLA, S&P 500, Gold, EUR/USD, Anthropic...) with every venue's mark, open interest, 24 h volume, funding APR and the price gap between venues in bps. asset_class filters: equity | crypto_equity | etf | index | commodity | fx | rates | preipo. Use get_hl_builder_markets for the raw Hyperliquid HIP-3 list by dex.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_top_tradersTop traders on OKX copy trading, Hyperliquid and GMX (public data, free): total PnL, win rate, AUM, copiers, live open positions (pair, side, leverage, entry, uPnL) and recently cl…Reads text others writeNo findings

    Why it is in this group

    • The name "get_top_traders" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Top traders on OKX copy trading, Hyperliquid and GMX (public data, free): total PnL, win rate, AUM, copiers, live open positions (pair, side, leverage, entry, uPnL) and recently closed trades with realized PnL. For a ranked list of consistently profitable Hyperliquid wallets with a profile per address, use get_hl_top_traders and get_trader_profile (priced).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_trader_profile[measured] Is this Hyperliquid wallet a good trader?Reads text others writeNo findings

    Why it is in this group

    • The name "get_trader_profile" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] Is this Hyperliquid wallet a good trader? PnL and ROI by day, week, month and all time; win rate, profit factor, average win and loss and fees over its last 2,000 fills; favorite coins; leverage habits and how often it sat within 5% of liquidation (our hourly snapshots); open positions now. Priced: $0.02 per call (x402), 4 credits, or a key's quota.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_alertsThe webhook alert subscriptions that belong to the caller's API key (read-only): id, type, url, filters (symbol, min_usd, x_normal, max_dist_pct) and delivery health: last_status (…Reads text others writeNo findings

    Why it is in this group

    • The name "list_alerts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The webhook alert subscriptions that belong to the caller's API key (read-only): id, type, url, filters (symbol, min_usd, x_normal, max_dist_pct) and delivery health: last_status (HTTP code or error of the last delivery), fails (consecutive failures; a subscription pauses itself at 20) and active. Call it to find the id for delete_alert or to check why alerts stopped arriving. Needs a Pro or Bot key, from the MCP connection's X-API-Key header or the api_key argument; without one it returns an error object, not an exception.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_history_packages[measured] Monthly Parquet history packages for backtests: liquidations (11 venues), funding hourly and settlements, open interest hourly, Hyperliquid and Lighter positions with li…Reads text others writeNo findings

    Why it is in this group

    • The name "list_history_packages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] Monthly Parquet history packages for backtests: liquidations (11 venues), funding hourly and settlements, open interest hourly, Hyperliquid and Lighter positions with liquidation prices — one file per dataset per month since 2026-07 with rows, bytes and sha256. Each entry has `url` (download with the API key in X-API-Key) and `available` for the caller's tier: Pro = this month and the previous one, Bot = all, free = none (use get_history for the last 24 h).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_markets[measured] What exists: every venue we track and, for each, the contracts with live open interest right now (BASEUSDT symbols), plus the top-100 coin pool.Reads text others writeNo findings

    Why it is in this group

    • The name "list_markets" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    [measured] What exists: every venue we track and, for each, the contracts with live open interest right now (BASEUSDT symbols), plus the top-100 coin pool. Call this first when unsure which symbol or exchange string another tool accepts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

60 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write60
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__derivatives__create_alert"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (1 destructive, 2 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://liquidvision.app/mcp: tools/list returned 69 tools to an anonymous client, including delete_alert (destructive), buy_credits (irreversible), buy_day_pass (irreversible), ask (write), test_rule (write) and 7 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 12
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "buy_credits" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "buy_day_pass" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "get_api_key" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_api_key" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 12.View diff
    • Tools that change things, listed without credentials: 3 to 12
  2. Tools9 added, 10 changed.+9 added~10 changedView diff
  3. Tools9 added, 42 changed.+9 added~42 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  5. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http derivatives https://liquidvision.app/mcp
claude mcp add --transport http derivatives https://liquidvision.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__derivatives__list_markets",
      "mcp__derivatives__get_accuracy",
      "mcp__derivatives__get_funding_rates",
      "mcp__derivatives__get_microstructure",
      "mcp__derivatives__get_positioning_regime",
      "mcp__derivatives__get_liquidation_cascades",
      "mcp__derivatives__list_history_packages",
      "mcp__derivatives__get_funding_arbitrage",
      "mcp__derivatives__get_funding_dispersion",
      "mcp__derivatives__get_funding_settlements",
      "mcp__derivatives__get_open_interest",
      "mcp__derivatives__get_open_interest_history",
      "mcp__derivatives__get_funding_history",
      "mcp__derivatives__get_long_short_ratio",
      "mcp__derivatives__get_liquidations",
      "mcp__derivatives__get_liquidations_summary",
      "mcp__derivatives__get_oi_board",
      "mcp__derivatives__get_cash_flows",
      "mcp__derivatives__get_arbitrum_perps",
      "mcp__derivatives__get_top_traders",
      "mcp__derivatives__get_token_unlocks",
      "mcp__derivatives__get_stocks",
      "mcp__derivatives__get_liquidation_map",
      "mcp__derivatives__get_hl_liquidation_map",
      "mcp__derivatives__get_liquidation_heatmap",
      "mcp__derivatives__get_orderbook_heatmap",
      "mcp__derivatives__get_market_brief",
      "mcp__derivatives__get_precedents",
      "mcp__derivatives__get_crypto_twitter",
      "mcp__derivatives__get_fear_greed",
      "mcp__derivatives__get_hl_top_traders",
      "mcp__derivatives__get_trader_profile",
      "mcp__derivatives__get_prediction_markets",
      "mcp__derivatives__get_defi_liquidations",
      "mcp__derivatives__get_smart_money",
      "mcp__derivatives__attest_snapshot",
      "mcp__derivatives__explain_market",
      "mcp__derivatives__get_footprint",
      "mcp__derivatives__get_cvd",
      "mcp__derivatives__get_spoofing",
      "mcp__derivatives__get_history",
      "mcp__derivatives__list_alerts",
      "mcp__derivatives__get_hl_whales",
      "mcp__derivatives__get_detective_events",
      "mcp__derivatives__get_lighter_liquidation_map",
      "mcp__derivatives__get_lighter_whales",
      "mcp__derivatives__get_hl_account",
      "mcp__derivatives__get_tokenized_stocks",
      "mcp__derivatives__get_hl_builder_markets",
      "mcp__derivatives__get_hip3_markets"
    ],
    "ask": [
      "mcp__derivatives__ask",
      "mcp__derivatives__test_rule",
      "mcp__derivatives__scan_rule",
      "mcp__derivatives__check_position",
      "mcp__derivatives__buy_credits",
      "mcp__derivatives__buy_day_pass",
      "mcp__derivatives__credits_balance",
      "mcp__derivatives__get_api_key",
      "mcp__derivatives__create_alert"
    ],
    "deny": [
      "mcp__derivatives__delete_alert"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as derivatives. Review it before you use it.

Capability tags behind 60 rules
  • mcp__derivatives__list_markets untrusted-input
  • mcp__derivatives__get_accuracy untrusted-input
  • mcp__derivatives__get_funding_rates untrusted-input
  • mcp__derivatives__get_microstructure untrusted-input
  • mcp__derivatives__get_positioning_regime untrusted-input
  • mcp__derivatives__get_liquidation_cascades untrusted-input
  • mcp__derivatives__list_history_packages untrusted-input
  • mcp__derivatives__get_funding_arbitrage untrusted-input
  • mcp__derivatives__get_funding_dispersion untrusted-input
  • mcp__derivatives__get_funding_settlements untrusted-input
  • mcp__derivatives__get_open_interest untrusted-input
  • mcp__derivatives__get_open_interest_history untrusted-input
  • mcp__derivatives__get_funding_history untrusted-input
  • mcp__derivatives__get_long_short_ratio untrusted-input
  • mcp__derivatives__get_liquidations untrusted-input
  • mcp__derivatives__get_liquidations_summary untrusted-input
  • mcp__derivatives__get_oi_board untrusted-input
  • mcp__derivatives__get_cash_flows untrusted-input
  • mcp__derivatives__get_arbitrum_perps untrusted-input
  • mcp__derivatives__get_top_traders untrusted-input
  • mcp__derivatives__get_token_unlocks untrusted-input
  • mcp__derivatives__get_stocks untrusted-input
  • mcp__derivatives__get_liquidation_map untrusted-input
  • mcp__derivatives__get_hl_liquidation_map untrusted-input
  • mcp__derivatives__get_liquidation_heatmap untrusted-input
  • mcp__derivatives__get_orderbook_heatmap untrusted-input
  • mcp__derivatives__get_market_brief untrusted-input
  • mcp__derivatives__ask untrusted-input
  • mcp__derivatives__get_precedents untrusted-input
  • mcp__derivatives__test_rule untrusted-input
  • mcp__derivatives__get_crypto_twitter untrusted-input
  • mcp__derivatives__get_fear_greed untrusted-input
  • mcp__derivatives__get_hl_top_traders untrusted-input
  • mcp__derivatives__get_trader_profile untrusted-input
  • mcp__derivatives__get_prediction_markets untrusted-input
  • mcp__derivatives__get_defi_liquidations untrusted-input
  • mcp__derivatives__get_smart_money untrusted-input
  • mcp__derivatives__scan_rule untrusted-input
  • mcp__derivatives__check_position untrusted-input
  • mcp__derivatives__attest_snapshot untrusted-input
  • mcp__derivatives__buy_credits untrusted-input
  • mcp__derivatives__buy_day_pass untrusted-input
  • mcp__derivatives__credits_balance untrusted-input
  • mcp__derivatives__explain_market untrusted-input
  • mcp__derivatives__get_footprint untrusted-input
  • mcp__derivatives__get_cvd untrusted-input
  • mcp__derivatives__get_spoofing untrusted-input
  • mcp__derivatives__get_api_key private-data, untrusted-input
  • mcp__derivatives__get_history untrusted-input
  • mcp__derivatives__create_alert untrusted-input, outbound
  • mcp__derivatives__list_alerts untrusted-input
  • mcp__derivatives__delete_alert untrusted-input
  • mcp__derivatives__get_hl_whales untrusted-input
  • mcp__derivatives__get_detective_events untrusted-input
  • mcp__derivatives__get_lighter_liquidation_map untrusted-input
  • mcp__derivatives__get_lighter_whales untrusted-input
  • mcp__derivatives__get_hl_account untrusted-input
  • mcp__derivatives__get_tokenized_stocks untrusted-input
  • mcp__derivatives__get_hl_builder_markets untrusted-input
  • mcp__derivatives__get_hip3_markets untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.liquidvision/derivatives/verify?hash=76fcc29e894ea8f65cbdcdb236931ff8bcca3e70c0660140296475e24e375d5c" | jq -e '.changed == false'

Pinned hash 76fcc29e894e, from Nov 12, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.liquidvision/derivatives/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.liquidvision/derivatives
[![Anlyon Radar](https://radar.anlyon.com/badge/app.liquidvision/derivatives.svg)](https://radar.anlyon.com/servers/app.liquidvision/derivatives)

Source: MCP Registry · repository. Synced Nov 12, 2026, 10:17 UTC.

LiquidVision — Crypto Derivatives Data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LiquidVision — Crypto Derivatives Data MCP server safe?

No scan can promise that. What its definitions show: 60 tools, 10 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LiquidVision — Crypto Derivatives Data MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_alert.

Can the LiquidVision — Crypto Derivatives Data MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: buy_credits and buy_day_pass.

What tools does the LiquidVision — Crypto Derivatives Data MCP server have?

60 tools: 1 destructive, 2 irreversible, 7 write, 50 read. delete_alert, buy_credits, buy_day_pass, ask, test_rule, scan_rule, check_position, credits_balance and 52 more.

Does the LiquidVision — Crypto Derivatives Data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LiquidVision — Crypto Derivatives Data MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_alert.

Has the LiquidVision — Crypto Derivatives Data MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.