MCP server

AI agents

The Buildix MCP server exposes live Hyperliquid orderflow analytics as Model Context Protocol tools. Plug it into Claude, ChatGPT, Cursor, or any MCP-compatible agent so the model can read the screener, fetch deep-view data on a pair, get current signals, inspect smart money positioning, pull the liquidation map or read the CVD time series on demand. Seven read-only tools. Streamable HTTP transport. Stateless. Each tool requires the same plan as its REST equivalent, so an API key belongs in every request.

Endpoint

https://www.buildix.trade/api/mcp

Streamable HTTP only (POST). SSE is disabled — no Redis, fully stateless.

Connect from Claude Code

Paste this into your terminal. Replace bx_... with a key from your dashboard. Without a key only the two open tools answer, and every gated tool replies with the plan it needs.

claude mcp add --transport http buildix https://www.buildix.trade/api/mcp \
  --header "Authorization: Bearer bx_..."

Connect from Cursor / Claude Desktop

Add this to your client config (e.g. mcp.json).

{
  "mcpServers": {
    "buildix": {
      "url": "https://www.buildix.trade/api/mcp",
      "headers": {
        "Authorization": "Bearer bx_..."
      }
    }
  }
}

Clients that cannot send a custom header

Some connector UIs offer only OAuth, Mixed or No Authentication and give you no field for a static header — ChatGPT Developer Mode custom connectors are the common case. There, put the key in the endpoint URL instead:

https://www.buildix.trade/api/mcp?api_key=bx_...

Same key, same tiers, same daily quota. Headers are read first and the query parameter is only the fallback, so if you can send Authorization or x-api-key, that form stays the recommended one.

A key placed in a URL can end up in your own client's logs, in browser history and in any proxy between you and us, so use this only where a header is impossible, and give that connector a key of its own rather than reusing one. If a key is ever exposed, revoke it from Dashboard > API Keys and generate a new one — revocation takes effect on the next request.

Quick test (curl)

MCP is JSON-RPC over POST. This call lists the registered tools.

curl -X POST https://www.buildix.trade/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

get_screenerOpeninput: none

All Hyperliquid pairs with price, 24h change, volume, OI, funding.

get_pairOpeninput: symbol: string (e.g. "BTC")

Detailed market data for one pair: mark, oracle, change, volume, OI, funding, max leverage.

get_signalsTraderinput: none

Active V5+V6 orderflow signals: direction, score, confidence (0-100), regime, reasons.

get_smart_moneyProinput: none

Top whale wallets, their open positions, aggregated per-coin long/short bias.

get_liquidation_mapWhaleinput: symbol: string, price_range_pct?: number (1-20), scenarios?: number[]

Liquidation clusters + cascade scenarios. HIP-3 markets supported via "<dex>:<COIN>".

get_hip4_edgeWhaleinput: underlying?: string, min_abs_divergence?: number, edge_flag?: enum, limit?: number

HIP-4 outcome markets ranked by model-vs-market divergence, with an edge_score blending divergence and V5 orderflow on the underlying perp.

get_cvdWhaleinput: symbol: string, interval?: "5m" | "15m" | "1h", lookback?: number

CVD as a time series bucketed at 5m / 15m / 1h. Each bucket: buy_usd, sell_usd, delta, running cvd, trade count. The delta is computed on a SAMPLE of the tape (~300 fills per symbol), so use it as a directional measure and for price/CVD divergence, not as absolute traded volume. The payload reports the real coverage_minutes for the symbol.

Authentication & rate limits

Pass a Buildix API key on every MCP request, in either the Authorization: Bearer bx_... or the x-api-key: bx_... header — or, only where a custom header is impossible, as ?api_key=bx_... on the endpoint URL (see above). The key decides two things: which tools answer, and your daily quota. Anonymous calls still reach get_screener and get_pair at free-tier limits; every other tool replies with the plan it requires and how to pass a key, so nothing fails silently inside your agent. Daily quotas are the same as the REST API (Whale: 2,000 requests/day; the dedicated API plan: 50,000). Generate keys from Dashboard > API Keys, compare plans on Pricing.

Questions? hello@buildix.trade