hypernatt-terminal is an MCP server with 3 tools an agent can call, among them get_agent_manifest, get_liq_radar, swap_via_nattswap. It answers at https://hypernatt.com/mcp/protocol over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 6 times since 11 September 2026; the last check, on 19 October 2026, succeeded.
Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_agent_manifest | Start here (free, compact): 3 tools + prices + cluster do_not + honest usage. Pass detail=full for quota/pass/onboarding. Then get_liq_radar. Inputs: locale, detail |
get_liq_radar | If cluster_grammar is present, read it before liq_radar. class=noise (<3%) is high-leverage bait — ignore. class=true (~7%+) is the low-leverage stack. Terrain, not a signal. Also magnet, OI, L/S, clusters, real liqs. Whitelist BTC ETH SOL Inputs: x_payment, agent_wallet, symbol |
swap_via_nattswap | Cross-chain token swap powered by Li.Fi across 70+ chains incl. Hyperliquid. USE WHEN: bridge, fund gas, treasury routing, or rebalance. RETURNS: Li.Fi route + execution_readiness + swap_actions_v1. Prefer signing swap_actions_v1 in order. Inputs: fromChain, toChain, fromToken, toToken, fromAmount, fromAddress |
Every block below points at https://hypernatt.com/mcp/protocol. Pick your client and copy.
claude mcp add --transport http hypernatt-terminal https://hypernatt.com/mcp/protocol
{
"mcpServers": {
"hypernatt-terminal": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://hypernatt.com/mcp/protocol"]
}
}
}{
"mcpServers": {
"hypernatt-terminal": {
"url": "https://hypernatt.com/mcp/protocol"
}
}
}{
"servers": {
"hypernatt-terminal": {
"type": "http",
"url": "https://hypernatt.com/mcp/protocol"
}
}
}{
"context_servers": {
"hypernatt-terminal": {
"url": "https://hypernatt.com/mcp/protocol"
}
}
}{
"mcpServers": {
"hypernatt-terminal": {
"serverUrl": "https://hypernatt.com/mcp/protocol"
}
}
}{
"mcpServers": {
"hypernatt-terminal": {
"url": "https://hypernatt.com/mcp/protocol"
}
}
}name: hypernatt-terminal
version: 0.0.1
schema: v1
mcpServers:
- name: hypernatt-terminal
type: streamable-http
url: https://hypernatt.com/mcp/protocol{
"mcpServers": {
"hypernatt-terminal": {
"httpUrl": "https://hypernatt.com/mcp/protocol"
}
}
}{
"mcpServers": {
"hypernatt-terminal": {
"type": "http",
"url": "https://hypernatt.com/mcp/protocol"
}
}
}{
"mcpServers": {
"hypernatt-terminal": {
"url": "https://hypernatt.com/mcp/protocol"
}
}
}goose://extension?url=https%3A%2F%2Fhypernatt.com%2Fmcp%2Fprotocol&type=streamable_http&id=hypernatt-terminal&name=hypernatt-terminal
It answered our last check on 19 October 2026 in 134 ms. Over 6 checks since 11 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 12 September 2026: get_agent_manifest, get_liq_radar, swap_via_nattswap.
It answered our last check on 19 October 2026 in 134 ms. Over 6 checks since 11 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://hypernatt.com/mcp/protocol. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.dialloube-research. Endpoint host: hypernatt.com. ARD identifier: urn:air:io.github.dialloube-research:mcp:hypernatt-terminal.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.