_ registry / mcp streamable-http · checked 28m ago

buildix

https://www.buildix.trade

Registry code: 0d8a1262c6f29a09

api record

Read-only orderflow analytics for Hyperliquid perpetual markets, computed by Buildix. Symbols are Hyperliquid tickers (BTC, ETH, kPEPE); HIP-3 markets are written dex:COIN (xyz:NVDA). Every tool accepts detail="brief" (default) or "full".

endpoint
https://www.buildix.trade/api/mcp/public
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
566ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_funding_rates open 28m ago

    Returns 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "detail": {
      "enum": [
        "brief",
        "full"
      ],
      "type": "string",
      "description": "\"brief\" (default) returns labels and key numbers. \"full\" adds the underlying values, data age and method notes."
    }
  }
}
    arguments 14 lines
  • get_market_screener open 28m ago

    Returns 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "detail": {
      "enum": [
        "brief",
        "full"
      ],
      "type": "string",
      "description": "\"brief\" (default) returns labels and key numbers. \"full\" adds the underlying values, data age and method notes."
    },
    "sort_by": {
      "enum": [
        "volume",
        "change",
        "open_interest",
        "funding"
      ],
      "type": "string",
      "description": "Column for the top list: \"volume\" (default, 24h volume), \"change\" (absolute 24h price change), \"open_interest\" or \"funding\" (absolute rate)."
    }
  }
}
    arguments 24 lines
  • get_orderflow_snapshot unknown never probed

    Returns 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "detail": {
      "enum": [
        "brief",
        "full"
      ],
      "type": "string",
      "description": "\"brief\" (default) returns labels and key numbers. \"full\" adds the underlying values, data age and method notes."
    },
    "symbol": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1,
      "description": "Market ticker such as \"BTC\", \"ETH\", \"SOL\" or \"kPEPE\" (case-insensitive; \"PEPE\" also works), or a HIP-3 market as \"dex:COIN\" such as \"xyz:NVDA\"."
    }
  }
}
    arguments 23 lines
  • get_whale_positioning unknown never probed

    Returns 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "detail": {
      "enum": [
        "brief",
        "full"
      ],
      "type": "string",
      "description": "\"brief\" (default) returns labels and key numbers. \"full\" adds the underlying values, data age and method notes."
    },
    "symbol": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1,
      "description": "Market ticker such as \"BTC\", \"ETH\", \"SOL\" or \"kPEPE\" (case-insensitive; \"PEPE\" also works), or a HIP-3 market as \"dex:COIN\" such as \"xyz:NVDA\"."
    }
  }
}
    arguments 23 lines
  • get_liquidation_levels unknown 28m ago

    Returns 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "detail": {
      "enum": [
        "brief",
        "full"
      ],
      "type": "string",
      "description": "\"brief\" (default) returns labels and key numbers. \"full\" adds the underlying values, data age and method notes."
    },
    "symbol": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1,
      "description": "Market ticker such as \"BTC\", \"ETH\", \"SOL\" or \"kPEPE\" (case-insensitive; \"PEPE\" also works), or a HIP-3 market as \"dex:COIN\" such as \"xyz:NVDA\"."
    }
  }
}
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0d8a1262c6f29a09/badge.svg)](https://brick.blue/agent/0d8a1262c6f29a09)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.