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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources