Hyperliquid MCP Server v6

Created By
TradingBalthazara year ago
Hyperliquid MCP Server v6 - A Model Context Protocol server for interacting with the Hyperliquid exchange API
Overview

what is Hyperliquid MCP Server v6?

Hyperliquid MCP Server v6 is a Model Context Protocol server designed for seamless interaction with the Hyperliquid exchange API, enabling users to manage their trading activities effectively.

how to use Hyperliquid MCP Server v6?

To use the server, clone the repository, install the necessary dependencies, build the server, and run it. It can be integrated with any MCP-compatible client, such as a Next.js application.

key features of Hyperliquid MCP Server v6?

  • Full integration with Hyperliquid API
  • Support for both spot and perpetual markets
  • Real-time price data
  • Account information and position management
  • Order placement and cancellation
  • Strategy creation and management

use cases of Hyperliquid MCP Server v6?

  1. Automating trading strategies on the Hyperliquid exchange.
  2. Monitoring account positions and executing trades in real-time.
  3. Developing custom trading applications that leverage the Hyperliquid API.

FAQ from Hyperliquid MCP Server v6?

  • Is the server compatible with all trading strategies?

Yes! The server supports the creation and management of custom trading strategies.

  • What programming language is used?

The server is built using JavaScript.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TradingBalthazar
Star
0
Language
JavaScript
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