# OMX for Hyperliquid (pypi · omx-hyperliquid)

Hyperliquid execution for AI agents: limits, human approval, kill switch. Keyless demo + live paper.

- Trust score: 67/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `omx-hyperliquid`: 67/100 (this document), [markdown](https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid.md), [page](https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid)

## Channel facts

- Registry: `pypi`
- Package: `omx-hyperliquid`
- Version: `0.1.8`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 56 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Lumen-Founder/omx-hyperliquid-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 895 tokens (~89/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill_switch" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OMX for Hyperliquid MCP server?

OMX for Hyperliquid runs locally as a PyPI package, launched with uvx omx-hyperliquid. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lumen-founder-omx-hyperliquid-trading -- uvx omx-hyperliquid
```

### Cursor

```json
{
  "mcpServers": {
    "lumen-founder-omx-hyperliquid-trading": {
      "command": "uvx",
      "args": [
        "omx-hyperliquid"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lumen-founder-omx-hyperliquid-trading": {
      "command": "uvx",
      "args": [
        "omx-hyperliquid"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lumen-founder-omx-hyperliquid-trading -- uvx omx-hyperliquid
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lumen-founder-omx-hyperliquid-trading": {
      "type": "local",
      "command": [
        "uvx",
        "omx-hyperliquid"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lumen-founder-omx-hyperliquid-trading --command uvx --arg omx-hyperliquid
```

### Hermes

```yaml
mcp_servers:
  lumen-founder-omx-hyperliquid-trading:
    command: "uvx"
    args: ["omx-hyperliquid"]
```

### Netclaw

```json
{
  "McpServers": {
    "lumen-founder-omx-hyperliquid-trading": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "omx-hyperliquid"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lumen-founder-omx-hyperliquid-trading -t stdio -c uvx -a omx-hyperliquid
```

### Other

```json
{
  "mcpServers": {
    "lumen-founder-omx-hyperliquid-trading": {
      "command": "uvx",
      "args": [
        "omx-hyperliquid"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-19 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-16 (score 65, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `get_quote` (~36 tokens)

Top of book, mid, data age and depth within the policy band for an agent-allowed coin.

Input parameters:

- `coin` (string, required)

### `preview_order` (~152 tokens)

Dry run: planned child orders, policy decisions, fee bound, and whether a human must approve.
side: buy|sell. algo: market|limit|twap|pov|chase|native_twap. size in base units. Sends nothing.

Input parameters:

- `algo` (string)
- `coin` (string, required)
- `duration_s` (integer)
- `limit_px`
- `max_slippage_bps` (number)
- `note` (string)
- `post_only` (boolean)
- `pov_rate` (number)
- `reduce_only` (boolean)
- `side` (string, required)
- `size` (number, required)
- `slices` (integer)

### `submit_order` (~212 tokens)

Submit an intent. Above the approval threshold or the daily agent budget it is queued for a
human and an approval_id is returned instead; check it with approval_status.
ALWAYS pass a fresh client_intent_id (8..40 chars, A-Z a-z 0-9 _ -) and REUSE it when you retry
after a timeout or error: a repeated id returns the existing intent (status "duplicate",
intent_id "ag-<client_intent_id>") and never sends a second order.

Input parameters:

- `algo` (string)
- `client_intent_id`
- `coin` (string, required)
- `duration_s` (integer)
- `limit_px`
- `max_slippage_bps` (number)
- `note` (string)
- `post_only` (boolean)
- `pov_rate` (number)
- `reduce_only` (boolean)
- `side` (string, required)
- `size` (number, required)
- `slices` (integer)

### `approval_status` (~34 tokens)

State of a queued approval: pending, approved, rejected, expired, executed or failed.

Input parameters:

- `approval_id` (string, required)

### `order_status` (~35 tokens)

Fill progress, average price, cost vs arrival mid, fees and block reasons of an intent.

Input parameters:

- `intent_id` (string, required)

### `get_receipt` (~65 tokens)

Execution receipt of an intent: every child order and fill (venue ids), exchange and builder fees,
cost vs arrival mid, self-checks and a sha256 receipt_hash; a finished intent's receipt is anchored in
the audit log.

Input parameters:

- `intent_id` (string, required)

### `cancel_order` (~33 tokens)

Cancel an intent this agent (same client name) created, and its resting children.

Input parameters:

- `intent_id` (string, required)

### `kill_switch` (~33 tokens)

Stop all new orders and cancel resting ones. Agents can turn it on, never off.

Input parameters:

- `reason` (string, required)

### `account_summary` (~27 tokens)

Equity, day P&L (flows excluded), positions, open orders and remaining agent budget.

### `policy_limits` (~22 tokens)

Read-only view of the policy limits, agent thresholds and builder fee.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 82
- 2026-11-19: 66
- 2026-11-18: 81
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 78
- 2026-11-11: 63
- 2026-11-10: 62
- 2026-11-09: 77
- 2026-11-08: 76
- 2026-11-07: 61
- 2026-11-06: 75
- 2026-11-05: 60

## Common questions

### What is the OMX for Hyperliquid MCP server?

OMX for Hyperliquid is an MCP server listed in the public MCP registry as io.github.Lumen-Founder/omx-hyperliquid-trading. Hyperliquid execution for AI agents: limits, human approval, kill switch. Keyless demo + live paper. This page covers its PyPI package (omx-hyperliquid).

### Is the OMX for Hyperliquid MCP server safe to use?

OMX for Hyperliquid scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the OMX for Hyperliquid MCP server expose?

OMX for Hyperliquid exposes 10 tools: get_quote, preview_order, submit_order, approval_status, order_status, and 5 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Is the OMX for Hyperliquid MCP server still maintained?

OMX for Hyperliquid is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the OMX for Hyperliquid MCP server under?

OMX for Hyperliquid declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the OMX for Hyperliquid MCP server?

VerifyMCP ran 15 checks on OMX for Hyperliquid, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about OMX for Hyperliquid: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/omx-hyperliquid/
- Socket report: https://socket.dev/pypi/package/omx-hyperliquid
- Repository: https://github.com/Lumen-Founder/omx-hyperliquid-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid.xml
- Changelog JSON feed: https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid.json
- HTML version of this page: https://verifymcp.io/servers/lumen-founder-omx-hyperliquid-trading/omx-hyperliquid
