Skip to content

Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server

app.hyperperps/liquidation-heatmaphyperperps.appstreamable-httpv1.1.0Scanned

Live Hyperliquid liquidation heatmap: liquidation clusters, stop pools, TP walls, crowd positioning.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server can do

The Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server is published by hyperperps.app, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (get_liquidation_heatmap).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

2 tools

Only reads 2Show 2 read-only tools
  • get_heatmap_field_definitionsDefinitions of every field in the liquidation heatmap: conventions, cluster shape, field glossary, query options, supported markets and refresh cadence.No findings

    Why it is in this group

    • The name "get_heatmap_field_definitions" says "get": a word for reading.
    Description, as the server wrote it
    Definitions of every field in the liquidation heatmap: conventions, cluster shape, field glossary, query options, supported markets and refresh cadence. Generated from the live API documentation.

    Annotations the server declares

    • title: Heatmap field definitions
    • readOnlyHint: true
    • openWorldHint: false
  • get_liquidation_heatmapLive liquidation clusters (long and short walls with prices, notional, distance from spot), stop-loss and take-profit pools, and positioning stats for a Hyperliquid perp, computed …Reads text others writeNo findings

    Why it is in this group

    • The name "get_liquidation_heatmap" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Live liquidation clusters (long and short walls with prices, notional, distance from spot), stop-loss and take-profit pools, and positioning stats for a Hyperliquid perp, computed from ~100k tracked wallets and refreshed every ~15 s. Default view: walls within 5% of spot, biggest per side; range/levels widen it to the full ladder.

    Annotations the server declares

    • title: Hyperliquid liquidation heatmap
    • readOnlyHint: true
    • openWorldHint: true

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

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 liquidation-heatmap https://hyperperps.app/mcp
claude mcp add --transport http liquidation-heatmap https://hyperperps.app/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": [
      "mcp__liquidation-heatmap__get_liquidation_heatmap",
      "mcp__liquidation-heatmap__get_heatmap_field_definitions"
    ],
    "ask": [],
    "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 liquidation-heatmap. Review it before you use it.

Capability tags behind 1 rule
  • mcp__liquidation-heatmap__get_liquidation_heatmap untrusted-input

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/app.hyperperps/liquidation-heatmap/verify?hash=0aed90d1630b529c10b0ae1bbb23d956871c3e3fde2a2d9984ce2ed776d526da" | jq -e '.changed == false'

Pinned hash 0aed90d1630b, from Nov 20, 2026, 21:18 UTC.

Watch

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

https://radar.anlyon.com/servers/app.hyperperps/liquidation-heatmap/changes.xml

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

Badge

Anlyon Radar badge for app.hyperperps/liquidation-heatmap
[![Anlyon Radar](https://radar.anlyon.com/badge/app.hyperperps/liquidation-heatmap.svg)](https://radar.anlyon.com/servers/app.hyperperps/liquidation-heatmap)

Source: MCP Registry · repository. Synced Nov 20, 2026, 21:17 UTC.

Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server: questions and answers

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

Is the Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server delete data?

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

Can the Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps 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 Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server have?

2 tools: 2 read. get_liquidation_heatmap and get_heatmap_field_definitions.

Does the Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server send data to outside services?

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

Has the Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.