liquidmap MCP server
io.liquidmap/liquidmapliquidmap.iostreamable-httpv1.1.0Scanned
Crypto order flow: order book walls across 10 exchanges, big trades, footprint, CVD, futures.
6 tools: 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the liquidmap MCP server can do
The liquidmap MCP server is published by liquidmap.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: order_book_walls, big_trades, candles, cvd and 1 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
big_tradesBig 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 (absorb…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
candlesOHLC candles with aggressive buy and sell volume, delta and point of control (POC).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
cvdCumulative 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),…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
futuresUSDT 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 sho…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
order_book_wallsLarge resting limit orders ("walls") in the order book within ±range_pct of the price, sorted by size in USD.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
market_snapshotLive 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 CV…No findings
Why it is in this group
- The name "market_snapshot" says "snapshot": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:20 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://liquidmap.io/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://kzldsarpuqplekwnjtcg.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://liquidmap.io/mcp: tools/list returned 6 tools to an anonymous client, including order_book_walls (write), big_trades (write), candles (write), cvd (write), futures (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http liquidmap https://liquidmap.io/mcpclaude mcp add --transport http liquidmap https://liquidmap.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__liquidmap__market_snapshot"
],
"ask": [
"mcp__liquidmap__order_book_walls",
"mcp__liquidmap__big_trades",
"mcp__liquidmap__candles",
"mcp__liquidmap__cvd",
"mcp__liquidmap__futures"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as liquidmap. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.liquidmap/liquidmap/verify?hash=45d0d20ba7c5f57b9ed99f5cbd560f5d3a6c055a00a8966bbd1cbc435cbdac11" | jq -e '.changed == false'Pinned hash 45d0d20ba7c5, from Nov 17, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.liquidmap/liquidmap/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.liquidmap/liquidmap)Source: MCP Registry. Synced Nov 17, 2026, 03:18 UTC.
liquidmap MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the liquidmap MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the liquidmap MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the liquidmap MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the liquidmap MCP server have?
- 6 tools: 5 write, 1 read. order_book_walls, big_trades, candles, cvd, futures and market_snapshot.
Does the liquidmap MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the liquidmap MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the liquidmap MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.