Buildix runs a public Model Context Protocol server so an AI assistant can read Hyperliquid orderflow analytics while you talk to it: buying and selling pressure, liquidation levels, what large accounts are positioned for, funding across the market and a market screener. Paste one URL into your assistant. There is no account to create and no key to manage, and every tool is read-only: nothing on this server places an order, moves funds or changes data.
https://www.buildix.trade/api/mcp/public
Every tool accepts detail: "brief" (the default) returns labels and the key numbers in a few hundred tokens, "full" adds the underlying values, the age of each source and a short note on method. Every answer carries the time of the market data it was computed from and ends with the line Informational orderflow analytics, not financial advice.
get_orderflow_snapshotOrderflow snapshotREAD-ONLYReturns a compact orderflow reading for one Hyperliquid perpetual market, computed by Buildix from recent fills, the order book and market context: direction of recent buy and sell flow (CVD), order book imbalance (OBI) and flow toxicity (VPIN) as categories, funding rate and open interest. Use it when the user asks about buying or selling pressure, order book balance, flow toxicity, funding or open interest for one coin or HIP-3 market.
input: symbol (e.g. "BTC", "kPEPE", "xyz:NVDA"), detail?: "brief" | "full"
try: "Is there more buying or selling pressure on SOL right now?"
get_liquidation_levelsLiquidation levelsREAD-ONLYReturns the main liquidation levels above and below the current price for one Hyperliquid perpetual market, estimated from the whole open interest with an assumed leverage mix: price, distance and size of each cluster, and in detail "full" a wider range and the amount liquidated on moves of 5, 10 and 15%. A model, not a record of positions. Use it when the user asks where liquidations sit around the price or how much could be liquidated on a move of a given size.
input: symbol, detail?: "brief" | "full"
try: "Where are the liquidation levels for BTC on Hyperliquid?"
get_whale_positioningWhale positioningREAD-ONLYReturns the aggregated long versus short positioning of the large Hyperliquid accounts Buildix tracks for one market: long and short notional, the number of accounts on each side and the resulting bias. No account addresses are returned. Use it when the user asks whether whales or large traders are long or short a coin.
input: symbol, detail?: "brief" | "full"
try: "Are whales long or short ETH right now?"
get_funding_ratesFunding ratesREAD-ONLYReturns Hyperliquid perpetual funding rates ranked from highest to most negative, annualized, with a market-wide summary (median, open-interest-weighted average, count of positive and negative markets). Markets under $1M of open interest are left out of the rankings. Use it when the user asks which markets pay the highest or most negative funding, or how funding looks across Hyperliquid.
input: detail?: "brief" | "full"
try: "Which Hyperliquid markets have the highest funding?"
get_market_screenerMarket screenerREAD-ONLYReturns a snapshot of the Hyperliquid perpetual market: number of markets, total open interest and 24h volume, breadth, open-interest-weighted funding, the top markets by 24h volume, price change, open interest or funding, and the largest 24h gainers and losers. Use it for market overviews, top movers or the most active markets.
input: detail?: "brief" | "full", sort_by?: "volume" | "change" | "open_interest" | "funding"
try: "Give me an overview of the Hyperliquid market today."
Menu names move between app versions; the steps below are the current ones. Wherever the assistant asks for an authentication method, choose none: this server does not use one.
Custom connectors work on every Claude plan, Free included.
Developer mode is offered on paid ChatGPT plans, on the web.
Adding a connector needs the administrator role, which an individual account owner has.
Custom connectors are a paid Perplexity feature.
Claude Code registers the server with one command:
claude mcp add --transport http buildix https://www.buildix.trade/api/mcp/public
Cursor, VS Code, Windsurf and most other clients take a JSON entry like this one (the file and the outer key differ by client):
{
"mcpServers": {
"buildix": {
"type": "http",
"url": "https://www.buildix.trade/api/mcp/public"
}
}
}To check the server by hand, or to try it in the MCP Inspector, call a tool with curl:
curl -X POST https://www.buildix.trade/api/mcp/public \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_funding_rates","arguments":{}}}'The answers are analytics Buildix computes from Hyperliquid market data that its own pipeline collects. The server reads those results; it does not query Hyperliquid while answering you, which is why an answer arrives in well under a second and why every answer states the time of the data it used.
All Hyperliquid perpetuals on the default dex, plus HIP-3 builder markets such as xyz:NVDA.
CVD direction reads the last captured fills: a sample of the tape, so it shows direction, not total traded volume. OBI uses the top 10 levels on each side and is reported as bid heavy, balanced or ask heavy.
Computed for the most active default-dex markets and reported as a level: low, normal, elevated or high. Other markets report it as unavailable.
Aggregated only: the server never returns an address, a label or a single position.
Used for the 24h funding average in detail="full".
Liquidation levels are an estimate over the whole open interest of the market, spread over an assumed mix of leverage: aggregated clusters, not a record of individual positions.
Full policy: Privacy Policy.
The public server has one shared daily capacity of 20,000 tool calls across all users, reset at 00:00 UTC. There is no per-address limit, because AI assistants call from shared networks. An identical question is answered from a short cache (30 seconds to 2 minutes depending on how often the underlying data changes), so the figures you see are never older than the data they come from plus that window.
Those live on the keyed server documented at /mcp and on the REST API at /developers. They are separate from this public server and need a Buildix API key.
Use the Hyperliquid ticker: BTC, ETH, SOL. Contracts quoted per thousand units carry a lowercase k (kPEPE, kBONK); PEPE also resolves to kPEPE. HIP-3 markets are written dex:COIN, for example xyz:NVDA or xyz:GOLD.
The server only answers from data Buildix has collected in the last few minutes and never fills a gap with an older figure. Retry after a few minutes. A HIP-3 dex that Buildix does not currently refresh stays unavailable.
That source has no recent data for this market, for example no captured fills on a quiet market or no VPIN outside the most active markets. The other fields are current.
Capacity is shared by everyone who uses the public server and resets at 00:00 UTC. A pause is a maintenance switch. Neither depends on anything in your account or your prompt.
Those live on the keyed server documented at /mcp and on the REST API at /developers. They are separate from this public server and need a Buildix API key.
Disclaimer. Informational orderflow analytics, not financial advice. The tools describe market conditions; they do not recommend trades, and figures can be estimates (each answer says which). Trading perpetual futures carries a high risk of loss. Read the risk disclosure.
Support and security reports: hello@buildix.trade