# LiqSonar (remote · liqsonar.com)

Crypto futures order-flow signals, pumps, liquidation levels, order book walls and verdicts

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `liqsonar.com`: 38/100 (this document), [markdown](https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar.md), [page](https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar)

## Channel facts

- Endpoint: `https://liqsonar.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-liqsonar-liqsonar 'https://liqsonar.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-liqsonar-liqsonar": {
      "url": "https://liqsonar.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-liqsonar-liqsonar": {
      "type": "http",
      "url": "https://liqsonar.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-liqsonar-liqsonar]
url = "https://liqsonar.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-liqsonar-liqsonar": {
      "type": "remote",
      "url": "https://liqsonar.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-liqsonar-liqsonar --url 'https://liqsonar.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-liqsonar-liqsonar:
    url: "https://liqsonar.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-liqsonar-liqsonar": {
      "Transport": "http",
      "Url": "https://liqsonar.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-liqsonar-liqsonar -t streamable-http -u 'https://liqsonar.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-liqsonar-liqsonar": {
      "type": "http",
      "url": "https://liqsonar.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 38, 0)

- [security regression] Endpoint reachability: behind authorisation → unreachable
- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] 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.
- [functional] 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.

### 2026-10-31 (score 38, 0)

- [security regression] Endpoint reachability: reachable → behind authorisation

### 2026-10-30 (score 38)

First indexed and scored.

## MCP tools (5)

### `get_signals` (~122 tokens)

Order-flow signals

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.

Input parameters:

- `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

### `get_pumps` (~98 tokens)

Pumps and dumps

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.

Input parameters:

- `days` (integer): Look-back window in days
- `language` (string): Language of the AI summaries
- `limit` (integer): Maximum number of events

### `get_liquidation_levels` (~109 tokens)

Liquidation levels

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.

Input parameters:

- `days` (integer): How many days of open interest to build the levels from
- `symbol` (string, required): Binance USDT futures symbol, e.g. BTCUSDT (a bare coin like BTC also works)

### `get_order_book_walls` (~172 tokens)

Order book walls

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.

Input parameters:

- `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

### `get_verdict` (~122 tokens)

Manipulation or organic verdict

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.

Input parameters:

- `hours` (integer): Look-back window in hours
- `symbol` (string, required): Binance USDT futures symbol, e.g. BTCUSDT (a bare coin like BTC also works)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar#diagnostics

## Score history

- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 38
- 2026-11-02: 38
- 2026-11-01: 38
- 2026-10-31: 38
- 2026-10-30: 38

## Common questions

### 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.

### What did VerifyMCP test on the LiqSonar MCP server?

VerifyMCP ran 3 checks on LiqSonar, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about LiqSonar: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.

## Links

- Remote endpoint: https://liqsonar.com/mcp
- Website: https://liqsonar.com/api-docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar.json
- HTML version of this page: https://verifymcp.io/servers/com-liqsonar-liqsonar/liqsonar