Is the Dialloube Research Hypernatt Terminal MCP server down?

mcp-registry/io.github.dialloube-research/hypernatt-terminal · v2.9.1

Also listed as awesome/dialloube-research/hypernatt-terminal

healthy
Last checked 2026-10-19 00:31 UTC · handshake 694ms

As of 2026-10-19 00:31 UTC, the Dialloube Research Hypernatt Terminal MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.6%
checks observed
3,765
outages (90d)
16
tools
9

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

Install Dialloube Research Hypernatt Terminal MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "dialloube-research-hypernatt-terminal-mc": {
      "type": "http",
      "url": "https://hypernatt.com/mcp/protocol"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 2 warning(s) across 4 tool(s); ~1,270 tokens of tool definitions.
Scores higher than 32% of 15,325 MCP servers Glimind has audited.
Its tool list costs an agent ~1,270 tokens per session — lighter than 65% of servers.
78 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints38
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_native_depth

Handshake + tools/list takes ~2,324 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

3 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_agent_manifest, get_liq_radar, swap_via_nattswap

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal/fixes

get_agent_manifest 1 change
{
  "name": "get_agent_manifest",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "detail": {
        "enum": [
          "compact",
          "full"
        ],
        "type": "string",
        "description": "Default compact. full = quota/pass/onboarding."
      },
      "locale": {
        "type": "string",
        "description": "Not a translation switch. Ignored. Catalog is English only."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_liq_radar 1 change
{
  "name": "get_liq_radar",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "symbol": {
        "enum": [
          "BTC",
          "ETH",
          "SOL",
          "BNB",
          "XRP",
          "HYPE",
          "ZEC"
        ],
        "type": "string",
        "description": "Optional crypto symbol (BTC ETH SOL BNB XRP HYPE ZEC). Default BTC when omitted."
      },
      "x_payment": {
        "type": "string",
        "description": "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."
      },
      "agent_wallet": {
        "type": "string",
        "description": "Optional EVM wallet (0x + 40 hex). Skips x402 when swap-earned quota balance covers this tool's credit weight."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.dialloube-research/hypernatt-terminal"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.dialloube-research/hypernatt-terminal"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal.svg)](https://glimind.com/server/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.dialloube-research%2Fhypernatt-terminal?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ac10cfa5c8479f1a…, first seen 2026-10-17, included at leaf 11509 of 24,012. Version history · verify what your client received.

Tools (9)

Compare: most reliable other servers · most reliable finance servers · most reliable data servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Dialloube Research Hypernatt Terminal MCP server down right now?

As of 2026-10-19 00:31 UTC, the Dialloube Research Hypernatt Terminal MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Dialloube Research Hypernatt Terminal MCP server provide?

Dialloube Research Hypernatt Terminal MCP server advertises 9 tools, including get_agent_manifest, get_cycle_signal, get_hunt_score, get_liq_radar, get_liquidation_radar.

How do I install Dialloube Research Hypernatt Terminal MCP server?

Point your MCP client at this streamable-http endpoint: https://hypernatt.com/mcp/protocol

Is the Dialloube Research Hypernatt Terminal MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Dialloube Research Hypernatt Terminal MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve