hypernatt-terminal
REMOTE · HYPERNATT.COM · 2 COMPONENTS · SCANNED SEP 20
Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 867 tokens (~216/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the hypernatt-terminal MCP server?
hypernatt-terminal is a hosted endpoint at https://hypernatt.com/mcp/protocol, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hypernatt.com
claude mcp add --transport http dialloube-research-hypernatt-terminal 'https://hypernatt.com/mcp/protocol'
{
"mcpServers": {
"dialloube-research-hypernatt-terminal": {
"url": "https://hypernatt.com/mcp/protocol"
}
}
} {
"servers": {
"dialloube-research-hypernatt-terminal": {
"type": "http",
"url": "https://hypernatt.com/mcp/protocol"
}
}
} [mcp_servers.dialloube-research-hypernatt-terminal] url = "https://hypernatt.com/mcp/protocol"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dialloube-research-hypernatt-terminal": {
"type": "remote",
"url": "https://hypernatt.com/mcp/protocol",
"enabled": true
}
}
} openclaw mcp add dialloube-research-hypernatt-terminal --url 'https://hypernatt.com/mcp/protocol' --transport streamable-http
mcp_servers:
dialloube-research-hypernatt-terminal:
url: "https://hypernatt.com/mcp/protocol" {
"McpServers": {
"dialloube-research-hypernatt-terminal": {
"Transport": "http",
"Url": "https://hypernatt.com/mcp/protocol"
}
}
} assistant mcp add dialloube-research-hypernatt-terminal -t streamable-http -u 'https://hypernatt.com/mcp/protocol'
{
"mcpServers": {
"dialloube-research-hypernatt-terminal": {
"type": "http",
"url": "https://hypernatt.com/mcp/protocol"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Tool “reconcile_execution” was removed ▼ security
- Tool “get_execution_quote” was removed ▼ security
- Tool “compare_execution_context” was removed ▼ security
- Tool “get_agent_manifest” rewrote its description, which is the text the model reads security
- Tool coverage: 84% → 95% ▲ functional
- Schema quality: 1306 → 867 ▲ functional
- Server version: 2.8.0 → 2.9.1 functional
- New tool “get_native_depth” functional
- 14 Sept 26 −1
- Tool “get_agent_manifest” rewrote its description, which is the text the model reads security
- Schema quality: 630 → 1306 ▼ functional
- Tool coverage: 100% → 84% ▼ functional
- Server version: 2.7.0 → 2.8.0 functional
- New tool “compare_execution_context” functional
- New tool “get_execution_quote” functional
- New tool “reconcile_execution” functional
- 6 Sept 26 +11
- Stability: fail → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
- “get_liq_radar” reworded the description of “x_payment” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 17 Aug 26 0
- Tool “swap_via_nattswap” rewrote its description, which is the text the model reads security
- Tool “get_liq_radar” rewrote its description, which is the text the model reads security
- Tool “get_agent_manifest” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “get_agent_manifest” added an optional parameter “detail” cosmetic
- “get_agent_manifest” reworded the description of “locale” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Tool “get_liq_radar” rewrote its description, which is the text the model reads security
- Tool “get_agent_manifest” rewrote its description, which is the text the model reads security
- Schema quality: fair → poor functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://hypernatt.com/mcp/protocol
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hypernatt.com | CN=YE2,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6f7577353f651a8b2a5b8c7d716c0a45c32 |
| SANs: api.hypernatt.com, hypernatt.com, www.hypernatt.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hypernatt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hypernatt.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hypernatt.com/mcp/protocol | Verified | 200 | |
| http (plaintext) | http://hypernatt.com/mcp/protocol | HTTPS enforced | 301 | https://hypernatt.com/mcp/protocol |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agent_manifest ~95
Start here (free): 4 tools, prices, daily per-tool/per-token trial status and intent-based journeys. Choose liquidation radar, native BTC/ETH depth or Li.Fi swap. Compact includes arguments; detail=full adds quota/pass/onboarding.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Default compact. full = quota/pass/onboarding. |
| locale | string | – | Not a translation switch. Ignored. Catalog is English only. |
No output schema declared.
No examples provided.
get_liq_radar ~268
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 BNB XRP HYPE ZEC (omit=BTC). USE WHEN: terrain / timing / sizing. NOT a trade signal. RETURNS: hypernatt_liq_radar_v2. COST: $0.001 x402 (Base or Solana). Side effects: none.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_wallet | string | – | Optional EVM wallet (0x + 40 hex). Skips x402 when swap-earned quota balance covers this tool's credit weight. |
| symbol | string | – | Optional crypto symbol (BTC ETH SOL BNB XRP HYPE ZEC). Default BTC when omitted. |
| x_payment | string | – | Base64 x402 USDC payment. Rails: Base eip155:8453 (EIP-3009) OR Solana SVM exact (@x402/svm; not an EVM signature). Omit on first call to receive 402 accepts[]; retry after paying $0.001/call. |
No output schema declared.
No examples provided.
get_native_depth ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_wallet | string | – | Optional wallet for credits. Never a private key. |
| lookback_s | number | – | Fixed-price wall history and observed flow window, 30 or 300 seconds; default 300. |
| quantity_base | string | yes | Token base units, not USDC. |
| side | string | yes | – |
| symbol | string | yes | BTC or ETH only. |
| x_payment | string | – | x402 Base or Solana payment. Omit first to discover 402. |
No output schema declared.
No examples provided.
swap_via_nattswap ~281
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.5% integrator fee (Li.Fi may add its own cut — read quote.estimate.feeCosts). Side effects: MCP read-only until wallet signs.
| Name | Type | Req | Description |
|---|---|---|---|
| fromAddress | string | yes | Sender wallet 0x + 40 hex chars |
| fromAmount | string | yes | Amount in token smallest units (wei for 18-decimal tokens) |
| fromChain | number|string | yes | Source Li.Fi chain id (e.g. 1 Ethereum, 8453 Base, 42161 Arbitrum) |
| fromToken | string | yes | Source token contract address on fromChain |
| slippage | number | – | Max slippage percent (e.g. 0.5 for 0.5%) |
| toAddress | string | yes | Recipient wallet 0x + 40 hex chars |
| toChain | number|string | yes | Destination Li.Fi chain id |
| toToken | string | yes | Destination token contract address on toChain |
No output schema declared.
No examples provided.
What is the hypernatt-terminal MCP server?
hypernatt-terminal is an MCP server listed in the public MCP registry as io.github.DIALLOUBE-RESEARCH/hypernatt-terminal. Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments. This page covers its hosted endpoint (https://hypernatt.com/mcp/protocol).
Is the hypernatt-terminal MCP server safe to use?
hypernatt-terminal scores 78 out of 100 on VerifyMCP. 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.
What tools does the hypernatt-terminal MCP server expose?
hypernatt-terminal exposes 4 tools: get_agent_manifest, swap_via_nattswap, get_native_depth, get_liq_radar. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.
Does the hypernatt-terminal MCP server require authentication?
No. We connected to hypernatt-terminal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the hypernatt-terminal MCP server still maintained?
hypernatt-terminal is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.