mcpbeat

HL Portfolio API MCP Server

io.github.Br0ski777/hl-portfolio
answering

HL Portfolio API is answering right now. Last checked 1 min ago. It exposes 4 tools. Last commit 19 Jul 2026.

Hyperliquid account analysis: positions, PnL, fills, orders, funding. x402 pay-per-call.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
26 ms
Response time
average over 24h
1
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add hl-portfolio --transport http https://hl-portfolio.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hl-portfolio": {
      "url": "https://hl-portfolio.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hl-portfolio]
url = "https://hl-portfolio.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "hl-portfolio": {
      "url": "https://hl-portfolio.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hl-portfolio": {
      "url": "https://hl-portfolio.api.klymax402.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hyperliquid
hyperliquid_get_account_state
Use this when you need to retrieve the full portfolio state of a Hyperliquid perpetuals account. Returns the complete clearinghouse state for any wallet address including account-level metrics and per-position details. Returns: 1. accountValue: total account equity in USD 2. totalNtlPos: total notional position size across all open positions 3. totalMarginUsed: margin currently locked in positions 4. withdrawable: available balance that can be withdrawn 5. positions[]: array of open positions, each with coin, size, entryPrice, unrealizedPnl, leverage, liquidationPrice, marginType (cross/isolated) Example output: { accountValue: "125430.50", totalNtlPos: "89200.00", withdrawable: "36230.50", positions: [{ coin: "BTC", size: "1.5", entryPrice: "67500.00", unrealizedPnl: "2340.00", leverage: 5, liquidationPrice: "54200.00", marginType: "cross" }] } Use this BEFORE analyzing a trader's risk exposure, checking margin health, or evaluating portfolio allocation on Hyperliquid. Essential for copy-trading evaluation and risk monitoring. Do NOT use for trade history -- use hyperliquid_get_trade_fills instead. Do NOT use for open orders -- use hyperliquid_get_open_orders instead. Do NOT use for funding payments -- use hyperliquid_get_user_funding instead. Do NOT use for vault performance -- use hyperliquid_get_vault_details instead. Do NOT use for whale tracking -- use hyperliquid_detect_whale_trades instead.
hyperliquid_get_open_orders
Use this when you need to see all pending/open orders for a Hyperliquid perpetuals account. Returns every resting order on the book with full order parameters. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. side: buy (bid) or sell (ask) 3. limitPx: limit price of the order 4. sz: order size 5. orderType: limit, stop-market, stop-limit, take-profit, etc. 6. reduceOnly: whether the order can only reduce an existing position 7. timestamp: when the order was placed 8. oid: unique order ID Example output: { orders: [{ coin: "BTC", side: "buy", limitPx: "65000.00", sz: "0.5", orderType: "limit", reduceOnly: false, oid: 123456 }], count: 3 } Use this to understand a trader's pending strategy, detect limit orders near current price, evaluate order-to-position ratio, or monitor stop-loss placement on Hyperliquid. Do NOT use for executed trades -- use hyperliquid_get_trade_fills instead. Do NOT use for current positions -- use hyperliquid_get_account_state instead. Do NOT use for market-level orderbook -- use hyperliquid_get_market_data instead.
hyperliquid_get_trade_fills
Use this when you need to retrieve recent trade executions (fills) for a Hyperliquid perpetuals account. Returns the most recent trades with full execution details including realized PnL on closed positions. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. side: buy or sell (A = sell/ask, B = buy/bid) 3. size: position size filled 4. price: execution price 5. fee: trading fee paid in USD 6. closedPnl: realized PnL if the trade closed a position (0 if opening) 7. timestamp: execution time in milliseconds 8. hash: transaction hash for the fill 9. crossed: whether the order crossed the spread (taker) Example output: { fills: [{ coin: "ETH", side: "buy", size: "10.0", price: "3450.50", fee: "0.69", closedPnl: "0.00", timestamp: 1712000000000 }], count: 20 } Use this to analyze a trader's recent activity, calculate realized PnL, evaluate trading frequency, or audit trade execution quality on Hyperliquid. Do NOT use for current positions -- use hyperliquid_get_account_state instead. Do NOT use for open/pending orders -- use hyperliquid_get_open_orders instead. Do NOT use for funding payments -- use hyperliquid_get_user_funding instead. Do NOT use for market-wide whale trades -- use hyperliquid_detect_whale_trades instead.
hyperliquid_get_user_funding
Use this when you need to retrieve funding payment history for a Hyperliquid perpetuals account. Returns all funding rate payments received or paid, useful for calculating funding income/expense and evaluating carry trade profitability. Returns: 1. coin: the perpetual market (BTC, ETH, SOL, etc.) 2. fundingRate: the funding rate applied (positive = longs pay shorts) 3. payment: USD amount received (positive) or paid (negative) 4. timestamp: when the funding payment occurred 5. positionSize: the position size at time of funding Example output: { funding: [{ coin: "BTC", fundingRate: "0.0001", payment: "-1.35", timestamp: 1712000000000, positionSize: "1.5" }], totalReceived: "45.20", totalPaid: "-12.30", netFunding: "32.90" } Use this to evaluate funding income for carry/basis trades, calculate total cost of holding positions, or analyze the profitability of a delta-neutral funding strategy on Hyperliquid. Do NOT use for current positions -- use hyperliquid_get_account_state instead. Do NOT use for market-wide funding rates -- use hyperliquid_get_funding_rates instead. Do NOT use for funding arbitrage opportunities -- use funding_arb_find_opportunities instead. Do NOT use for trade execution history -- use hyperliquid_get_trade_fills instead.

Endpoints

URLTransportStateLatencyChecked
https://hl-portfolio.api.klymax402.com/mcp sse answering 22 ms 1 min ago

HL Portfolio API — questions

Answers built from our own checks of this server.

What can HL Portfolio API do?
It exposes 4 tools, read directly from the server on our last check. Among them: hyperliquid_get_account_state, hyperliquid_get_open_orders, hyperliquid_get_trade_fills, hyperliquid_get_user_funding. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is HL Portfolio API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 26 ms. The bar chart above shows every period we have measured.
How do I connect HL Portfolio API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HL Portfolio API need an API key?
No. HL Portfolio API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is HL Portfolio API?
It answers our handshake in 26 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is HL Portfolio API open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.