hypernatt-terminal vs Hyperliquid Agent Gateway
hypernatt-terminal is an MCP server published by DIALLOUBE-RESEARCH. Marketplaces we read that list it: 1 (Official MCP Registry). Hyperliquid Agent Gateway is an MCP server published by alekskram. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-04. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  hypernatt-terminal |  Hyperliquid Agent Gateway |
|---|---|---|
| Official MCP Registry | Listed Version: 2.8.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (PyPI): 391 Downloads/week (PyPI): 60 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | hypernatt-terminal | Hyperliquid Agent Gateway |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (hypernatt.com/mcp/protocol) | On your machine (hyperliquid-agent-gateway) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dialloube-research/hypernatt-terminal | github.com/alekskram/hyperliquid-agent-gateway |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 400 (4 days ago) | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
hypernatt-terminal
Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.
Hyperliquid Agent Gateway
Read-only MCP gateway to Hyperliquid: liquidation distance, funding carry, HyperEVM flows. No keys.
How to run each
hypernatt-terminal As a remote MCP server
claude mcp add --transport http hypernatt-terminal https://hypernatt.com/mcp/protocolHyperliquid Agent Gateway As a local MCP server: PyPI package
claude mcp add --transport stdio hyperliquid-agent-gateway -- uvx hyperliquid-agent-gatewayCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only hypernatt-terminal has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: hypernatt-terminal · What it can do: Hyperliquid Agent Gateway · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.