Ironflowsh MCP

What ironflowsh/mcp does

ironflowsh/mcp MCP server exposes read-only Hyperliquid data through the Model Context Protocol. It covers native perpetual markets, HIP-3 builder markets, HIP-4 outcome markets, and spot markets. The server provides 36 tools for market data, wallet analytics, trading signals, cohorts, service status, and historical queries.

The data includes prices, recent trades, candles, funding, open interest, fills, liquidations, vault activity, market listings, and market snapshots. Wallet-focused tools return account state, summaries, PnL series, funding, maker-taker information, and ledger records. Other tools identify top traders, market leaders, early movers, trader profiles, wallet labels, and wallet behavior.

For broader analysis, describe_data documents queryable tables and example queries, while run_query executes one read-only ClickHouse SELECT. Queryable data includes fills, wallet totals, behavior labels, funding, mark and oracle prices, open interest, liquidations, builder-code fills, transfers, and vault flows. This makes ironflowsh/mcp MCP server a fit for the 💰 Finance & Fintech category, especially for market research and account analysis.

How it works

The hosted deployment is available at https://mcp.ironflow.sh/mcp using Streamable HTTP. A client can connect directly to that URL, optionally sending an Authorization: Bearer header with an Ironflow key. Clients that cannot add headers can place the key in the URL as a key query parameter.

A local deployment runs through the @ironflowsh/mcp npm package and requires Node.js 18 or newer. The package connects to the Ironflow API, whose default base URL is https://api.ironflow.sh. An HTTP variant can also be started locally with ironflow-mcp-http; it listens on port 8080 by default and serves the /mcp path.

Setup and configuration

For a hosted connection, add the Streamable HTTP URL to an MCP client. The README provides configurations for Claude Desktop, Claude Code, and Cursor. For local use, run:

npx -y @ironflowsh/mcp

Set IRONFLOW_API_KEY when using a key. The key is optional: unauthenticated access allows 10 requests per minute and 24 hours of history, while a free key increases the allowance to 60 requests per minute and 30 days. The fill history itself covers a rolling 12 months.

IRONFLOW_API_URL changes the API base URL. The self-hosted HTTP process accepts PORT; MCP_LOG_SALT controls the salt used for hashing caller identifiers in access logs. The hosted service records request method, tool arguments, client name, status, and a salted caller-IP hash, but not raw IP addresses or API keys.

Tools and capabilities

• Query market prices, trades, candles, funding, open interest, fills, liquidations, mark prices, and vault operations.
• Inspect wallet state, summaries, PnL, funding, maker-taker activity, ledgers, and behavior labels.
• Find top traders, market leaders, early movers, trader profiles, market leaders, and wallet cohorts.
• Run read-only SQL against documented Hyperliquid data tables.
• Review service status, current metrics, and status history.

Some market analytics, including liquidation levels and the vault leaderboard, require a Builder or Enterprise key.

Limitations and notes

ironflowsh/mcp MCP server is read-only. It cannot place orders, change account state, or manage orders. The toolset has no order-book, order-status, or streaming capability. Keyless SQL and data queries are limited to the most recent 24 hours; a free key extends query visibility to 30 days. Access limits and history windows therefore matter when designing automated research workflows.