Hyperliquid Info MCP Server

Created By
kukapaya year ago
An MCP server that provides real-time data and insights from the Hyperliquid perp DEX for use in bots, dashboards, and analytics.
Overview

what is Hyperliquid Info MCP Server?

Hyperliquid Info MCP Server is a server that provides real-time data and insights from the Hyperliquid perpetual decentralized exchange (DEX) for use in trading bots, dashboards, and analytics.

how to use Hyperliquid Info MCP Server?

To use the server, clone the repository from GitHub, install the necessary dependencies, and run the server in development mode. You can interact with the server using natural language prompts to fetch data and insights.

key features of Hyperliquid Info MCP Server?

  • User data queries for positions, orders, and trade history.
  • Market data tools for mid prices, order book snapshots, and candlestick data.
  • Analysis prompt to analyze user trading activity.
  • ISO 8601 support for precise time-based queries.

use cases of Hyperliquid Info MCP Server?

  1. Analyzing trading positions and performance.
  2. Fetching user-specific trading data and history.
  3. Retrieving market data for analysis and decision-making.
  4. Integrating with trading bots for automated trading strategies.

FAQ from Hyperliquid Info MCP Server?

  • What programming language is required?

Python 3.10 is required to run the server.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • Can I use this server for real-time trading?

Yes, it is designed to provide real-time insights for trading activities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kukapay
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago