# OMX for Hyperliquid (pypi · omx-hyperliquid)

Non-custodial Hyperliquid execution for AI agents: pre-trade limits, kill switch, audit log.

- Trust score: 30/100 (low)
- Change this week: 0
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Deprecated**: this server is marked deprecated in the MCP registry. The registry records this reason: "Renamed to io.github.Lumen-Founder/omx-hyperliquid-trading (same package, omx-hyperliquid)."

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `omx-hyperliquid`
- Version: `0.1.3`
- 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**: 74/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to Lumen-Founder/omx).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## 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 -- uvx omx-hyperliquid
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "lumen-founder-omx": {
      "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 30, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 45, +15)

- [security improvement] Malware scan: unverified → pass

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

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 45, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 30, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-15 (score 45, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-14 (score 30, −15)

- [security regression] Malware scan: pass → unverified

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

- [security improvement] Malware scan: unverified → pass

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

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

## Score history

- 2026-11-21: 30
- 2026-11-20: 45
- 2026-11-19: 30
- 2026-11-18: 45
- 2026-11-17: 30
- 2026-11-16: 45
- 2026-11-15: 45
- 2026-11-14: 30
- 2026-11-13: 45
- 2026-11-12: 45
- 2026-11-11: 30
- 2026-11-10: 30
- 2026-11-09: 30
- 2026-11-08: 30
- 2026-11-07: 45
- 2026-11-06: 30
- 2026-11-05: 45

## 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. Non-custodial Hyperliquid execution for AI agents: pre-trade limits, kill switch, audit log. This page covers its PyPI package (omx-hyperliquid).

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

OMX for Hyperliquid scores 30 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.

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

OMX for Hyperliquid is marked deprecated 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 8 checks on OMX for Hyperliquid, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about OMX for Hyperliquid: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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
- Changelog RSS feed: https://verifymcp.io/servers/lumen-founder-omx/omx-hyperliquid.xml
- Changelog JSON feed: https://verifymcp.io/servers/lumen-founder-omx/omx-hyperliquid/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lumen-founder-omx/omx-hyperliquid.json
- HTML version of this page: https://verifymcp.io/servers/lumen-founder-omx/omx-hyperliquid
