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

io.github.ironflowsh/mcp

io.github.ironflowsh/mcp 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.

We read its 36 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

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

Claude Code
claude mcp add --transport http mcp https://mcp.ironflow.sh/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.ironflow.sh/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"mcp","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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

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

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

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

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. What we found across the registry.

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

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26