In-depth architectural comparison of the Perp Cli and Hyperliquid Info Mcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Perp Cli
Finance & Fintech · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Hyperliquid Info Mcp
Finance & Fintech · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Perp Cli if you need specialized Finance & Fintech tools running via a local process. Choose Hyperliquid Info Mcp if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Perp Cli when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: LIGHTER_API_KEY_INDEX.
Primary tools included: Supports 4 DEXes: Pacifica, Hyperliquid, Lighter, Aster, Funding rate arbitrage scanning and dual-leg execution, Unified portfolio overview with balances, positions, and risk.
Perp Cli is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Hyperliquid Info Mcp belongs to Finance & Fintech using local stdio subprocess. Select Perp Cli when you need capabilities focused on finance & fintech and Hyperliquid Info Mcp when you require tools for finance & fintech.
Primary tools included: User-specific queries for positions, orders, trades, funding, fees, and staking, Market data including mid prices, L2 order book snapshots, and candlestick data, Metadata retrieval for perpetual and spot markets.