Skip to content

Liqwall market data MCP server

com.liqwall/market-dataliqwall.comstreamable-httpv1.1.0Scanned

Crypto liquidation maps, liquidations, funding, open interest: 4 tools without a key, 6 with one.

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 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

4 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.
Govern this server →

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 Liqwall market data MCP server can do

The Liqwall market data MCP server is published by liqwall.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: liquidation_map, liquidations, derivatives and fear_greed), but cannot delete data. None of its tools 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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 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.

4 tools

Changes things 4Claude Code: ask
  • derivativesFunding rates, open interest and the long/short ratio of perpetual futures, for one coin or for the ten largest coins by open interest.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
    Funding rates, open interest and the long/short ratio of perpetual futures, for one coin or for the ten largest coins by open interest. Use it for questions like "what is the funding rate of ETH", "is open interest growing", "are traders long or short". Returns current values: the Binance funding rate and the average across exchanges per 8 hours, open interest in USD with its change over 24 hours and over the last hour, the share of Binance accounts that are long, the long/short ratio and the share of top traders' positions in longs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Funding, open interest, long/short
  • fear_greedThe crypto Fear and Greed Index: the mood of the market right now on a scale from 0 (extreme fear) to 100 (extreme greed), for the whole market or for BTC, ETH or SOL, with the val…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
    The crypto Fear and Greed Index: the mood of the market right now on a scale from 0 (extreme fear) to 100 (extreme greed), for the whole market or for BTC, ETH or SOL, with the values a day, a week and a month ago.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Fear and Greed Index
  • liquidation_mapWhere forced liquidations stand around the current price of one market: USD amounts of long liquidations below the price and of short liquidations above it, on Hyperliquid (crypto,…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
    Where forced liquidations stand around the current price of one market: USD amounts of long liquidations below the price and of short liquidations above it, on Hyperliquid (crypto, stocks, indices and commodities) and across large exchanges (Binance, OKX, Bybit, Hyperliquid, Gate). Use it for questions like "where are the liquidation levels for BTC", "where do longs get liquidated", "what is the nearest liquidation cluster". Returns one current snapshot: the price, totals within a few percent of the price, the largest levels on each side with their distance from the price, and the URL of the live map. An unknown market returns the list of valid ones.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Liquidation map
  • liquidationsHow much was liquidated: the last 24 hours and the last hour, longs against shorts, for the whole crypto market or for one coin.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
    How much was liquidated: the last 24 hours and the last hour, longs against shorts, for the whole crypto market or for one coin. Use it for questions like "how much was liquidated today", "were longs or shorts liquidated", "which exchange had the most liquidations". Returns the totals, the split by coin (whole market) or by exchange (one coin), the largest liquidations of the last hour, and the URL of the page.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Liquidations

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://liqwall.com/mcp: tools/list returned 4 tools to an anonymous client, including liquidation_map (write), liquidations (write), derivatives (write), fear_greed (write)

    What this check looks for

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.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http market-data https://liqwall.com/mcp
claude mcp add --transport http market-data https://liqwall.com/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__market-data__liquidation_map",
      "mcp__market-data__liquidations",
      "mcp__market-data__derivatives",
      "mcp__market-data__fear_greed"
    ],
    "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 market-data. 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/com.liqwall/market-data/verify?hash=2e8e907ebbf9b382d15ca95c24713c643cc964ae40bd8a510070459b701dce9f" | jq -e '.changed == false'

Pinned hash 2e8e907ebbf9, from Nov 13, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.liqwall/market-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.liqwall/market-data
[![Anlyon Radar](https://radar.anlyon.com/badge/com.liqwall/market-data.svg)](https://radar.anlyon.com/servers/com.liqwall/market-data)

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

Liqwall market data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Liqwall market data MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 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 Liqwall market data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Liqwall market data 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 Liqwall market data MCP server have?

4 tools: 4 write. liquidation_map, liquidations, derivatives and fear_greed.

Does the Liqwall market data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Liqwall market data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Liqwall market data MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.