Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

liquidmap

REMOTE · LIQUIDMAP.IO

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

Available components

73 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 +40
    • Transport: unverified → pass ▲ security
    • 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. security
    • MCP protocol: unverified → pass ▲ functional
    • 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 functional
  • 16 Nov 26 31

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://liquidmap.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=liquidmap.io CN=YE1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA384 6449236ef27629c6a1aa7c84512ae207ba9
SANs: *.liquidmap.io, liquidmap.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of liquidmap.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
liquidmap.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://liquidmap.io/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://liquidmap.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://liquidmap.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://liquidmap.io/mcp
Authorisation server https://kzldsarpuqplekwnjtcg.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://liquidmap.io/mcp Verified 200
http (plaintext) http://liquidmap.io/mcp Inconclusive 401
MCP tools · 6 exposed · ~869 tokens

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 →

Tool Tokens
big_trades ~169

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.

NameTypeReqDescription
limitinteger–Maximum number of bursts to return (1 to 200), largest first
min_usdnumber–Only bursts worth at least this many USD
minutesinteger–Look-back window in minutes (1 to 1440)
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

No output schema declared.

No examples provided.

candles ~159

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

NameTypeReqDescription
footprintboolean–Include the price levels of each candle with bought and sold volume (max 20 candles)
limitinteger–Number of most recent candles (1 to 200)
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
timeframestring–Candle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w

No output schema declared.

No examples provided.

cvd ~153

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

NameTypeReqDescription
limitinteger–Number of most recent points (1 to 500)
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
timeframestring–Candle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w

No output schema declared.

No examples provided.

futures ~101

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.

NameTypeReqDescription
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

No output schema declared.

No examples provided.

market_snapshot ~98

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.

NameTypeReqDescription
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

No output schema declared.

No examples provided.

order_book_walls ~189

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

NameTypeReqDescription
limitinteger–Maximum number of walls to return (1 to 50)
pairstringyesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
range_pctnumber–How far from the price to look, in % (0.1 to 30)
sourcestring–"binance" = Binance spot book only; "all" = 15 books from 10 exchanges aggregated

No output schema declared.

No examples provided.

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.

remote · liquidmap.io

# add to Claude Code
claude mcp add --transport http io-liquidmap-liquidmap 'https://liquidmap.io/mcp'
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.