hip4-mcp
Related Servers
Alternatives to hip4-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceQuery live HIP-4 prediction market data on Hyperliquid - real-time odds, orderbooks, trades, candles, user positions, and portfolio analysis via 10 MCP tools.106MIT
- AlicenseAqualityNot gradedmaintenanceEnables interaction with the Hyperliquid DEX for retrieving market data, managing positions, and executing trades. Supports both testnet and mainnet operations with comprehensive trading tools including order placement, cancellation, and portfolio management.11MIT
- AlicenseAqualityDmaintenanceProvides read-only tools to query live Polymarket prediction-market data via the public Gamma API, enabling search, browsing, and detailed market and event information.4MIT
- AlicenseAqualityBmaintenanceRead-only Hyperliquid and cross-exchange market research for AI agents, providing structured tools for live market data without requiring authentication.943 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Hyperliquid markets for technical analysis, order book data retrieval, and cryptocurrency trading. Supports read-only market access without credentials and authenticated trading operations via private key configuration.MIT
- AlicenseAqualityBmaintenanceExposes real-time Hyperliquid explorer and analytics data from flowscan.xyz as 44 read-only tools, letting AI agents answer questions about protocol revenue, perp market positioning, individual open positions, wallet activity, and staking without an API key. It runs over stdio against Hyperliquid mainnet only, using the same API routes the Flowscan frontend calls.44MIT
TDQS
Scored across 10 tools
Each tool targets a distinct data type (market info, prices, orderbook, user data, encoding), but get_outcome_prices and get_outcome_depth_summary both return price-related data for all markets, which could cause minor confusion. Descriptions are clear enough to differentiate them.
Most tools follow a consistent verb_noun pattern (list_, get_, search_), but 'encoding_helper' breaks the pattern by using a noun phrase. The rest are highly consistent, with all get_ tools prefixed uniformly.
10 tools is well within the optimal 3-15 range and each covers a specific aspect of HIP-4 outcome markets (listing, pricing, orderbook, user positions, trades, etc.). No tool feels redundant or unnecessary.
The server effectively covers read-only market data needs: listing, searching, prices, depth, candles, and user account data. The only notable gap is the lack of order placement/cancellation, but the server appears intended for data retrieval, not trading. A single-market fetch could also be useful but list_outcomes already provides all metadata.