Vordium perps for any MCP client: markets, accounts, and orders you confirm, signed on your machine.
Scored across 26 tools
Most tools target distinct data, but several overlap heavily: get_account bundles balances, positions and orders that get_balance/get_positions/get_orders also return, and get_address further overlaps with account/agent/tx data. get_network vs get_status and get_policy vs get_agents/get_risk also have fuzzy boundaries, though descriptions and examples help.
All 26 tools use a consistent get_noun snake_case pattern with no mixed verb styles or casing. The naming is highly predictable and easy to reason about.
At 26 tools, the surface is just over the heavy threshold and feels sprawling for what is effectively a read-only data server. Many granular getters could be consolidated or scoped, especially the account/address/balance/position/order group.
The surface is read-only and covers many queries, but for an apparent Vordium trading/agent platform it lacks core lifecycle actions such as placing/canceling orders, creating/updating agents or policies, depositing/withdrawing, and claiming rewards. These gaps will cause dead ends for users expecting to act on the data.
One account at a glance: USDC balances, positions with entry, mark, unrealized PnL and liquidation price, and open orders. Ask: "Check my account 0x…"
Inputs: address (required). Returns: usdc, orders, address, network, +3 more
An address summary: account value, open positions, agents and EVM transactions, with its explorer link. Ask: "Look up 0x…"
Inputs: address (required). Returns: address, network, summary, explorer, +2 more
An owner's AI agents: status, limits and policy, usage, and each agent's latest actions. Ask: "What are my agents doing?"
Inputs: address (required). Returns: count, owner, agents, network, +1 more
An account's USDC: available to trade, in positions, reserved by orders, unrealized PnL. Ask: "How much USDC does 0x… have?"
Inputs: address (required). Returns: usdc, address, network, summary
One block by height: time, proposer, operations, with its explorer link. Ask: "What happened in block 152,000,000?"
Inputs: height (required). Returns: network, summary
Price candles (open, high, low, close, volume) for one market. Ask: "How did ETH move over the last day?"
Inputs: limit, price, symbol, pair_id, +1 more. Returns: count, market, candles, network, +3 more
Maker and taker fees, maximum leverage, initial and maintenance margin, and the liquidation terms as the network publishes them (the fee, or none), for every market or one. Ask: "What does it cost to trade BTC with 10x?"
Inputs: symbol, pair_id. Returns: count, markets, network, summary, +1 more
An account's recent trades with price, size, fee and realized PnL, as the explorer records them. Ask: "What did 0x… trade today?"
Inputs: address (required), limit. Returns: address, network, summary
The funding rate, interval and next settlement for one market, and optionally its past settlements. Ask: "What has ETH funding been over the last day?"
Inputs: symbol, history, pair_id. Returns: market, history, network, pair_id, +4 more
The season's points leaderboard, or the trading leaderboard by PnL, ROI or volume. Ask: "Who leads the season?"
Inputs: sort, board, limit, window, +1 more. Returns: rows, board, network, summary
Every market the network lists, with its state, leverage, fees and trading rules (tick, lot, minimum size). Ask: "Which markets can I trade?"
Inputs: no named parameters. Returns: count, markets, network, summary
Which Vordium network this server reads, checked against the network itself, and the facts it vouches for (chain id, genesis, finalized block, agent trading on or off), and whether it matches the chain id and genesis this release is pinned to (nothing is signed otherwise). Ask: "Which network am I connected to?"
Inputs: no named parameters. Returns: truth, pinned, network, summary, +2 more
Oracle and mark prices, for every market or one. Ask: "What is the ETH price?"
Inputs: symbol, pair_id. Returns: prices, network, summary
One resting order by its id: market, side, price, size left. An order that is not resting now (it filled or was cancelled) is reported as gone. Ask: "What is the state of order 8840974?"
Inputs: order_id (required), address. Returns: found, order, address, network, +2 more
Resting bids and asks for one market, best first, with the spread. Ask: "How deep is the BTC book?"
Inputs: depth, symbol, pair_id. Returns: asks, bids, empty, market, +6 more
An account's resting orders, with their order ids. Ask: "Which orders does 0x… have open?"
Inputs: address (required). Returns: count, orders, address, network, +1 more
An address's season points by source, its rank, whether it qualifies and its VORD estimate. Ask: "What's my rank in the season?"
Inputs: address (required), season_id. Returns: rank, address, network, summary, +2 more
Each agent's policy and market limits as the chain stores them, and whether the network enforces them now. Ask: "What limits does my agent trade under?"
Inputs: address (required), agent. Returns: count, owner, agents, network, +2 more
An account's open positions as the chain stores them. Ask: "What positions does 0x… hold?"
Inputs: address (required). Returns: count, address, network, summary, +1 more
An address's referral code, tier, referred volume and earnings. Ask: "How much have my referrals earned?"
Inputs: address (required). Returns: code, tier, address, network, +1 more
Each agent's usage against its policy, as the chain accounts it. Ask: "How much of its daily loss limit has my agent used?"
Inputs: address (required), agent. Returns: count, owner, agents, network, +2 more
The current rewards season: status, VORD budget, rules, participants and how many qualify. Ask: "What is the current season?"
Inputs: season_id. Returns: name, network, summary, season_id
Is the network live: block height, blocks per second, validators agreeing, and whether trading and deposits are open. Ask: "Is Vordium up right now?"
Inputs: no named parameters. Returns: live, height, network, summary, +6 more
Agent limits by tier and the referral tier table, where the network serves them. Ask: "How many agents can each tier run?"
Inputs: no named parameters. Returns: network, summary, agent_limits, referral_tiers
The latest trades in one market: time, side, price, size and value. Ask: "Show the last 10 BTC trades."
Inputs: limit, symbol, pair_id. Returns: count, market, trades, network, +2 more
One EVM transaction by hash: block, sender, receiver, value and result, with its explorer link. The hash is sent to the explorer to look it up, so give only a transaction hash, never a key. Ask: "Explain transaction 0x…"
Inputs: hash (required). Returns: network, summary
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Live prices, perps, prediction markets and a paper trading desk over one MCP.
Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution
Hyperliquid MCP — read-only market data from Hyperliquid's public info API.
Trade Papertrade BTC and ETH perps from Claude, ChatGPT, Codex, Cursor and any MCP client.
Add one secure layer between your agents and this server.