# liquidmap (remote · liquidmap.io)

Crypto order flow: order book walls across 10 exchanges, big trades, footprint, CVD, futures.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://liquidmap.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-21.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 932 tokens (~155/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the liquidmap MCP server?

liquidmap is a hosted endpoint at https://liquidmap.io/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 io-liquidmap-liquidmap 'https://liquidmap.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-liquidmap-liquidmap": {
      "url": "https://liquidmap.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.io-liquidmap-liquidmap]
url = "https://liquidmap.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-liquidmap-liquidmap --url 'https://liquidmap.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-liquidmap-liquidmap:
    url: "https://liquidmap.io/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add io-liquidmap-liquidmap -t streamable-http -u 'https://liquidmap.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-liquidmap-liquidmap": {
      "type": "http",
      "url": "https://liquidmap.io/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-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 71, +40)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-11-16 (score 31)

First indexed and scored.

## MCP tools (6)

### `market_snapshot` (~98 tokens)

Market snapshot

Live snapshot of a crypto pair on liquidmap: price, 24 h change, the largest resting bid and ask walls near the price, big aggressive trades ("bursts") of the last hour, today's CVD (spot and perpetual) and futures funding and open interest. Start here.

Input parameters:

- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

### `order_book_walls` (~189 tokens)

Order book walls

Large resting limit orders ("walls") in the order book within ±range_pct of the price, sorted by size in USD. source "binance" = Binance spot book; "all" = 15 books from 10 exchanges aggregated (Binance, OKX, Bybit, Kraken, Bitfinex, Coinbase, Bitstamp, Gemini, Deribit, Gate).

Input parameters:

- `limit` (integer): Maximum number of walls to return (1 to 50)
- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
- `range_pct` (number): How far from the price to look, in % (0.1 to 30)
- `source` (string): "binance" = Binance spot book only; "all" = 15 books from 10 exchanges aggregated

### `big_trades` (~169 tokens)

Big trades (bursts)

Big aggressive market orders ("bursts": trades of the same side grouped in 5-second windows) of the last N minutes, with side (buy/sell), size, USD value, price and verdict (absorbed = the resting book took it and price did not go through; broke_through = it moved price), plus the share of absorbed bursts.

Input parameters:

- `limit` (integer): Maximum number of bursts to return (1 to 200), largest first
- `min_usd` (number): Only bursts worth at least this many USD
- `minutes` (integer): Look-back window in minutes (1 to 1440)
- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

### `candles` (~159 tokens)

Candles with footprint

OHLC candles with aggressive buy and sell volume, delta and point of control (POC). With footprint=true, each candle also has its price levels with bought and sold volume (at most 20 candles).

Input parameters:

- `footprint` (boolean): Include the price levels of each candle with bought and sold volume (max 20 candles)
- `limit` (integer): Number of most recent candles (1 to 200)
- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
- `timeframe` (string): Candle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w

### `cvd` (~153 tokens)

Cumulative volume delta

Cumulative volume delta (aggressive buys minus sells) for spot and the USDT perpetual, as in the liquidmap terminal: reset every day at 00:00 Madrid time up to 1h, every week (4h), month (1d) or year (1w).

Input parameters:

- `limit` (integer): Number of most recent points (1 to 500)
- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
- `timeframe` (string): Candle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w

### `futures` (~101 tokens)

Futures data

USDT perpetual of the pair on Binance: funding rate and next funding time, mark price, open interest (last 24 h, hourly) and liquidations of the last 24 h summarised: longs and shorts liquidated in USD, the price zones with most liquidations and the 10 largest.

Input parameters:

- `pair` (string, required): Coin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 31

## Common questions

### What is the liquidmap MCP server?

liquidmap is an MCP server listed in the public MCP registry as io.liquidmap/liquidmap. Crypto order flow: order book walls across 10 exchanges, big trades, footprint, CVD, futures. This page covers its hosted endpoint (https://liquidmap.io/mcp).

### Is the liquidmap MCP server safe to use?

liquidmap scores 73 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 liquidmap MCP server expose?

liquidmap exposes 6 tools: market_snapshot, order_book_walls, big_trades, candles, cvd, futures. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.

### Does the liquidmap MCP server require authentication?

Yes. liquidmap asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the liquidmap MCP server still maintained?

liquidmap 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 liquidmap MCP server?

VerifyMCP ran 12 checks on liquidmap, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about liquidmap: HTTPS. 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://liquidmap.io/mcp
- Website: https://liquidmap.io/en/crypto-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/io-liquidmap-liquidmap/liquidmap.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-liquidmap-liquidmap/liquidmap/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-liquidmap-liquidmap/liquidmap.json
- HTML version of this page: https://verifymcp.io/servers/io-liquidmap-liquidmap/liquidmap
