# Liqwall market data (remote · liqwall.com)

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

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `liqwall.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-liqwall-market-data/liqwall.md), [page](https://verifymcp.io/servers/com-liqwall-market-data/liqwall)

## Channel facts

- Endpoint: `https://liqwall.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-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 739 tokens (~184/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Liqwall market data MCP server?

Liqwall market data is a hosted endpoint at https://liqwall.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-liqwall-market-data 'https://liqwall.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-liqwall-market-data": {
      "url": "https://liqwall.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-liqwall-market-data]
url = "https://liqwall.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-liqwall-market-data:
    url: "https://liqwall.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-liqwall-market-data": {
      "type": "http",
      "url": "https://liqwall.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-07 (score 86, +1)

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

### 2026-11-06 (score 85, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 85, +1)

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

### 2026-11-03 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-28 (score 81, +1)

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

### 2026-10-26 (score 80, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

## MCP tools (4)

### `liquidation_map` (~218 tokens)

Liquidation map

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.

Input parameters:

- `coin` (string, required): Market ticker: BTC, ETH, SOL, HYPE, XRP, DOGE … or a Hyperliquid market such as XAU (gold), CL (crude oil), SP500, NVDA, TSLA. Names such as Bitcoin or Gold and pair names such as BTCUSDT are accepte…

### `liquidations` (~136 tokens)

Liquidations

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.

Input parameters:

- `coin` (string): One of BTC, ETH, SOL, XRP, DOGE, HYPE, BNB; omit it for the whole crypto market

### `derivatives` (~146 tokens)

Funding, open interest, long/short

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.

Input parameters:

- `coin` (string): Coin ticker such as BTC, ETH or SOL; omit it for the ten largest coins

### `fear_greed` (~88 tokens)

Fear and Greed Index

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.

Input parameters:

- `coin` (string): BTC, ETH or SOL; omit it for the whole crypto market

## Diagnostics

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

## Score history

- 2026-11-07: 86
- 2026-11-06: 85
- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 18
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-11: 73
- 2026-10-10: 36

## Common questions

### What is the Liqwall market data MCP server?

Liqwall market data is an MCP server listed in the public MCP registry as com.liqwall/market-data. Crypto liquidation maps, liquidations, funding, open interest: 4 tools without a key, 6 with one. This page covers its hosted endpoint (https://liqwall.com/mcp).

### Is the Liqwall market data MCP server safe to use?

Liqwall market data scores 86 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 Liqwall market data MCP server expose?

Liqwall market data exposes 4 tools: liquidation_map, liquidations, derivatives, fear_greed. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

### Does the Liqwall market data MCP server require authentication?

No. We connected to Liqwall market data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Liqwall market data MCP server still maintained?

Liqwall market data is still listed as active in the MCP registry. We last reached this channel on 7 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 Liqwall market data MCP server?

VerifyMCP ran 13 checks on Liqwall market data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://liqwall.com/mcp
- Website: https://liqwall.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-liqwall-market-data/liqwall.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-liqwall-market-data/liqwall/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-liqwall-market-data/liqwall.json
- HTML version of this page: https://verifymcp.io/servers/com-liqwall-market-data/liqwall