Other · Remote MCP server

hypernatt-terminal

Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.DIALLOUBE-RESEARCH/hypernatt-terminal
Version
2.8.0
Status
Active
Category
other
Transport
Streamable HTTP, SSE (HTTP + Server-Sent Events)
Published
2026-09-14
Updated
2026-09-14
Publisher
DIALLOUBE-RESEARCH (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/DIALLOUBE-RESEARCH) · how
Repository
github.com/DIALLOUBE-RESEARCH/hypernatt-terminal
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://hypernatt.com/mcp/protocolNone
SSE (HTTP + Server-Sent Events)https://hypernatt.com/mcp/sseNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Endpoint
https://hypernatt.com/mcp/protocol (HTTP)
Reachable
Yes (HTTP 200)
Handshake
hypernatt-terminal 2.9.1 · protocol 2025-06-18
Tools discovered
4: get_agent_manifest, swap_via_nattswap, get_native_depth, get_liq_radar
Checked on
2026-10-05
Endpoint
https://hypernatt.com/mcp/sse (SSE)
Reachable
Yes (HTTP 200)
SSE stream
Opened and named its message endpoint (not used further)
Checked on
2026-10-05

How the live check works

How to connect hypernatt-terminal

hypernatt-terminal is a remote MCP server: there is nothing to install. Its endpoint is https://hypernatt.com/mcp/protocol, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

It also lists an endpoint on the older SSE transport https://hypernatt.com/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Hyperliquid Funding Rates APIHL perp funding rates for 229 markets. Sort, history, arb opportunities. x402.Remote · SSELive check: ✗ no handshakehl-funding.api.klymax402.com
Hyperliquid Vaults APIHyperliquid vault summaries - APR, TVL, PnL, followers, sorted by performance. x402.Remote · SSELive check: ✗ no handshakehl-vaults.api.klymax402.com
Hypermarrow MCPLocal-first AI memory MCP server. Record, recall and consolidate memory on your own machine.Local · stdionpm: hypermarrow-mcp
Hypermnesia MCPPersistent memory for AI agents - 36 cited neuroscience mechanisms, local-first, hybrid retrieval.Local · stdioPyPI: hypermnesia-mcp
Hypertool MCPDynamically expose tools from proxied servers based on an Agent Persona.Local · stdionpm: @toolprint/hypertool-mcp
HypertuneEvaluate and inspect your Hypertune feature flags from your AI assistant.Remote · HTTPLive check: ✓ handshakehypertune.usefulapi.io
HyperXosist-Agent Remote MCPX feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs.Remote · HTTPLive check: ✓ handshakemcp.kgninja.dev
Hypr Cua MCPHyprland/Wayland computer-use MCP: grim screenshots + uinput click/type + hyprctl targeting.Local · stdioPyPI: hypr-cua-mcp