Skip to main content
Glama
DIALLOUBE-RESEARCH

hypernatt-terminal

by DIALLOUBE-RESEARCH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to hypernatt-terminal

No user-submitted related servers found.

    Related Servers

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have largely distinct purposes: a discovery/manifest tool, a cross-chain swap, a BTC/ETH depth feed, and a liquidation radar. The two market-data tools (get_native_depth and get_liq_radar) both deliver market 'terrain/context' and are explicitly meant to be combined, so an agent could occasionally conflate them, but descriptions differentiate them well.

    Naming Consistency4/5

    Three of four tools use the get_<noun> pattern (get_agent_manifest, get_native_depth, get_liq_radar), which is predictable. swap_via_nattswap breaks the pattern with a swap_via_<provider> verb phrase, a minor deviation that is still readable.

    Tool Count4/5

    Four tools is a reasonable, well-scoped set for a focused market-data-plus-swap terminal: one discovery tool and three functional capabilities. It is on the lean side but each tool earns its place, with no obvious filler.

    Completeness4/5

    The surface covers discovery, market context (depth and liquidation terrain), and cross-chain swapping, with the swap returning actions to be signed externally, which is a coherent lifecycle for a read-only terminal. Minor gaps exist (e.g. no historical data, position/portfolio or wallet-signing tool), but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources