Home / MCP registry index / io.github.ironflowsh/hyperliquid

Ironflow: Hyperliquid data

io.github.ironflowsh/hyperliquid in the official MCP registry. Endpoint https://mcp.ironflow.sh/mcp. Source: github.com/ironflowsh/mcp.

The registry describes it as: Read-only Hyperliquid data for AI agents: fills, candles, funding, liquidations, wallet analytics.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http hyperliquid https://mcp.ironflow.sh/mcp

{
  "mcpServers": {
    "hyperliquid": {
      "url": "https://mcp.ironflow.sh/mcp"
    }
  }
}

code --add-mcp '{"name":"hyperliquid","type":"http","url":"https://mcp.ironflow.sh/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

describe_data run_query get_wallet_behavior get_price get_recent_trades get_candles get_funding_rates get_open_interest get_liquidations get_liquidation_summary get_fills get_mark_prices get_vault_operations get_liquidation_levels get_vault_leaderboard get_funding_stats get_user_state get_user_funding get_user_maker_taker get_user_ledger get_pnl_leaderboard get_market_top_wallets get_markets_snapshot get_user_summary get_wallet_labels get_user_pnl_series get_top_traders get_market_leaders get_early_movers get_trader_profile list_cohorts get_cohort_addresses get_status get_status_metrics get_status_history list_markets

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-03): b7ec864997361de3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ironflowsh-hyperliquid/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ironflowsh-hyperliquid)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Analytics and SEO MCP servers