Skip to content

hypernatt-terminal MCP server

io.github.DIALLOUBE-RESEARCH/hypernatt-terminalDIALLOUBE-RESEARCHstreamable-httpv2.10.0Scanned

Liquidation radar, recorded BTC/ETH depth and flow, Li.Fi swaps, L2 archive catalog. 5 tools; x402.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the hypernatt-terminal MCP server can do

The hypernatt-terminal MCP server is published by the GitHub account DIALLOUBE-RESEARCH. It has 5 tools. It can create or change data (2 tools: get_agent_manifest and swap_via_nattswap), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (get_native_depth and get_liq_radar).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 2.10.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • get_agent_manifestStart here (free): 5 tools, prices, daily per-tool/per-token trial status and intent-based journeys.No findings

    Why it is in this group

    • The name "get_agent_manifest" says "get": a word for reading.
    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    Start here (free): 5 tools, prices, daily per-tool/per-token trial status and intent-based journeys. Choose liquidation radar, native BTC/ETH depth, Li.Fi swap or the L2 archive catalog. Compact includes arguments; detail=full adds quota/pass/onboarding.
  • swap_via_nattswapCross-chain token swap powered by Li.Fi across 70+ chains incl.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. MCP free; on-chain swap costs gas + HyperNatt 0.25% integrator fee (Li.Fi may add its own cut — read quote.estimate.feeCosts). Side effects: MCP read-only until wallet signs.
Only reads 3Show 3 read-only tools
  • get_l2_archive_catalogFree, read-only.No findings

    Why it is in this group

    • The name "get_l2_archive_catalog" says "get": a word for reading.
    Description, as the server wrote it
    Free, read-only. USE WHEN an agent needs historical raw Hyperliquid L2 order-book data for BTC or ETH: returns the catalog of the sealed archive (coverage, files, SHA-256, free 24h sample under CC BY 4.0, offers, x402 purchase endpoints, terms). Same JSON as https://hypernatt.com/api/datasets/catalog. NOT WHEN the agent needs live market data (use get_liq_radar or get_native_depth). No arguments; no payment; nothing is bought by calling it.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false
  • get_liq_radarReturns the liquidation map of one coin (BTC, ETH, SOL, BNB, XRP, HYPE or ZEC; default BTC).Reads text others writeNo findings

    Why it is in this group

    • The name "get_liq_radar" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Returns the liquidation map of one coin (BTC, ETH, SOL, BNB, XRP, HYPE or ZEC; default BTC). If cluster_grammar is present, read it first: class=noise (distance <3%) is high-leverage bait to ignore; class=true (~7%+) is the low-leverage stack. The liq_radar block (hypernatt_liq_radar_v2) holds modeled liquidation clusters (zones where leveraged positions may liquidate), observed real_liquidations, open interest (OI) and long/short (L/S) context, and magnet.score (directional density bias from OI, L/S and funding; not a hit probability). USE WHEN an agent needs liquidation terrain for timing or sizing. NOT WHEN it needs order-book depth for a BTC/ETH size (use get_native_depth) or a swap (use swap_via_nattswap). Read-only; terrain, not a trade signal. Price: 0.001 USDC/call via x402 (Base or Solana) or eligible credits.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • get_native_depthBTC/ETH perpetual market context: four simultaneous recorded liquidity views (REF, M2, M5, AGG4), size coverage, fixed-price wall changes and observed aggressor buy/sell flow over …Reads text others writeNo findings

    Why it is in this group

    • The name "get_native_depth" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    BTC/ETH perpetual market context: four simultaneous recorded liquidity views (REF, M2, M5, AGG4), size coverage, fixed-price wall changes and observed aggressor buy/sell flow over 30s or 300s. Aggregated views see wider price ranges at coarser precision; never add their overlapping volumes. Combine with liquidation radar. Read agent_readout and quality first. No strategy signal, full-book claim or fill guarantee. Price: 0.001 USDC/call via existing x402 Base/Solana or eligible credits.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
yes
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hypernatt.com/mcp/protocol: tools/list returned 5 tools to an anonymous client, including get_agent_manifest (write), swap_via_nattswap (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 4 changed.+1 added~4 changedView diff

Install

Pinned to version 2.10.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hypernatt-terminal https://hypernatt.com/mcp/protocol
claude mcp add --transport http hypernatt-terminal https://hypernatt.com/mcp/protocol

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hypernatt-terminal__get_l2_archive_catalog",
      "mcp__hypernatt-terminal__get_native_depth",
      "mcp__hypernatt-terminal__get_liq_radar"
    ],
    "ask": [
      "mcp__hypernatt-terminal__get_agent_manifest",
      "mcp__hypernatt-terminal__swap_via_nattswap"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hypernatt-terminal. Review it before you use it.

Capability tags behind 2 rules
  • mcp__hypernatt-terminal__get_native_depth untrusted-input
  • mcp__hypernatt-terminal__get_liq_radar untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.DIALLOUBE-RESEARCH/hypernatt-terminal/verify?hash=ac727359cf40c4cfa9bd8afef6528f1ef66b878ee2f99cd0b2f0cfd90a0a6785" | jq -e '.changed == false'

Pinned hash ac727359cf40, from Nov 12, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.DIALLOUBE-RESEARCH/hypernatt-terminal/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.DIALLOUBE-RESEARCH/hypernatt-terminal
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.DIALLOUBE-RESEARCH/hypernatt-terminal.svg)](https://radar.anlyon.com/servers/io.github.DIALLOUBE-RESEARCH/hypernatt-terminal)

Source: MCP Registry · repository. Synced Nov 12, 2026, 02:17 UTC.

hypernatt-terminal MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the hypernatt-terminal MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the hypernatt-terminal MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the hypernatt-terminal MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the hypernatt-terminal MCP server have?

5 tools: 2 write, 3 read. get_agent_manifest, swap_via_nattswap, get_l2_archive_catalog, get_native_depth and get_liq_radar.

Does the hypernatt-terminal MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the hypernatt-terminal MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the hypernatt-terminal MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.