hyperliquid_perp_meta

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_perp_meta for the schema, then POST the same URL with its arguments for the data.

Hyperliquid’s full list of tradeable perpetual contracts and their leverage/precision limits, from Hyperliquid’s own API.

Tool description as the model sees it

Perpetuals universe metadata from Hyperliquid’s public info API ({“type”:“meta”}) — every perp contract Hyperliquid lists (currently 190+), each with its symbol, szDecimals (size precision), maxLeverage, and isDelisted when retired. This is the reference list to resolve a human-asked symbol (“BTC”, “ETH”, “SOL”) to a contract Hyperliquid actually trades before calling hyperliquid_mids, hyperliquid_l2_book, hyperliquid_candles or hyperliquid_funding_history with it — those all take the bare coin symbol shown here (e.g. “BTC”, not “BTC-PERP”). Pass coin to look up one symbol instead of the full list.

Parameters

NameTypeRequiredDescription
coinstringnoOptional — filter to one perp symbol, e.g. “BTC” or “ETH”. Omit to list the whole universe.

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_perp_meta","arguments":{"coin":"BTC"}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('hyperliquid_perp_meta', {
  "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