mmflow MCP server

MCP server

Connect Claude — or any MCP client — straight to mmflow's Hyperliquid analytics. The server exposes 17 read-only tools over the Model Context Protocol's Streamable HTTP transport. No API key, no install — just a URL.

← REST reference OpenAPI spec

Connect

streamable http

Claude Code (CLI)

claude mcp add --transport http mmflow https://mmflow.ai/api/mcp/mcp

Claude Desktop / other MCP clients

Add a custom connector pointing at the Streamable HTTP URL.

https://mmflow.ai/api/mcp/mcp

Endpoint: https://mmflow.ai/api/mcp/mcp. The server is read-only and unauthenticated — it inherits the public v1 API's per-IP rate limit. Inspect it locally with npx @modelcontextprotocol/inspector.

Tools

17 read-only

perps_open_interestCross-venue open interest per coin × venue.

perps_oi_historyHyperliquid OI time series for one coin.

perps_fundingCross-venue funding rates per coin × venue.

perps_funding_historyCross-venue funding-rate time series for one coin.

perps_liquidations24h cross-venue liquidation totals per coin.

perps_positioningNet long/short positioning across Binance + OKX.

perps_whalesRecent large Hyperliquid prints over a notional threshold.

options_chainDeribit option chain for an underlying.

options_gexDealer gamma exposure — call wall, put wall, gamma flip.

options_skewIV smile + ATM term structure per expiry.

markets_spotCross-venue spot ticker (Coinbase, Binance, Bitfinex, Kraken).

onchain_etf_flowsSpot ETF daily net flows (BTC / ETH).

onchain_treasuriesPublic-company crypto treasury holdings.

onchain_valuationBTC on-chain valuation — MVRV-Z, NUPL, Puell, Reserve Risk.

polymarket_eventsTop Polymarket events ranked by liquidity.

polymarket_orderbookPolymarket CLOB orderbook for one token.

list_capabilitiesThe full mmflow OpenAPI document.

How it works

Each tool is a thin proxy over one mmflow /api/v1 endpoint and returns the same { data, meta } JSON. An agent can compose calls — e.g. read options_gex then perps_funding to reason about a squeeze. Live streaming tools and keyed quota are on the roadmap.

Prefer plain HTTP? REST reference