Is there an official Hyperliquid MCP server?

Hyperliquid does not operate any of the community repositories compared here. Fensory and Phantom are product-operated integrations that reach Hyperliquid, while the remaining projects are community software.

Should I use my main wallet private key?

Use a revocable, restricted agent key where the project supports one. A main wallet key has broader authority and creates a larger failure surface. Read-only workflows should use an address without a signing key whenever the server allows it.

Which open-source option has the strongest key handling?

hypurrquant/perp-cli is the strongest documented option in this field. It accepts Hyperliquid agent keys through a hidden prompt or stdin and stores credentials in an encrypted local vault. The operator still owns the local machine and its security.

Does testnet make a trading server safe?

Testnet is useful for checking tool calls, order fields and failure handling before real funds are exposed. It does not test the security of your production machine, the accuracy of live market data or the behavior of a model under a different prompt.

What should I compare after the signing key?

Check whether the server supports read-only use, agent keys, the exact order types you need, testnet, cancellation after lost connectivity, active maintenance and a real software license. Then decide which operating work you are willing to own.

Hyperliquid MCP servers, compared by where the signing key lives

A Hyperliquid MCP server can give an AI assistant market data, account reads or the ability to place perpetual futures orders. The material difference is where the signing credential lives. Some projects put it in an environment file, some encrypt it locally, and two hosted routes keep it out of the MCP client. This comparison uses official documentation and repository history checked on 18 October 2026.

Published 2026-10-18, last edited 2026-10-18. Every competitor claim was read against its own source on 2026-10-18. The page is re-checked when a source changes and at least quarterly. Fensory appears in this comparison and sells a trading account.

The comparison

Hyperliquid MCP routes compared on signing credentials, deployment, execution, controls, maintenance and software cost
Route	Where the signing credential lives	How it runs	What it can do	Controls	Project status	Software cost
FensoryOurs	None. OAuth through a Fensory account	Remote Streamable HTTP. No local package or server process.	Executes	a kill-switch, an access expiry, a market allow-list and a per-order cap, all enforced on the account. An order above the cap is rejected rather than trimmed	Active, hosted	Free to connect. 0.01% to 0.05% on perpetual futures and Hyperliquid spot, nothing on tokenized equities, yields or bridging
Phantom MCP	None. Browser sign-in on first use	Remote service reached through the Phantom MCP client connection.	Executes	A simulation-first convention on transfers and transactions, which the agent follows rather than the account enforcing. The segregated wallet is the real boundary	Live, but the public repository has not moved since 28 April 2026. Development is internal	No Phantom swap fee documented
hypurrquant/perp-cli	Imported through a hidden prompt or stdin into an encrypted local vault. Hyperliquid agent keys are supported, so the master key need not be stored.	Local CLI and MCP server. The operator chooses the machine and uptime model.	Reads markets and accounts, previews and places orders, closes positions and scans funding or spread opportunities.	Local risk checks, dry-run and pre-trade validation are documented. The operator owns the policy and the machine that enforces it.	Active. Default branch updated 18 October 2026.	MIT-licensed software. Infrastructure and venue costs remain.
0xikalgo/hyperliquid-mcp	An agent private key is stored in a local .env file. Automatic setup temporarily stores the main key as well.	Self-hosted Rust server with a keyless read-only mode.	Spot and perpetual reads, balances, orders, leverage, closing positions and spot-to-perpetual transfers.	No independent order cap is documented. Agent-key scope and revocation are the main controls.	Default branch last updated 17 March 2026. The project states that it has no guarantees.	MIT-licensed software. Automatic setup approves a 0.01% builder fee.
edkdev/hyperliquid-mcp	The signing key is supplied as HYPERLIQUID_PRIVATE_KEY in the MCP client environment. An approved API-wallet key can be used.	Self-hosted local MCP server.	Perpetual futures market and limit orders, bracket orders, cancellation, modification and account reads.	No independent order cap is documented. Agent-key permissions are the available boundary.	Default branch last updated 27 October 2025. Four visible commits.	MIT-licensed software.
caiovicentino/hyperliquid-mcp-server	HYPERLIQUID_PRIVATE_KEY is stored in .env or the MCP client environment. Restricted agent-key use is not documented.	Self-hosted local MCP server.	Trading, account, market-data and real-time tools, including TWAP and a dead-man switch.	The dead-man switch can cancel orders after lost connectivity. No order-size cap is documented.	Default branch last updated 10 November 2025. Documentation is primarily in Portuguese.	MIT-licensed software.
erscoder/hyperliquid-mcp	Read-only mode uses an address. Trading stores HL_PRIVATE_KEY in the client environment or a local .env file.	Self-hosted local MCP server.	Read-only market and account tools, plus orders, closing positions and leverage when a key is configured.	Read-only mode removes execution authority. No independent trading cap is documented.	Default branch last updated 22 August 2026.	Source available. The README says MIT, but the repository has no LICENSE file.
GigabrainGG/hyperliquid-mcp	HYPERLIQUID_PRIVATE_KEY is stored in an environment variable, .env or config.json. API wallets are suggested.	Self-hosted local MCP server.	Perpetual futures orders, account reads, leverage and spot-to-perpetual transfers.	No independent order cap is documented. Testnet is available for rehearsal.	Default branch last updated 17 January 2026.	No license file was found, so reuse rights are not stated.
Impa-Ventures/hyperliquid-mcp	PRIVATE_KEY is stored in .env or the MCP client configuration. The docs do not distinguish a main key from an agent key.	Self-hosted local MCP server.	Reads account and market state, places and cancels orders, and transfers between spot and perpetual balances.	No keyless mode, testnet setup or independent order cap is documented.	Default branch last updated 25 March 2025.	MIT-licensed software.

