LiquidVision — Crypto Derivatives Data
REMOTE · LIQUIDVISION.APP · SCANNED SEP 27
Exchange-exact crypto derivatives data for AI agents: OI, funding, liquidations, 13 venues.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2553 tokens (~88/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (21% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the LiquidVision — Crypto Derivatives Data MCP server?
LiquidVision — Crypto Derivatives Data is a hosted endpoint at https://liquidvision.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · liquidvision.app
claude mcp add --transport http app-liquidvision-derivatives 'https://liquidvision.app/mcp'
{
"mcpServers": {
"app-liquidvision-derivatives": {
"url": "https://liquidvision.app/mcp"
}
}
} {
"servers": {
"app-liquidvision-derivatives": {
"type": "http",
"url": "https://liquidvision.app/mcp"
}
}
} [mcp_servers.app-liquidvision-derivatives] url = "https://liquidvision.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-liquidvision-derivatives": {
"type": "remote",
"url": "https://liquidvision.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-liquidvision-derivatives --url 'https://liquidvision.app/mcp' --transport streamable-http
mcp_servers:
app-liquidvision-derivatives:
url: "https://liquidvision.app/mcp" {
"McpServers": {
"app-liquidvision-derivatives": {
"Transport": "http",
"Url": "https://liquidvision.app/mcp"
}
}
} assistant mcp add app-liquidvision-derivatives -t streamable-http -u 'https://liquidvision.app/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- 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 security
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://liquidvision.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liquidvision.app | CN=YR2,O=Let's Encrypt,C=US | 19 Jul 2026 | 17 Oct 2026 | RSA 2048 | SHA256-RSA | 52d5c47eb4f41b3451b6d429562e06c0f33 |
| SANs: liquidvision.app, www.liquidvision.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of liquidvision.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| liquidvision.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liquidvision.app/mcp | Verified | 200 | |
| http (plaintext) | http://liquidvision.app/mcp | HTTPS enforced | 301 | https://liquidvision.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_market ~93
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).
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_accuracy ~83
[measured] The public accuracy audit: our open interest and funding vs Binance, Bybit, OKX and Hyperliquid's own endpoints, sampled every 10 min (diff %, snapshot age, 24h mean/max), plus how the modeled liquidation map scored against realized liquidations. Read this before trusting any number here with money.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_arbitrum_perps ~77
Arbitrum perps board: GMX v2 open interest per coin and its share of every tracked venue, GMX funding next to the CEX median (8h basis), on-chain liquidations over 24h. Ask this for 'how is Arbitrum positioned vs CEXs'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_cash_flows ~48
Derivatives cash flow per exchange: net USD into/out of open interest over 1h/4h/24h windows, per core symbol. Positive = money flowing in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_cvd ~66
Cumulative volume delta split by trade size (retail <$10K, mid <$100K, large <$1M, whale >$1M). Whale-vs-retail divergence = smart-money signal.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_footprint ~65
Order-flow footprint for a core perp symbol: per candle x price bin, taker buy/sell USD volume and delta (Binance + Bybit trade streams).
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| step | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_funding_dispersion ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_venues | integer | – | – |
| window | integer | – | – |
No output schema declared.
No examples provided.
get_funding_history ~55
Bucketed funding-rate history per exchange for a symbol (e.g. BTCUSDT) over the last `minutes` (5-20160).
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| symbol | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_funding_rates ~34
Latest perpetual funding rates and mark prices for every tracked exchange/symbol pair. Positive rate = longs pay shorts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_funding_settlements ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| exchange | string | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_hl_liquidation_map ~121
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_liquidation_cascades ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_liquidation_heatmap ~82
[modeled] Liquidation heatmap: estimated cluster intensity per price bin over time (grid[time][bin]) with the price path. range: 12h | 1d | 3d | 7d.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
| range | string | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_liquidation_map ~140
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
| range | string | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_liquidations ~54
Recent liquidation events (side, price, qty) across exchanges over the last `minutes` (1-1440). side=long means a long position was liquidated.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_liquidations_summary ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
No output schema declared.
No examples provided.
get_long_short_ratio ~22
Latest global long/short account ratio per exchange/symbol.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_market_brief ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_microstructure ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
No output schema declared.
No examples provided.
get_oi_board ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_open_interest ~22
Latest open interest (contracts and USD) per exchange/symbol.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_open_interest_history ~53
Open interest time series for a symbol (e.g. BTCUSDT) over the last `minutes` (5-10080).
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| symbol | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_orderbook_heatmap ~71
Order book liquidity heatmap grid (time x price buckets with resting quantity) for one exchange (binance/bybit/okx) and symbol (e.g. BTCUSDT).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | – |
| minutes | integer | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_positioning_regime ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
No output schema declared.
No examples provided.
get_spoofing ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
| minutes | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_stocks ~44
Crypto-related equities (COIN, MSTR, miners) and spot BTC/ETH ETF quotes: price, day change %, range, volume. ~15-min delayed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_unlocks ~35
Upcoming token unlock events for pool coins, nearest first: next unlock timestamp and token amount per public vesting schedule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_top_traders ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_markets ~65
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.