mcp-registry/app.liquidvision/derivatives · v1.30.0
As of 2026-10-25 08:40 UTC, the Liquidvision Derivatives MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 7 minutes.
Exchange-exact crypto derivatives data for AI agents: OI, funding, liquidations, 13 venues, 42 tools
Claude Code
claude mcp add --transport http liquidvision-derivatives-mcp-server https://liquidvision.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"liquidvision-derivatives-mcp-server": {
"type": "http",
"url": "https://liquidvision.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
42 of 42 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
42 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
80 parameter(s) across 31 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 31 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.liquidvision%2Fderivatives/fixes
{
"name": "create_alert",
"description": "Subscribe an HTTPS URL to push alerts instead of polling (Pro: 3, Bot: 20 subscriptions).\n type='cascade': a liquidation cascade just ended, over min_usd and x_normal times the coin's\n normal minute. type='hl_near_liq': a Hyperliquid whale position over min_usd within\n max_dist_pct of its liquidation price. type='cluster_sweep': price reached one of the 10\n largest modeled liquidation-map clusters (size over min_usd; no symbol = BTC, ETH, SOL), sent\n 3 min later with modeled vs ac",
"inputSchema": {
"type": "object",
"title": "create_alertArguments",
"required": [
"type",
"url"
],
"properties": {
"url": {
"type": "string",
"title": "Url"
},
"type": {
"type": "string",
"title": "Type"
},
"symbol": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Symbol",
"default": null
},
"api_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Api Key",
"default": null
},
"min_usd": {
"type": "number",
"title": "Min Usd",
"default": 1000000
},
"x_normal": {
"type": "number",
"title": "X Normal",
"default": 8
},
"max_dist_pct": {
"type": "number",
"title": "Max Dist Pct",
"default": 3
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_alert",
"description": "Permanently delete one webhook alert subscription. DESTRUCTIVE and not reversible:\n deliveries to its URL stop at once and its signing secret is discarded (create_alert\n issues a new one). Only a subscription owned by the caller's API key can be deleted;\n an id belonging to another key returns {\"deleted\": false} and changes nothing. id: the\n number returned by create_alert or list_alerts. Needs a Pro or Bot key (X-API-Key header\n of the MCP connection, or api_key).",
"inputSchema": {
"type": "object",
"title": "delete_alertArguments",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"title": "Id"
},
"api_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Api Key",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "explain_market",
"description": "AI risk-intelligence answer: ask e.g. 'Why did BTC drop 4%?' and get a\n concise grounded explanation (liquidation cascades, funding extremes, where\n the positions sit, next risk zone) computed from live derivatives data\n across 13 venues (CEXs, Hyperliquid and GMX).",
"inputSchema": {
"type": "object",
"title": "explain_marketArguments",
"required": [
"question"
],
"properties": {
"symbol": {
"type": "string",
"title": "Symbol",
"default": "BTCUSDT"
},
"question": {
"type": "string",
"title": "Question"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.liquidvision/derivatives"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.liquidvision/derivatives"}) over MCP.
get_history ~329 tokenscreate_alert ~305 tokensget_hl_whales ~255 tokensget_liquidations ~249 tokensget_lighter_whales ~247 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.liquidvision%2Fderivatives?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.liquidvision%2Fderivatives?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.liquidvision%2Fderivatives.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.liquidvision%2Fderivatives.svg :target: https://glimind.com/server/mcp-registry%2Fapp.liquidvision%2Fderivatives?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cef9ff2e52efc209…, first seen 2026-10-22, included at leaf 45102 of 64,924. Version history · verify what your client received.
Compare: most reliable other servers · most reliable ml servers · most reliable data servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 08:40 UTC, the Liquidvision Derivatives MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 7 minutes.
Liquidvision Derivatives MCP server advertises 42 tools, including create_alert, delete_alert, explain_market, get_accuracy, get_api_key.
Point your MCP client at this streamable-http endpoint: https://liquidvision.app/mcp
Glimind scanned all 42 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.