LiqSonar
REMOTE · LIQSONAR.COM
Crypto futures order-flow signals, pumps, liquidation levels, order book walls and verdicts
Available components
Last scanned (2 hours ago)
Scores higher than 28% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Crypto and Web3
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 31 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- 30 Oct 26 38
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 5 Nov 2026 · Probed https://liqsonar.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of liqsonar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| liqsonar.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liqsonar.com/mcp | Unreachable | ||
| http (plaintext) | http://liqsonar.com/mcp | HTTPS enforced |
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_liquidation_levels Liquidation levels ~109
Estimated USD of long and short liquidations per price bin within ±12% of the current price for one pair, built from open interest changes across exchanges and typical leverage. Long liquidations sit below the price, short ones above. Only bins with liquidity are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days of open interest to build the levels from |
| symbol | string | yes | Binance USDT futures symbol, e.g. BTCUSDT (a bare coin like BTC also works) |
No output schema declared.
No examples provided.
get_order_book_walls Order book walls ~172
Large resting limit orders (walls) in the latest futures order book snapshot, largest first: exchange, side (bid = buy wall below the price, ask = sell wall above), price, size in USD, distance from the mid price in %, how long the wall has stood in seconds, 24h price change and how many minutes of average traded volume it would take to eat the wall.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of walls |
| max_distance_pct | number | – | Maximum distance from the mid price in % |
| min_usd | number | – | Minimum wall size in USD |
| side | string | – | Optional: bid or ask; omit for both |
| symbol | string | – | Optional Binance USDT futures symbol, e.g. SOLUSDT; omit for every pair |
No output schema declared.
No examples provided.
get_pumps Pumps and dumps ~98
Detected pump and dump events across Binance futures, newest first: start, peak and end prices and times, maximum move, the dump that followed, volume surge, open interest change, liquidation volume during the pump and the dump, and an AI summary when one exists.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back window in days |
| language | string | – | Language of the AI summaries |
| limit | integer | – | Maximum number of events |
No output schema declared.
No examples provided.
get_signals Order-flow signals ~122
Recent order-flow signals on Binance futures, newest first: CVD divergences, absorption, buy/sell pressure, CVD flips, funding extremes and volume spikes, with severity, price change, CVD and a short English detail. Thresholds are still being calibrated, so treat a signal as context rather than a call.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window in hours |
| limit | integer | – | Maximum number of signals |
| symbol | string | – | Optional Binance USDT futures symbol, e.g. SOLUSDT; omit for every pair |
No output schema declared.
No examples provided.
get_verdict Manipulation or organic verdict ~122
For one pair, whether the price moves with or against the order flow (CVD) on Binance, Bybit, OKX and Bitget over the last hours: healthy_rally, healthy_drop, bearish_divergence (price up while sellers dominate), bullish_divergence (price down while buyers accumulate) or neutral, with a short English detail per exchange.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window in hours |
| symbol | string | yes | Binance USDT futures symbol, e.g. BTCUSDT (a bare coin like BTC also works) |
No output schema declared.
No examples provided.
How do I install the LiqSonar MCP server?
LiqSonar is a hosted endpoint at https://liqsonar.com/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 · liqsonar.com
claude mcp add --transport http com-liqsonar-liqsonar 'https://liqsonar.com/mcp'
What is the LiqSonar MCP server?
LiqSonar is an MCP server listed in the public MCP registry as com.liqsonar/liqsonar. Crypto futures order-flow signals, pumps, liquidation levels, order book walls and verdicts. This page covers its hosted endpoint (https://liqsonar.com/mcp).
Is the LiqSonar MCP server safe to use?
LiqSonar scores 38 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 LiqSonar MCP server expose?
LiqSonar exposes 5 tools: get_signals, get_pumps, get_liquidation_levels, get_order_book_walls, get_verdict. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.
Does the LiqSonar MCP server require authentication?
Its publisher declares no required credentials for LiqSonar. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LiqSonar MCP server still maintained?
LiqSonar is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.