hyperliquid_asset_context

Pack: hyperliquid · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/hyperliquid_asset_context for the schema, then POST the same URL with its arguments for the data.

A Hyperliquid perp’s live funding rate, open interest, mark/oracle price and 24h volume, from Hyperliquid’s own API.

Tool description as the model sees it

Live perp market context for one contract — current funding rate, open interest, mark price, oracle price, mid price, 24h premium, and 24h notional + base volume — from Hyperliquid’s public info API ({“type”:“metaAndAssetCtxs”}, matched to the requested coin by universe index). This is the single call that answers “what is BTC perp funding right now” or “what is Hyperliquid’s open interest in ETH” — the live numbers next to kalshi_* and polymarket_* for anyone pricing crypto-adjacent prediction markets. For a HISTORY of funding rates rather than the current one, use hyperliquid_funding_history.

Parameters

NameTypeRequiredDescription
coinstringyesPerp symbol, e.g. “BTC”, “ETH”, “SOL”. See hyperliquid_perp_meta for the full list.

Example call

Arguments

{
  "coin": "BTC"
}

curl

curl -X POST https://gateway.pipeworx.io/hyperliquid/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"hyperliquid_asset_context","arguments":{"coin":"BTC"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('hyperliquid_asset_context', {
  "coin": "BTC"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the hyperliquid pack
{
  "mcpServers": {
    "hyperliquid": {
      "url": "https://gateway.pipeworx.io/hyperliquid/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 2, 2026