LiquidVision — Crypto Derivatives Data
v1.4.0Crypto derivatives data and answers for AI agents: smart money, liquidations, funding, 13 venues
Endpoint health
online- Last checked
- 11/20/2026, 5:17:49 AM
- Latency
- 124 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.liquidvision%2Fderivatives
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.liquidvision/derivatives": {
"url": "https://liquidvision.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Ask a derivatives question
ask
ONE CALL instead of five: ask in plain words ('where is leverage stacked on BTC', 'why did ETH drop', 'is SOL funding crowded', 'biggest whales near liquidation') and get `answer`: short statements with the numbers in them, `facts`: the same numbers as JSON, `sources`: which endpoints were read and how old their data is, `caveats`. The question is read for its topics (liquidations, funding, open interest, whales, levels, sentiment; English or Russian) and only those endpoints are fetched. No model involved: facts, not opinion, so you do the judging. Free, no key. For the base rate of the current state call get_precedents; for the full brief of a coin call get_market_brief.
Schema valid · SHA-256 fd2268ef7237…
View input schema
{ "type": "object", "properties": { "question": { "description": "The question in plain words, English or Russian.", "title": "Question", "type": "string" }, "coin": { "default": "BTC", "description": "Base asset, e.g. BTC, ETH, SOL (no USDT suffix).", "title": "Coin", "type": "string" } }, "required": [ "question" ], "title": "askArguments" }Signed data snapshot
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). 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.
Connections
streamable-http
https://liquidvision.app/mcp