Fensory vs an open-source Hyperliquid MCP server
Fensory operates the server and keeps the venue signing credential out of the MCP client. A self-hosted Hyperliquid server gives the operator the code and the signing path, which also means the operator owns credential storage, uptime, updates and every control that should stop a bad order.
hypurrquant/perp-cli is the current reference for the open-source route because it is active, MIT licensed, supports Hyperliquid agent keys and stores them in an encrypted local vault. It still keeps a signing credential on the operator’s machine. That is not inherently wrong. It is the trade for owning the execution stack.
Every cell was checked against first-party documentation, governing terms or regulator material on 2026-10-18, never on a directory listing or another comparison. Fensory publishes this page and appears in the table.
Side by side
| Product | Who holds the funds | What stops a bad order | What it trades | Where you can open it |
|---|---|---|---|---|
| hypurrquant/perp-cliOpen-source, local and modifiable multi-venue server | At the connected venue. The software runs locally and signs with the credential you import. | Local risk checks, dry-run and pre-trade validation are documented. The operator owns the policy and the machine that enforces it. | Perpetual futures across supported venues, including Hyperliquid and HIP-3 markets. | No product geofence is documented. Venue restrictions still apply. |
| FensoryOursHosted remote server with OAuth and account controls | You. Tokens settle to a wallet you control, perp margin sits at the venue | 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 | MCP: Hyperliquid spot and perpetual futures. App: tokenized US equities and treasuries, and gold | Not available to US persons |
Every row uses the same custody, control, asset and geography fields so the comparison stays aligned.
What you are choosing
The operating trade-off in concrete terms, from first setup to the markets the agent can reach.
| Decision | hypurrquant/perp-cli | Fensory |
|---|---|---|
| Code control | Operator can inspect and change the stack | Proprietary hosted runtime |
| Signing credential | Encrypted local vault; agent key supported | No venue key in the MCP client |
| Uptime | Operator responsibility | Fensory responsibility |
| Risk logic | Local gate you can modify | Published account settings you cannot extend |
| Venue scope | Several perpetual futures venues | Hyperliquid spot and perpetual futures through MCP |
Where it is stronger
Specific rather than generous. A comparison that cannot name what the other product does better has not understood it.
hypurrquant/perp-cli
The open-source route wins on control. A team can inspect the order path, replace the policy, add a venue, keep logs in its own environment and avoid a builder fee charged by a hosted intermediary. perp-cli also supports several perpetual futures venues, keyless market scans, dry-run workflows and a risk gate that the operator can change. Fensory cannot offer that level of ownership over its backend.
What connecting actually involves
hypurrquant/perp-cli
Install and run the CLI, connect the MCP server, import a restricted agent or API key through the hidden prompt or stdin, and decide where the process and encrypted vault live. Market reads can run without a key. Authenticated tools add portfolio, preview, execution, close, funding and profit-and-loss workflows. Infrastructure, monitoring and incident response stay with the operator.
Fensory
Connect the remote endpoint through OAuth, configure the account controls and let the hosted service operate the server. There is less code to own and less freedom to change it. The account pays the published Fensory fee where applicable, plus venue fees.
Where Fensory differs
Fensory removes the local server and local signing credential from the MCP connection. The user authorizes one remote URL through OAuth and does not need to patch, restart or monitor the trading process.
The controls live in the account rather than in code the operator must maintain. Fensory checks the per-order cap, approved markets, access expiry and kill-switch. A DIY team can build stronger or more specific rules, but the server does not acquire them merely because it is open source.
Fensory also separates the app catalogue from the MCP execution path. Hyperliquid spot and perpetual futures are reachable over MCP. Supported tokenized equities and treasuries are app instruments and are not represented as trades a generic Hyperliquid server can place.
Which one is for you
You need to inspect or change every line that can place an order
Use the open-source route. That requirement is incompatible with a proprietary hosted runtime.
You already operate reliable trading infrastructure
Use the open-source route if its ongoing maintenance is ordinary work for your team.
You want one remote endpoint and no trading credential in the client
Use Fensory if you are eligible and its documented controls match your needs.
You need a custom daily-loss or portfolio rule
Use open source and implement it, or choose a product that documents that exact rule. Fensory’s current cap is per order, not per day.
You want tokenized equities rather than equity perpetual futures
Evaluate the Fensory app or another tokenized-equity venue. A Hyperliquid server reaches derivatives where listed, not the separate issuer token catalogues.
Questions people ask
- Is an open-source Hyperliquid MCP server free?
- The code can be free. The operator still pays for infrastructure, monitoring, maintenance and venue fees. At enough volume, owning the stack may cost less than a fee on every order.
- Does self-hosting mean I need my main wallet key?
- No. The current perp-cli reference supports a Hyperliquid agent or API key, so the master key need not live on the machine. The restricted signing key still needs secure local storage.
- Which route has better controls?
- Fensory ships four documented account settings. Open source gives a team the ability to build any rule it can implement and test. The stronger option depends on whether custom policy is a requirement or an operating burden.
- Can both routes place real Hyperliquid orders?
- Yes. Both can reach real execution when funded and enabled. Testnet, dry-run and preview paths reduce setup mistakes but do not guarantee live behavior or prevent losses.
- Does Fensory hide the private key from itself?
- The user does not place a venue key in the MCP client. Fensory operates a scoped signing path behind the hosted service. That is a managed trust boundary, not an assertion that no signing credential exists anywhere.
How this was put together
The open-source row is pulled from the R5 roundup and uses hypurrquant/perp-cli as the current reference. The full roundup lists the other community servers and their different license, maintenance and key-handling states.
Repository activity, license and setup were checked on the default branch on 18 October 2026. Tool claims come from the project documentation and are not presented as an independent funded-account test.
The cost comparison names components rather than inventing one VPS price. Many teams already operate infrastructure, while others would be adding a new production system.
Fensory publishes the page. Open source receives the recommendation for code control, custom policy and multi-venue scope. Fensory receives it for hosted operation and account controls without a local signing credential.