HL Portfolio API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

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

The publisher's own server: PortfolioFit

VerifiedSSEWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only Hyperliquid perpetuals account analysis over a remote MCP endpoint: positions, PnL, fills, open orders and funding, paid per call.

What you can do
  • Fetch full clearinghouse state for a wallet: positions, margin, PnL, leverage, liquidation prices
  • List recent trade fills with coin, side, size, price, fee and closed PnL
  • List open orders with price, size, order type and reduce-only flag
  • Retrieve funding payments received or paid, with totals and net funding
When to use it
Useful when an assistant needs to inspect a Hyperliquid perpetuals account for risk exposure, margin health, copy-trading evaluation, funding cost analysis or order review. It is read-only analysis, not trade execution.
Requirements
A remote MCP endpoint reached over SSE; no API key, signup or environment variables. Each call is paid in USDC on Base L2 through the x402 protocol, so the client needs an x402-aware wallet or payment handler to answer the 402 challenge.
Before you install
Every tool call costs money (roughly $0.005 to $0.008 per call in USDC on Base), so automated loops can spend funds. Payment is handled by a wallet-capable client and routed through third-party facilitators (Coinbase CDP, PayAI). Wallet addresses queried are sent to the remote service.

Installation

In SourceWeft

  1. Open HL Portfolio API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fhl-portfolio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hl-portfolio-api": {
      "type": "sse",
      "url": "https://hl-portfolio.api.klymax402.com/mcp"
    }
  }
}

README

HL Portfolio API

[MCP Server] [x402] [License: MIT]

Analyze Hyperliquid accounts: positions, PnL, fills, open orders, funding. Full clearinghouse state for any wallet. The portfolio layer agents need for Hyperliquid trading intelligence. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "hl-portfolio": {      "url": "https://hl-portfolio.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://hl-portfolio.api.klymax402.com/api/account" \  -H "Content-Type: application/json" \  -d '{"address":"0x0000000000000000000000000000000000dEaD"}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
hyperliquid_get_account_statePOST/api/account$0.008Full clearinghouse state for a Hyperliquid wallet: positions, margin, PnL, leverage, liquidation prices.
hyperliquid_get_trade_fillsPOST/api/fills$0.008Recent trade fills for a Hyperliquid wallet: coin, side, size, price, fee, closedPnl, timestamp.
hyperliquid_get_open_ordersPOST/api/orders$0.005Open orders for a Hyperliquid wallet: coin, side, size, price, order type, reduce-only flag.
hyperliquid_get_user_fundingPOST/api/funding$0.005Funding payments received/paid by a Hyperliquid wallet: coin, amount, rate, timestamp.

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.

Parameters

NameTypeRequiredDescription
addressstringyesHyperliquid wallet address (0x...) to retrieve account state for

Example response:

json
{ 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" }] }

When to use: analyzing a trader's risk exposure, checking margin health, or evaluating portfolio allocation on Hyperliquid. Essential for copy-trading evaluation and risk monitoring.

Not for: trade history (use hyperliquid_get_trade_fills), open orders (use hyperliquid_get_open_orders), funding payments (use hyperliquid_get_user_funding), vault performance (use hyperliquid_get_vault_details), whale tracking (use hyperliquid_detect_whale_trades).

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.

Parameters

NameTypeRequiredDescription
addressstringyesHyperliquid wallet address (0x...) to retrieve trade fills for
limitnumbernoMaximum number of fills to return (default: 20, max: 100)

Example response:

json
{ fills: [{ coin: "ETH", side: "buy", size: "10.0", price: "3450.50", fee: "0.69", closedPnl: "0.00", timestamp: 1712000000000 }], count: 20 }

Not for: current positions (use hyperliquid_get_account_state), open/pending orders (use hyperliquid_get_open_orders), funding payments (use hyperliquid_get_user_funding).

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.

Parameters

NameTypeRequiredDescription
addressstringyesHyperliquid wallet address (0x...) to retrieve open orders for

Example response:

json
{ orders: [{ coin: "BTC", side: "buy", limitPx: "65000.00", sz: "0.5", orderType: "limit", reduceOnly: false, oid: 123456 }], count: 3 }

Not for: executed trades (use hyperliquid_get_trade_fills), current positions (use hyperliquid_get_account_state).

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.

Parameters

NameTypeRequiredDescription
addressstringyesHyperliquid wallet address (0x...) to retrieve funding history for
startTimenumbernoUnix timestamp in milliseconds to start from (optional, default: last 7 days)

Example response:

json
{ funding: [{ coin: "BTC", fundingRate: "0.0001", payment: "-1.35", timestamp: 1712000000000, positionSize: "1.5" }], totalReceived: "45.20", totalPaid: "-12.30", netFunding: "32.90" }

Not for: current positions (use hyperliquid_get_account_state), funding arbitrage opportunities (use funding_arb_find_opportunities), trade execution history (use hyperliquid_get_trade_fills).

Example agent prompts

  • "Retrieve the full portfolio state of a Hyperliquid perpetuals account"
  • "Retrieve recent trade executions (fills) for a Hyperliquid perpetuals account"
  • "See all pending/open orders for a Hyperliquid perpetuals account"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 23ba94d

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Portfolio integrations