The credential model matters more than the tool count

All nine routes can make a useful Hyperliquid workflow, but they expose different failure surfaces. A raw wallet key in an environment file gives the local process everything that key can authorize. A Hyperliquid agent key narrows that authority and can be revoked, yet the local process still needs to store a signing credential. An encrypted local vault improves storage without removing the machine from the trust boundary.

Fensory and Phantom take a different route. Both use browser sign-in and keep a signing key out of the MCP client configuration. Phantom creates a dedicated wallet and applies its own signing policy. Fensory connects a hosted server through OAuth and checks account settings before sending an order. Neither arrangement makes trading safe by itself. It changes who operates the signing path and which controls exist outside the model.

The open-source field also has real strengths. You can read the code, choose where it runs, replace the signing logic and add controls the packaged product does not provide. hypurrquant/perp-cli is the strongest current example: it supports Hyperliquid agent keys, stores credentials in an encrypted local vault, exposes a risk gate and has active development. That is more operational work, and for a capable team it can be the right trade.

The Hyperliquid routes

Fensory

OursOfficial project

A hosted remote MCP server with OAuth. It reaches Hyperliquid spot and perpetual futures, including supported builder-dex markets, while account controls are configured in the Fensory app.

What it reaches: MCP: Hyperliquid spot and perpetual futures. App: tokenized US equities and treasuries, and gold
Cost: Free to connect. 0.01% to 0.05% on perpetual futures and Hyperliquid spot, nothing on tokenized equities, yields or bridging

Choose this if: You want a hosted connection, no signing credential in the MCP client, and account-enforced limits without operating your own server.

Worth knowing: The runtime is proprietary and Fensory is unavailable to US persons. A per-order cap does not stop a sequence of losing orders inside the limit.

The Fensory MCP server

Phantom MCP

Official project

Phantom creates a dedicated wallet through browser sign-in, signs through its key service and exposes Hyperliquid perpetual futures alongside on-chain wallet actions.

What it reaches: Solana, Ethereum and Bitcoin swaps, Hyperliquid perpetual futures
Cost: No Phantom swap fee documented

Choose this if: You want a dedicated wallet, no key in the client configuration and a broader on-chain wallet surface alongside Hyperliquid perpetual futures.

Worth knowing: No account-enforced order cap, market allow-list or kill-switch is documented. The amount funded to the dedicated wallet remains the main boundary.

Phantom docs

hypurrquant/perp-cli

Community project

An actively maintained MIT-licensed command-line system with eighteen MCP tools, keyless market reads, trading workflows, a local risk gate and support for several perpetual futures venues.

What it reaches: Perpetual futures across supported venues, including Hyperliquid and HIP-3 markets.
Cost: MIT-licensed software. Infrastructure and venue costs remain.

Choose this if: You want open code, encrypted local credential storage, several venues and the ability to modify the execution and risk path.

Worth knowing: It is a broader trading CLI rather than a dedicated Hyperliquid service. Setup, uptime, updates and credential security remain your responsibility.

hypurrquant/perp-cli

0xikalgo/hyperliquid-mcp

Community project

A Rust implementation with keyless read-only mode, spot and perpetual market tools, order execution and support for an existing Hyperliquid agent key.

What it reaches: Hyperliquid spot and perpetual futures.
Cost: MIT-licensed software. Automatic setup approves a 0.01% builder fee.

