LiquidVision — Crypto Derivatives Data
REMOTE · LIQUIDVISION.APP
Crypto derivatives data and answers for AI agents: smart money, liquidations, funding, 13 venues
Available components
Last scanned (23 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (7 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_alert). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14595 tokens (~211/item across 69 items; 69 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 70 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Nov 26 0
- Tool “buy_day_pass” rewrote its description, which is the text the model reads security
- “attest_snapshot” reworded the description of “params” cosmetic
- “scan_rule” reworded the description of “rules” cosmetic
- “test_rule” reworded the description of “rules” cosmetic
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_day_pass” rewrote its description, which is the text the model reads security
- Tool “get_hl_liquidation_map” rewrote its description, which is the text the model reads security
- Tool “get_lighter_liquidation_map” rewrote its description, which is the text the model reads security
- Tool “get_liquidation_heatmap” rewrote its description, which is the text the model reads security
- Tool “get_liquidation_map” rewrote its description, which is the text the model reads security
- Schema quality: 12896 → 14601 ▼ functional
- New tool “create_watch” functional
- New tool “get_watch” functional
- New tool “get_x_mentions” functional
- New tool “get_x_trends” functional
- New tool “get_x_tweet” functional
- New tool “get_x_user” functional
- New tool “get_x_user_tweets” functional
- New tool “pretrade_check” functional
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask” rewrote its description, which is the text the model reads security
- Tool “explain_market” rewrote its description, which is the text the model reads security
- Tool “get_crypto_twitter” rewrote its description, which is the text the model reads security
- New tool “search_twitter” functional
- Tool “ask” changed its title: Ask a derivatives question cosmetic
- Tool “attest_snapshot” changed its title: Signed data snapshot cosmetic
- Tool “buy_credits” changed its title: Buy prepaid credits cosmetic
- Tool “buy_day_pass” changed its title: Buy a 24-hour key cosmetic
- Tool “check_position” changed its title: Liquidation price of a position cosmetic
- Tool “create_alert” changed its title: Create alert cosmetic
- Tool “credits_balance” changed its title: Prepaid credit balance cosmetic
- Tool “delete_alert” changed its title: Delete alert cosmetic
- Tool “explain_market” changed its title: Market brief for a question cosmetic
- Tool “get_accuracy” changed its title: Our numbers vs the exchanges cosmetic
- Tool “get_api_key” changed its title: Get a free API key cosmetic
- Tool “get_arbitrum_perps” changed its title: Arbitrum perps board cosmetic
- Tool “get_cash_flows” changed its title: Cash flows cosmetic
- Tool “get_crypto_twitter” changed its title: Crypto Twitter pulse cosmetic
- Tool “get_cvd” changed its title: Cumulative volume delta cosmetic
- Tool “get_defi_liquidations” changed its title: DeFi liquidation map (Morpho) cosmetic
- Tool “get_detective_events” changed its title: Detective events cosmetic
- Tool “get_fear_greed” changed its title: Derivatives fear & greed cosmetic
- Tool “get_footprint” changed its title: Footprint cosmetic
- Tool “get_funding_arbitrage” changed its title: Funding arbitrage cosmetic
- Tool “get_funding_dispersion” changed its title: Funding dispersion cosmetic
- Tool “get_funding_history” changed its title: Funding history cosmetic
- Tool “get_funding_rates” changed its title: Funding rates cosmetic
- Tool “get_funding_settlements” changed its title: Funding settlements cosmetic
- Tool “get_hip3_markets” changed its title: Hyperliquid HIP-3 board cosmetic
- Tool “get_history” changed its title: History cosmetic
- Tool “get_hl_account” changed its title: Hyperliquid wallet lookup cosmetic
- Tool “get_hl_builder_markets” changed its title: Hyperliquid builder markets cosmetic
- Tool “get_hl_liquidation_map” changed its title: Hyperliquid liquidation map (measured) cosmetic
- Tool “get_hl_top_traders” changed its title: Top Hyperliquid traders cosmetic
- Tool “get_hl_whales” changed its title: Hyperliquid whale positions cosmetic
- Tool “get_lighter_liquidation_map” changed its title: Lighter liquidation map (measured) cosmetic
- Tool “get_lighter_whales” changed its title: Lighter whales cosmetic
- Tool “get_liquidation_cascades” changed its title: Liquidation cascades cosmetic
- Tool “get_liquidation_heatmap” changed its title: Liquidation heatmap cosmetic
- Tool “get_liquidation_map” changed its title: Liquidation map (modeled) cosmetic
- Tool “get_liquidations” changed its title: Liquidations cosmetic
- Tool “get_liquidations_summary” changed its title: Liquidations summary cosmetic
- Tool “get_long_short_ratio” changed its title: Long short ratio cosmetic
- Tool “get_market_brief” changed its title: Market brief for a coin cosmetic
- Tool “get_microstructure” changed its title: Microstructure cosmetic
- Tool “get_oi_board” changed its title: Open interest board cosmetic
- Tool “get_open_interest” changed its title: Open interest cosmetic
- Tool “get_open_interest_history” changed its title: Open interest history cosmetic
- Tool “get_orderbook_heatmap” changed its title: Orderbook heatmap cosmetic
- Tool “get_positioning_regime” changed its title: Positioning regime cosmetic
- Tool “get_precedents” changed its title: Past hours that resembled now cosmetic
- Tool “get_prediction_markets” changed its title: Polymarket crypto odds cosmetic
- Tool “get_smart_money” changed its title: Smart money on Hyperliquid cosmetic
- Tool “get_spoofing” changed its title: Spoofing cosmetic
- Tool “get_stocks” changed its title: Stocks cosmetic
- Tool “get_token_unlocks” changed its title: Token unlocks cosmetic
- Tool “get_tokenized_stocks” changed its title: Tokenized stocks cosmetic
- Tool “get_top_traders” changed its title: Top traders cosmetic
- Tool “get_trader_profile” changed its title: Hyperliquid trader profile cosmetic
- Tool “list_alerts” changed its title: List alerts cosmetic
- Tool “list_history_packages” changed its title: List history packages cosmetic
- Tool “list_markets” changed its title: List markets and venues cosmetic
- Tool “scan_rule” changed its title: Scan a rule across coins cosmetic
- Tool “test_rule” changed its title: Test a trading rule on the archive cosmetic
- 12 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_api_key” rewrote its description, which is the text the model reads security
- Tool “get_hl_liquidation_map” rewrote its description, which is the text the model reads security
- Tool “get_hl_whales” rewrote its description, which is the text the model reads security
- Tool “get_liquidation_map” rewrote its description, which is the text the model reads security
- Tool “get_precedents” rewrote its description, which is the text the model reads security
- Tool “get_smart_money” rewrote its description, which is the text the model reads security
- Tool “get_tokenized_stocks” rewrote its description, which is the text the model reads security
- Tool “get_top_traders” rewrote its description, which is the text the model reads security
- Tool “test_rule” rewrote its description, which is the text the model reads security
- Schema quality: 10808 → 12600 ▼ functional
- New tool “buy_day_pass” functional
- New tool “get_defi_liquidations” functional
- New tool “get_fear_greed” functional
- New tool “get_hl_top_traders” functional
- New tool “get_prediction_markets” functional
- New tool “get_trader_profile” functional
- New tool “get_crypto_twitter” functional
- New tool “get_smart_money” functional
- “create_alert” reworded the description of “metric” cosmetic
- 11 Nov 26 0
- Tool “create_alert” rewrote its description, which is the text the model reads security
- Tool “get_funding_arbitrage” rewrote its description, which is the text the model reads security
- New tool “scan_rule” functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- Tool “create_alert” rewrote its description, which is the text the model reads security
- Schema quality: 8890 → 10355 ▼ functional
- New tool “attest_snapshot” functional
- New tool “buy_credits” functional
- New tool “check_position” functional
- New tool “credits_balance” functional
- New tool “test_rule” functional
- “create_alert” added an optional parameter “entry” cosmetic
- “create_alert” added an optional parameter “leverage” cosmetic
- “create_alert” added an optional parameter “notional_usd” cosmetic
- “create_alert” added an optional parameter “side” cosmetic
- “create_alert” added an optional parameter “venue” cosmetic
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 +3
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Authorization: unverified → fail ▼ critical
- Tool “get_api_key” rewrote its description, which is the text the model reads security
- Tool “delete_alert” is now declared destructive security
- Schema quality: 151 → 193 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- “ask” reworded the description of “coin” cosmetic
- “ask” reworded the description of “question” cosmetic
- “create_alert” reworded the description of “api_key” cosmetic
- “create_alert” reworded the description of “max_dist_pct” cosmetic
- “create_alert” reworded the description of “metric” cosmetic
- “create_alert” reworded the description of “min_usd” cosmetic
- “create_alert” reworded the description of “op” cosmetic
- “create_alert” reworded the description of “symbol” cosmetic
- “create_alert” reworded the description of “threshold” cosmetic
- “create_alert” reworded the description of “type” cosmetic
- “create_alert” reworded the description of “url” cosmetic
- “create_alert” reworded the description of “x_normal” cosmetic
- “delete_alert” reworded the description of “api_key” cosmetic
- “delete_alert” reworded the description of “id” cosmetic
- “explain_market” reworded the description of “question” cosmetic
- “explain_market” reworded the description of “symbol” cosmetic
- “get_api_key” reworded the description of “email” cosmetic
- “get_cvd” reworded the description of “minutes” cosmetic
- “get_cvd” reworded the description of “symbol” cosmetic
- “get_detective_events” reworded the description of “chain” cosmetic
- “get_detective_events” reworded the description of “hours” cosmetic
- “get_detective_events” reworded the description of “limit” cosmetic
- “get_detective_events” reworded the description of “symbol” cosmetic
- “get_detective_events” reworded the description of “type” cosmetic
- “get_footprint” reworded the description of “minutes” cosmetic
- “get_footprint” reworded the description of “step” cosmetic
- “get_footprint” reworded the description of “symbol” cosmetic
- “get_funding_arbitrage” reworded the description of “limit” cosmetic
- “get_funding_arbitrage” reworded the description of “min_venues” cosmetic
- “get_funding_dispersion” reworded the description of “limit” cosmetic
- “get_funding_dispersion” reworded the description of “min_venues” cosmetic
- “get_funding_dispersion” reworded the description of “window” cosmetic
- “get_funding_history” reworded the description of “minutes” cosmetic
- “get_funding_history” reworded the description of “symbol” cosmetic
- “get_funding_settlements” reworded the description of “days” cosmetic
- “get_funding_settlements” reworded the description of “exchange” cosmetic
- “get_funding_settlements” reworded the description of “symbol” cosmetic
- “get_hip3_markets” reworded the description of “dex” cosmetic
- “get_hip3_markets” reworded the description of “limit” cosmetic
- “get_hip3_markets” reworded the description of “sort” cosmetic
- “get_history” reworded the description of “api_key” cosmetic
- “get_history” reworded the description of “dataset” cosmetic
- “get_history” reworded the description of “end” cosmetic
- “get_history” reworded the description of “exchange” cosmetic
- “get_history” reworded the description of “limit” cosmetic
- “get_history” reworded the description of “start” cosmetic
- “get_history” reworded the description of “symbol” cosmetic
- “get_hl_account” reworded the description of “address” cosmetic
- “get_hl_account” reworded the description of “api_key” cosmetic
- “get_hl_liquidation_map” reworded the description of “range” cosmetic
- “get_hl_liquidation_map” reworded the description of “symbol” cosmetic
- “get_hl_whales” reworded the description of “coin” cosmetic
- “get_hl_whales” reworded the description of “limit” cosmetic
- “get_hl_whales” reworded the description of “max_dist_pct” cosmetic
- “get_hl_whales” reworded the description of “min_usd” cosmetic
- “get_hl_whales” reworded the description of “side” cosmetic
- “get_hl_whales” reworded the description of “sort” cosmetic
- “get_lighter_liquidation_map” reworded the description of “range” cosmetic
- “get_lighter_liquidation_map” reworded the description of “symbol” cosmetic
- “get_lighter_whales” reworded the description of “coin” cosmetic
- “get_lighter_whales” reworded the description of “limit” cosmetic
- “get_lighter_whales” reworded the description of “max_dist_pct” cosmetic
- “get_lighter_whales” reworded the description of “min_usd” cosmetic
- “get_lighter_whales” reworded the description of “side” cosmetic
- “get_lighter_whales” reworded the description of “sort” cosmetic
- “get_liquidation_cascades” reworded the description of “hours” cosmetic
- “get_liquidation_cascades” reworded the description of “limit” cosmetic
- “get_liquidation_heatmap” reworded the description of “exchange” cosmetic
- “get_liquidation_heatmap” reworded the description of “range” cosmetic
- “get_liquidation_heatmap” reworded the description of “symbol” cosmetic
- “get_liquidation_map” reworded the description of “exchange” cosmetic
- “get_liquidation_map” reworded the description of “range” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://liquidvision.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liquidvision.app | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 57c61cef4d5908d5ee9e72a8008f84ebdee |
| SANs: *.liquidvision.app, liquidvision.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of liquidvision.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| liquidvision.app. | DS published | 2371 | 13 | Verified |
| liquidvision.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liquidvision.app/mcp | Verified | 200 | |
| http (plaintext) | http://liquidvision.app/mcp | HTTPS enforced | 301 | https://liquidvision.app/mcp |
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 →
get_spoofing Spoofing ~160
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 | – | Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it. |
| minutes | integer | – | Look-back window in minutes. |
| symbol | string | – | Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT). |
No output schema declared.
No examples provided.
get_stocks 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 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_tokenized_stocks Tokenized stocks ~180
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | – | – | Asset class filter: stocks | indices | commodities | forex. Omit for all. |
No output schema declared.
No examples provided.
get_top_traders Top traders ~107
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trader_profile Hyperliquid trader profile ~163
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Hyperliquid wallet, 0x + 40 hex characters. |
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
No output schema declared.
No examples provided.
get_watch Watch ~87
[alert] The events of a watch bought with create_watch, newest first, with the watch's own parameters and expiry. Free. An empty list means the condition has not fired yet.
| Name | Type | Req | Description |
|---|---|---|---|
| since | integer | – | Only events sent after this time in ms; 0 for all. |
| watch_id | string | yes | The watch_id returned by create_watch (w_...). |
No output schema declared.
No examples provided.
get_x_mentions X mentions ~152
[measured] Posts that mention an X (Twitter) account, newest first, up to 20 a page with author, followers and metrics, plus next_cursor. What people say TO or ABOUT an account. Always paid per call: $0.005 (x402, MPP or 1 prepaid credit); no key's daily allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| cursor | string | – | next_cursor of the previous page; empty for the first page. |
| username | string | yes | X handle without @, e.g. HyperliquidX. |
No output schema declared.
No examples provided.
get_x_trends X trends ~160
[measured] Trending topics on X (Twitter) right now for a location, with rank, name and the search query of each trend (pass it to search_twitter). Not limited to crypto. Always paid per call: $0.005 (x402, MPP or 1 prepaid credit); no key's daily allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| count | integer | – | How many trends, 5 to 50. |
| woeid | integer | – | Location: 1 = worldwide, or a country/city WOEID (23424977 = United States). |
No output schema declared.
No examples provided.
get_x_tweet X tweet ~159
[measured] One X (Twitter) post by ID with its text, author and metrics, plus one page of up to 20 replies and next_cursor for more. Read a thread or the reaction to a post. Always paid per call: $0.005 (x402, MPP or 1 prepaid credit); no key's daily allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| cursor | string | – | next_cursor of the previous page; empty for the first page. |
| tweet_id | string | yes | Numeric ID of the post (the digits at the end of its URL). |
No output schema declared.
No examples provided.
get_x_user X user ~127
[measured] An X (Twitter) account by username: followers, following, bio, post count, verification, account age and pinned tweets. Any account, not only crypto. Always paid per call: $0.005 (x402, MPP or 1 prepaid credit); no key's daily allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| username | string | yes | X handle without @, e.g. HyperliquidX. |
No output schema declared.
No examples provided.
get_x_user_tweets X user tweets ~164
[measured] The latest posts of an X (Twitter) account, newest first, up to 20 a page with text, time, likes, retweets, replies, quotes and views, plus next_cursor. For a keyword search use search_twitter. Always paid per call: $0.005 (x402, MPP or 1 prepaid credit); no key's daily allowance covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| cursor | string | – | next_cursor of the previous page; empty for the first page. |
| username | string | yes | X handle without @, e.g. HyperliquidX. |
No output schema declared.
No examples provided.
list_alerts List alerts ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
No output schema declared.
No examples provided.
list_history_packages List history packages ~161
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
No output schema declared.
No examples provided.
list_markets List markets and venues ~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.
pretrade_check Pretrade check ~258
[measured + modeled] Call this BEFORE opening a leveraged perpetual position: one answer with the liquidation price on 12 venues, the liquidation levels between the price and it, how often price moved that far in our archive, derivatives fear & greed, Hyperliquid whale positioning with its 24 h flow, funding cost per day, and `flags`: the measured facts that go against the trade. Replaces check_position + the map summaries + get_fear_greed + get_smart_money. Not a signal. Priced: $0.05 (x402, MPP), 10 prepaid credits, or a key's daily units.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| entry | – | – | Entry price; omit to use the current mark. |
| leverage | number | yes | Leverage of the position, e.g. 20. |
| notional_usd | number | – | Position size in USD (margin x leverage). |
| side | string | yes | long or short. |
| symbol | string | yes | Base asset or contract, e.g. BTC or BTCUSDT. |
No output schema declared.
No examples provided.
scan_rule Scan a rule across coins ~383
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| coins | integer | – | How many coins to scan, the largest by open interest first (5-100). |
| rules | string | yes | Up to 3 rules joined by commas or 'and', each metric>threshold or metric<threshold. Metrics: price_chg_1h_pct, price_chg_24h_pct, oi_chg_1h_pct, oi_chg_24h_pct, funding_apr_pct, long_pct, liq_1h_usd,… |
No output schema declared.
No examples provided.
search_twitter Search X (Twitter) ~241
[measured] Raw X (Twitter) search: one page of up to ~20 posts for any advanced-search query, each with text, time, author (username, followers, verified), likes, retweets, replies, quotes and views, plus next_cursor for the following page. Not limited to crypto. For a coin's sentiment next to its positioning use get_crypto_twitter instead. Always paid per call: $0.005 a page (x402, MPP or 1 prepaid credit); no key's daily allowance covers it, Pro and Bot included.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| cursor | string | – | next_cursor of the previous page; empty for the first page. |
| query | string | yes | X advanced-search query: keywords, $cashtags, #hashtags, from:user, since:YYYY-MM-DD, lang:en, min_faves:50, -filter:replies ... |
| type | string | – | Latest (newest first) or Top. |
No output schema declared.
No examples provided.
test_rule Test a trading rule on the archive ~377
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection. |
| coin | string | – | Base asset, e.g. BTC, ETH, SOL (no USDT suffix). |
| rules | string | yes | Up to 3 rules joined by commas or 'and', each metric>threshold or metric<threshold. Metrics: price_chg_1h_pct, price_chg_24h_pct, oi_chg_1h_pct, oi_chg_24h_pct, funding_apr_pct, long_pct, liq_1h_usd,… |
No output schema declared.
No examples provided.
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'
What is the LiquidVision — Crypto Derivatives Data MCP server?
LiquidVision — Crypto Derivatives Data is an MCP server listed in the public MCP registry as app.liquidvision/derivatives. Crypto derivatives data and answers for AI agents: smart money, liquidations, funding, 13 venues. This page covers its hosted endpoint (https://liquidvision.app/mcp).
Is the LiquidVision — Crypto Derivatives Data MCP server safe to use?
LiquidVision — Crypto Derivatives Data scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LiquidVision — Crypto Derivatives Data MCP server expose?
LiquidVision — Crypto Derivatives Data exposes 69 tools: list_markets, get_accuracy, get_funding_rates, get_microstructure, get_positioning_regime, and 64 more. Their descriptions and schemas cost roughly 13,895 tokens of context every time the server is loaded.
Does the LiquidVision — Crypto Derivatives Data MCP server require authentication?
No. We connected to LiquidVision — Crypto Derivatives Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LiquidVision — Crypto Derivatives Data MCP server still maintained?
LiquidVision — Crypto Derivatives Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the LiquidVision — Crypto Derivatives Data MCP server?
VerifyMCP ran 13 checks on LiquidVision — Crypto Derivatives Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.