hypernatt-terminal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | 8011 | |
| GATEWAY_URL | No | https://hypernatt.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_manifestA | Start here (free): catalog of 3 terminal tools + value_proposition_v1 + use_scenarios_v1 + glossary_v1 under agent_interpretation_rules_v1. Then call get_liq_radar for the forced-order map. |
| swap_via_nattswapA | 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 + recommended_action. Prefer signing swap_actions_v1 in order. MCP free; on-chain swap costs gas + integrator fee. Side effects: MCP read-only until wallet signs. |
| get_liq_radarA | Forced-order / liquidation map — magnet bias, OI build-up, L/S ratio, clusters above/below, real liqs 1h/24h. Whitelist BTC ETH SOL BNB XRP HYPE ZEC (omit symbol = BTC). Market structure classic public indicators do not show. USE WHEN: terrain / timing / sizing context. NOT a trade signal or Fuel Score. RETURNS: hypernatt_liq_radar_v2. COST: $0.001 x402 (Base or Solana). Side effects: none. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: the manifest is a starting guide, swap_via_nattswap handles token exchanges, and get_liq_radar provides market liquidation data. There is no overlap or ambiguity between them.
Names mostly follow a verb_noun pattern (get_agent_manifest, get_liq_radar) with one deviation (swap_via_nattswap). The style is consistent with underscores and lowercase, so it remains readable and predictable.
With 3 tools, the server is well-scoped for a specialized terminal. Each tool serves a necessary role: discovery, data, and action, and the count is within the ideal 3-15 range.
The set offers a complete lifecycle for a terminal: a manifest to start, a data tool for market context, and an action tool for swaps. Minor gaps like balance checks or additional market data are possible but not essential for the stated purpose.