hyperliquid-mcp
MCP server for Hyperliquid perpetual trading, order execution, live order-book/microstructure signals, trade-flow analytics, and Monte Carlo risk, exposed to AI assistants over the Model Context Protocol.
No README could be loaded. View the project on GitHub for full documentation.
Frequently asked questions
What is hyperliquid-mcp?
hyperliquid-mcp is MCP server for Hyperliquid perpetual trading, order execution, live order-book/microstructure signals, trade-flow analytics, and Monte Carlo risk, exposed to AI assistants over the Model Context Protocol.
How do I install hyperliquid-mcp?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is hyperliquid-mcp open source?
Yes — it is hosted on GitHub at https://github.com/Dakkshin/hyperliquid-mcp and has 4 stars.
Related MCP tools
AI-powered OSINT agent with interactive REPL, MCP server, and CLI. 19 tools. Works with Claude, GPT-4, or local models. For authorized security research only.
Open-source coding agent memory. Records issues, attempts, fixes and decisions, then warns your agent before it repeats an approach that already failed. Native MCP server for Claude Code, Cursor, Antigravity and Codex. 100% local, no cloud, no telemetry. MIT.
Build effective agents using Model Context Protocol and simple workflow patterns Python-based implementation. Trusted by 7600+ developers.
An AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.
Cut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP client. 313B+ tokens saved.
Decision audit trail + persistent memory for AI trading agents. Outcome-weighted recall, tamper-evident SHA-256 chain with RFC 3161 anchoring, 20 MCP tools.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP