# LiqFlow (remote · liqflow.app)

Hyperliquid liquidation levels, whale positions, liquidations, cohorts and funding. Free.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://liqflow.app/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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1944 tokens (~129/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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 LiqFlow MCP server?

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

### Cursor

```json
{
  "mcpServers": {
    "app-liqflow-liqflow": {
      "url": "https://liqflow.app/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.app-liqflow-liqflow]
url = "https://liqflow.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-liqflow-liqflow --url 'https://liqflow.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-liqflow-liqflow:
    url: "https://liqflow.app/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add app-liqflow-liqflow -t streamable-http -u 'https://liqflow.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-liqflow-liqflow": {
      "type": "http",
      "url": "https://liqflow.app/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-05 (score 77, +1)

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

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

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

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

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

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

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

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

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

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

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

### 2026-10-23 (score 71, +1)

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

### 2026-10-21 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (15)

### `market_overview` (~112 tokens)

Market overview

The whole market in one reading: how many perps lean bullish vs bearish on
liquidation pressure, and the markets leaning hardest each way.

The score compares short-liquidation exposure ABOVE price (forced buys if price
rises) with long-liquidation exposure BELOW it (forced sells if it falls),
weighted by distance. Negative = more fuel below, a bearish pull; positive = the
reverse. Uses 2 API calls.

Input parameters:

- `top` (integer): How many markets to list on each side

### `list_markets` (~90 tokens)

List markets

Market symbols LiqFlow covers, to resolve a name ("solana") to its market
symbol (SOL). `scored` markets also have scores, funding, depth and
volume; the rest have node data only (positions, levels, liquidations). Uses 2
API calls.

Input parameters:

- `query`: Filter by symbol or name, e.g. "pepe" or "bitcoin"

### `open_interest_ranking` (~45 tokens)

Open interest ranking

Hyperliquid markets ranked by open interest (USD), with how many positions
are open in each, from every wallet on the node.

Input parameters:

- `limit` (integer)

### `coin_snapshot` (~106 tokens)

Coin snapshot

Everything about one market right now: live price and 24h change, its
liquidation-pressure score, liquidation exposure each side and how close it
sits, the nearest big cluster, its rank among all markets, and what changed
since the previous snapshot. Start here for any question about one coin. Uses 2
API calls.

Input parameters:

- `coin` (string, required): Hyperliquid market symbol, e.g. BTC, ETH, HYPE, xyz:SKHX

### `liquidation_map` (~170 tokens)

Liquidation map

Where the forced orders sit around the current price for one market, from
every wallet on the node: liquidation prices (longs below = forced sells,
shorts above = forced buys), resting stop-loss / take-profit trigger orders,
and order-book depth, summed into price bands either side of the mark price,
plus the biggest liquidation clusters.

This is the "liquidation heatmap" question: where would a move run into
cascading liquidations, and how much is there. Uses 2 API calls.

Input parameters:

- `bands` (integer): Price bands per side
- `coin` (string, required): Hyperliquid market symbol, e.g. BTC, ETH, HYPE, xyz:SKHX
- `range_pct` (number): How far either side of price to map, in %

### `funding` (~107 tokens)

Funding rates

Perp funding rates. With a coin: the rate on each venue (Hyperliquid, Binance,
Bybit, OKX, Bitget, Gate) normalised to 8 hours, plus the open-interest
weighted aggregate. Without: the markets paying the most positive and most
negative funding right now. Positive = longs pay shorts.

Input parameters:

- `coin`: One market; omit for the most extreme rates across all
- `limit` (integer): Markets per side when no coin is given

### `coin_history` (~102 tokens)

Coin history

A metric's history for one market (with the price where the data has it),
thinned to at most 60 points.

Input parameters:

- `coin` (string, required): Hyperliquid market symbol, e.g. BTC, ETH, HYPE, xyz:SKHX
- `days` (integer)
- `metric` (string): score = liquidation-pressure score; funding = aggregate funding; depth = cross-exchange order-book imbalance; volume = cross-exchange traded volume

### `recent_liquidations` (~104 tokens)

Recent liquidations

Individual Hyperliquid liquidation fills, newest first, straight off the
node: who was liquidated, on which market, how big, at what price. One
liquidation can be several fills sharing an order id.

Input parameters:

- `coin`: One market; omit for all
- `hours` (number)
- `limit` (integer)
- `min_usd`: Only fills at least this large
- `side`: Which side was liquidated

### `liquidation_totals` (~126 tokens)

Liquidation totals

How much was liquidated. Without a coin: every market ranked by liquidated
USD over the window, long vs short. With a coin: long and short liquidations
per time bucket. Windows that the node missed are listed under `gaps` -- those
are missing data, not quiet periods.

Input parameters:

- `coin`: One market, for a time series; omit for a ranking of markets
- `hours` (number)
- `interval`: Bucket size for the time series; chosen from hours if omitted
- `limit` (integer): Markets in the ranking

### `cascades` (~104 tokens)

Liquidation cascades

Past sharp moves (at least `min_move_pct` in one 4-hour step) paired with how
much liquidation exposure sat in their path just before -- the evidence for
whether clusters actually get run.

Input parameters:

- `coin`: Only this market
- `days` (integer)
- `limit` (integer)
- `min_move_pct` (number): Smallest 4-hour move to count
- `sort` (string): Newest first, or most exposure first

### `top_positions` (~98 tokens)

Top positions

The largest open positions on Hyperliquid right now, longs and shorts, read
live from the node: wallet, size, notional, entry, leverage, liquidation price
and how far price is from it, unrealised PnL, and the wallet's size cohort.

Input parameters:

- `coin`: One market; omit for the largest on any market
- `limit` (integer): Per side
- `side`: Omit for both

### `wallet` (~73 tokens)

Wallet positions

One Hyperliquid wallet right now, read live from the node: account value,
PnL, every open position with leverage, liquidation price and how far price is
from it, and its open orders (limits, stops and take-profits).

Input parameters:

- `address` (string, required): Hyperliquid wallet address, 0x...

### `cohort_positioning` (~107 tokens)

Cohort positioning

How different kinds of traders are positioned: wallets grouped by account
size (Micro under $250 up to Whale over $1M) and by all-time PnL (Highly
Unprofitable to Highly Profitable), with each group's long and short notional
and the share that is long. "Are whales and the profitable traders on the
other side of retail?" Uses 2 API calls without a coin.

Input parameters:

- `coin`: One market; omit for all markets combined

### `cohort_top_coins` (~268 tokens)

Cohort top coins

Which coins one trader cohort is most long and most short on, ranked across
every market: "What are the most profitable traders most bullish and most
bearish on?" Each coin has the cohort's long and short notional, net USD,
share long and wallet count, plus the cohort's overall lean across all markets
to compare against. Uses 2 API calls without a side.

Input parameters:

- `cohort` (string): By all-time PnL: Highly Profitable (over $100k) down to Highly Unprofitable (under -$100k). By account size: Whale (over $1M) down to Micro (under $250).
- `limit` (integer): Coins per side
- `min_notional_usd` (number): Skip coins where the cohort holds less than this, long plus short. Without a floor a ratio ranking is all tiny markets where a few wallets are 100% one way
- `rank_by` (string): ratio: by the share of the cohort's notional that is long (conviction). net: by long minus short USD (the biggest bets, which favours BTC and ETH)
- `side`: long: the coins the cohort is most bullish on; short: most bearish on. Omit for both

### `leaderboard` (~51 tokens)

Trader leaderboard

Hyperliquid wallets ranked by all-time PnL or by 30-day volume.

Input parameters:

- `by` (string): All-time PnL, or 30-day traded volume
- `limit` (integer)

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 71
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 69

## Common questions

### What is the LiqFlow MCP server?

LiqFlow is an MCP server listed in the public MCP registry as app.liqflow/liqflow. Hyperliquid liquidation levels, whale positions, liquidations, cohorts and funding. Free. This page covers its hosted endpoint (https://liqflow.app/mcp).

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

LiqFlow scores 77 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 LiqFlow MCP server expose?

LiqFlow exposes 15 tools: market_overview, list_markets, open_interest_ranking, coin_snapshot, liquidation_map, and 10 more. Their descriptions and schemas cost roughly 1,663 tokens of context every time the server is loaded.

### Does the LiqFlow MCP server require authentication?

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

### Is the LiqFlow MCP server still maintained?

LiqFlow is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://liqflow.app/mcp
- Website: https://liqflow.app/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-liqflow-liqflow/liqflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-liqflow-liqflow/liqflow.json
- HTML version of this page: https://verifymcp.io/servers/app-liqflow-liqflow/liqflow