# LiquidVision — Crypto Derivatives Data (remote · liquidvision.app)

Exchange-exact crypto derivatives data for AI agents: OI, funding, liquidations, 13 venues.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `liquidvision.app`: 67/100 (this document), [markdown](https://verifymcp.io/servers/app-liquidvision-derivatives/liquidvision.md), [page](https://verifymcp.io/servers/app-liquidvision-derivatives/liquidvision)

## Channel facts

- Endpoint: `https://liquidvision.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 29 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2553 tokens (~88/item across 29 items; 29 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (21% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "app-liquidvision-derivatives": {
      "url": "https://liquidvision.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-liquidvision-derivatives": {
      "type": "http",
      "url": "https://liquidvision.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-liquidvision-derivatives]
url = "https://liquidvision.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-liquidvision-derivatives": {
      "type": "remote",
      "url": "https://liquidvision.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-liquidvision-derivatives --url 'https://liquidvision.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-liquidvision-derivatives:
    url: "https://liquidvision.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-liquidvision-derivatives": {
      "Transport": "http",
      "Url": "https://liquidvision.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-liquidvision-derivatives -t streamable-http -u 'https://liquidvision.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-liquidvision-derivatives": {
      "type": "http",
      "url": "https://liquidvision.app/mcp"
    }
  }
}
```

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

## Changelog

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

### 2026-09-26 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 66, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “explain_market” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 65)

First indexed and scored.

## MCP tools (29)

### `list_markets` (~65 tokens)

[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.

### `get_accuracy` (~83 tokens)

[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.

### `get_funding_rates` (~34 tokens)

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

Output parameters:

- `result` (array)

### `get_microstructure` (~136 tokens)

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.

Input parameters:

- `minutes` (integer)

### `get_positioning_regime` (~116 tokens)

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.

Input parameters:

- `minutes` (integer)

### `get_liquidation_cascades` (~125 tokens)

Liquidation cascades as discrete events rather than a raw feed.

    Each event: coin, which side broke, when it started, how long it ran, total
    and peak-minute USD, how many multiples of that coin's own normal minute it
    was, the move in cross-venue median mark price during it, and what price did
    in the hour after. Also returns market_wide: minutes when three or more
    unrelated coins cascaded together.

Input parameters:

- `hours` (integer)
- `limit` (integer)

### `get_funding_dispersion` (~141 tokens)

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.

Input parameters:

- `limit` (integer)
- `min_venues` (integer)
- `window` (integer)

### `get_funding_settlements` (~93 tokens)

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.

Input parameters:

- `days` (integer)
- `exchange` (string)
- `symbol` (string, required)

### `get_open_interest` (~22 tokens)

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

Output parameters:

- `result` (array)

### `get_open_interest_history` (~53 tokens)

Open interest time series for a symbol (e.g. BTCUSDT) over the last
    `minutes` (5-10080).

Input parameters:

- `minutes` (integer)
- `symbol` (string, required)

Output parameters:

- `result` (array)

### `get_funding_history` (~55 tokens)

Bucketed funding-rate history per exchange for a symbol (e.g. BTCUSDT)
    over the last `minutes` (5-20160).

Input parameters:

- `minutes` (integer)
- `symbol` (string, required)

Output parameters:

- `result` (array)

### `get_long_short_ratio` (~22 tokens)

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

Output parameters:

- `result` (array)

### `get_liquidations` (~54 tokens)

Recent liquidation events (side, price, qty) across exchanges over the
    last `minutes` (1-1440). side=long means a long position was liquidated.

Input parameters:

- `minutes` (integer)

Output parameters:

- `result` (array)

### `get_liquidations_summary` (~69 tokens)

Aggregated market-wide liquidation stats over the last `minutes`:
    1h/4h/12h/24h totals split long/short, per-symbol and per-exchange
    breakdowns, and a 30-min time series.

Input parameters:

- `minutes` (integer)

### `get_oi_board` (~82 tokens)

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.

Input parameters:

- `symbol` (string, required)

### `get_cash_flows` (~48 tokens)

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

### `get_arbitrum_perps` (~77 tokens)

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'.

### `get_top_traders` (~65 tokens)

Top lead traders (OKX copy trading, public data): total PnL, win rate,
    AUM, copiers, live open positions (pair, side, leverage, entry, uPnL) and
    recently closed trades with realized PnL.

### `get_token_unlocks` (~35 tokens)

Upcoming token unlock events for pool coins, nearest first: next unlock
    timestamp and token amount per public vesting schedule.

### `get_stocks` (~44 tokens)

Crypto-related equities (COIN, MSTR, miners) and spot BTC/ETH ETF quotes:
    price, day change %, range, volume. ~15-min delayed.

### `get_liquidation_map` (~140 tokens)

[modeled] Liquidation map for a perp symbol (e.g. BTCUSDT): estimated
    liquidation-cluster notional per price bin, split by leverage tier
    (10x/25x/50x/100x) and by exchange (binance/bybit/okx or 'all'), plus
    cumulative long/short curves from the current price outward.
    range: 12h | 1d | 3d | 7d. Validation vs realized liquidations: see get_accuracy.

Input parameters:

- `exchange` (string)
- `range` (string)
- `symbol` (string, required)

### `get_hl_liquidation_map` (~121 tokens)

[measured] Liquidation map for Hyperliquid, not a model: leveraged
    positions of the ~3000 largest accounts binned by the exchange-reported
    liquidation price, long/short notional per bin, cumulative curves and the
    largest positions. Partial coverage: large accounts only. range: 12h | 1d | 3d | 7d | max (±100%, recommended: large accounts run low leverage).

Input parameters:

- `range` (string)
- `symbol` (string, required)

### `get_liquidation_heatmap` (~82 tokens)

[modeled] Liquidation heatmap: estimated cluster intensity per price bin
    over time (grid[time][bin]) with the price path. range: 12h | 1d | 3d | 7d.

Input parameters:

- `exchange` (string)
- `range` (string)
- `symbol` (string, required)

### `get_orderbook_heatmap` (~71 tokens)

Order book liquidity heatmap grid (time x price buckets with resting
    quantity) for one exchange (binance/bybit/okx) and symbol (e.g. BTCUSDT).

Input parameters:

- `exchange` (string, required)
- `minutes` (integer)
- `symbol` (string, required)

### `get_market_brief` (~104 tokens)

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.

Input parameters:

- `symbol` (string)

### `explain_market` (~93 tokens)

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).

Input parameters:

- `question` (string, required)
- `symbol` (string)

### `get_footprint` (~65 tokens)

Order-flow footprint for a core perp symbol: per candle x price bin,
    taker buy/sell USD volume and delta (Binance + Bybit trade streams).

Input parameters:

- `minutes` (integer)
- `step` (integer)
- `symbol` (string)

### `get_cvd` (~66 tokens)

Cumulative volume delta split by trade size (retail <$10K, mid <$100K,
    large <$1M, whale >$1M). Whale-vs-retail divergence = smart-money signal.

Input parameters:

- `minutes` (integer)
- `symbol` (string)

### `get_spoofing` (~69 tokens)

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.

Input parameters:

- `exchange` (string)
- `minutes` (integer)
- `symbol` (string)

## Diagnostics

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

## Score history

- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 66
- 2026-09-24: 66
- 2026-09-23: 65

## 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. Exchange-exact crypto derivatives data for AI agents: OI, funding, liquidations, 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 67 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 29 tools: list_markets, get_accuracy, get_funding_rates, get_microstructure, get_positioning_regime, and 24 more. Their descriptions and schemas cost roughly 2,230 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 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://liquidvision.app/mcp
- Website: https://liquidvision.app/data
- Changelog RSS feed: https://verifymcp.io/servers/app-liquidvision-derivatives/liquidvision.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-liquidvision-derivatives/liquidvision.json
- HTML version of this page: https://verifymcp.io/servers/app-liquidvision-derivatives/liquidvision