Choose this if: You prefer Rust, want a keyless read-only mode and can provision an existing agent key rather than exposing the main wallet key.

Worth knowing: The signing key still sits in a local environment file. The automatic first-run path briefly writes the main key and should not be treated as the safer setup.

0xikalgo repository

edkdev/hyperliquid-mcp

Community project

A compact MIT-licensed server for perpetual futures orders, bracket orders, account reads, market data and vault reads.

What it reaches: Hyperliquid perpetual futures. Spot execution is not documented.
Cost: MIT-licensed software.

Choose this if: You want a small perpetual futures server whose code and order path are easy to inspect.

Worth knowing: No keyless read-only mode is documented, TWAP is listed as coming soon and the repository has not moved for nearly a year.

edkdev repository

caiovicentino/hyperliquid-mcp-server

Community project

An MIT-licensed server whose README documents twenty-seven tools, including orders, TWAP, leverage, isolated margin, market reads and a dead-man switch.

What it reaches: Hyperliquid perpetual futures.
Cost: MIT-licensed software.

Choose this if: You need TWAP or a documented dead-man switch and are comfortable reviewing a Portuguese-first repository.

Worth knowing: The setup tells users to export a wallet private key. No keyless mode or complete agent-key workflow is documented.

caiovicentino repository

erscoder/hyperliquid-mcp

Community project

A seventeen-tool server for perpetual futures market data, account state and order execution. Read-only use needs only a wallet address.

What it reaches: Hyperliquid perpetual futures.
Cost: Source available. The README says MIT, but the repository has no LICENSE file.

Choose this if: You want a simple read-only start and will enable trading only after inspecting the code and credential path.

Worth knowing: There is no license file, testnet setup or documented restricted-agent-key workflow.

erscoder repository

GigabrainGG/hyperliquid-mcp

Community project

A perpetual futures server with market and limit orders, bracket orders, take-profit and stop-loss orders, leverage and account reads.

What it reaches: Hyperliquid perpetual futures.
Cost: No license file was found, so reuse rights are not stated.

Choose this if: You want documented bracket and stop workflows and will review the code despite the missing license.

Worth knowing: No reuse license or keyless mode is documented. Partial market closing is explicitly unsupported.

GigabrainGG repository

Impa-Ventures/hyperliquid-mcp

Community project

An MIT-licensed server for account and order reads, market data, order placement and transfers between spot and perpetual accounts.

What it reaches: Hyperliquid perpetual futures and internal spot-to-perpetual transfers.
Cost: MIT-licensed software.

Choose this if: You are maintaining an existing integration built on this code and have already reviewed its key handling.

Worth knowing: The repository is the least current option here and documents neither an agent-key procedure nor testnet configuration.

Impa Ventures repository

How we checked

The field includes the seven community Hyperliquid servers already identified in the Fensory MCP comparison, plus Phantom and Fensory as the two browser-authorized routes. No project here is presented as an official Hyperliquid-operated MCP server.

Repository activity means the newest visible commit on the default branch, checked 18 October 2026. A recent commit is evidence of activity, not a security review. Tool claims come from each project README and were not treated as proof that every operation succeeds against a funded account.

The credential column distinguishes a main wallet key, a revocable Hyperliquid agent key, an encrypted local store and a hosted signer. These are different risk boundaries. A local agent key is materially narrower than a master key even though both are signing credentials on the machine.

Fensory publishes the page and appears first because it is the publisher. The table still names the advantages of local code, and hypurrquant/perp-cli is the recommendation when source control, customization and multi-venue support matter more than hosted operation.

Questions people ask

Is there an official Hyperliquid MCP server?: Hyperliquid does not operate any of the community repositories compared here. Fensory and Phantom are product-operated integrations that reach Hyperliquid, while the remaining projects are community software.
Should I use my main wallet private key?: Use a revocable, restricted agent key where the project supports one. A main wallet key has broader authority and creates a larger failure surface. Read-only workflows should use an address without a signing key whenever the server allows it.
Which open-source option has the strongest key handling?: hypurrquant/perp-cli is the strongest documented option in this field. It accepts Hyperliquid agent keys through a hidden prompt or stdin and stores credentials in an encrypted local vault. The operator still owns the local machine and its security.
Does testnet make a trading server safe?: Testnet is useful for checking tool calls, order fields and failure handling before real funds are exposed. It does not test the security of your production machine, the accuracy of live market data or the behavior of a model under a different prompt.
What should I compare after the signing key?: Check whether the server supports read-only use, agent keys, the exact order types you need, testnet, cancellation after lost connectivity, active maintenance and a real software license. Then decide which operating work you are willing to own.