The MCP serverfor agents

The archive, as tools an agent can call.

Ask a question. Over MCP (Model Context Protocol), the assistant picks the tools, calls them and returns figures with the calls behind them. A tool call spends the credits of the API requests it makes, one or more, from your Data API balance.

Get a keyRead the docs
What it returnsone question

One question, two calls, a real answer.

Every figure below was returned by the API. Run the two calls to check; the figures move.

an assistant configured with your API keycaptured 2026-08-07 10:08 UTC
  1. You

    Across every round trip on Hyperliquid, who is actually making money, and what does it cost them to trade?

  2. hd_completed_trades_search{ view: "summary" }412 ms
  3. hd_analytics_priority_fees{ view: "stats", hours: 24 }462 ms
  4. Assistant

    Across 95,909,031 reconstructed round trips since 2025-08-18, realised PnL nets to minus $54.97M while the same population paid $691.4M in fees on $4.42 trillion of volume. The venue does not compute any of this; each of these trades was rebuilt from its fills.

    round trips reconstructed
    95,909,031
    net realised PnL
    -$54,974,172
    fees paid
    $691,404,675
    volume closed
    $4.42T
    history since
    2025-08-18

    The direction split is the interesting part. Longs lost $2.48B and shorts made $2.42B over the same window, so the two sides very nearly cancel: the net is about 2% of either leg. Per coin, BTC is the only one of the top five in the black, and fees alone are more than twelve times the net loss.

    coinround tripsrealised PnLvolume closed
    BTC15,534,243+$46.54M$1.70T
    ETH6,495,392-$23.31M$856.20B
    HYPE5,567,718-$95.41M$230.86B
    xyz:XYZ1005,069,868-$6.57M$121.55B
    SOL4,588,705-$30.50M$259.78B

    On the cost side, over the last 24 hours 815,001 fills paid a priority tip, spending 1,108.46 HYPE between them, and only 235 wallets paid anything at all. The average tip was 0.0014 HYPE against a single largest tip of 10.14.

Wiring it uphosted, then local

One URL and your key. The client lists the tools.

The server is hosted, so there is nothing to install: put the endpoint and an API key in the client configuration and restart it. Every tool needs the key, and a tool call spends the credits of the API requests it makes, which can be more than one. When the Free plan runs out, the 429 response carries the plan, what is left and an upgrade_url the assistant can show you. Client guide

claude / cursor mcp config
{
  "mcpServers": {
    "hypedexer": {
      "url": "https://mcp.hypedexer.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
429 Too Many Requests
{
  "error": "credit_limit_reached",
  "message": "Monthly credit allotment for the Free plan is spent.",
  "plan": "free",
  "included_credits": 5000,
  "remaining_credits": 0,
  "overage_per_100k_usd": null,
  "upgrade_url": "https://hypedexer.com/pricing"
}

Or run it locally

The same server is on npm and runs over stdio, so the key never leaves your machine. The version is pinned to 2.1.0, the one the registry serves. With no key it enables the eight keyless Hyperliquid tools and nothing from the archive. A key restricted to the hosted server does not work locally.

local, with a key
{
  "mcpServers": {
    "hypedexer": {
      "command": "npx",
      "args": [
        "-y",
        "@hypedexer/[email protected]"
      ],
      "env": {
        "HYPEDEXER_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
local, no key: public tools only
{
  "mcpServers": {
    "hypedexer": {
      "command": "npx",
      "args": [
        "-y",
        "@hypedexer/[email protected]"
      ],
      "env": {
        "HYPEDEXER_MCP_TOOLS": "public"
      }
    }
  }
}

Start free: 5,000 credits a month, no card.

One key for the hosted server, the npm package and the Data API. Tool calls spend the same credits.

Get a keySet up a client