Skip to main content
Glama
qso-graph

n1mm-mcp

by qso-graph

Related Servers

Alternatives to n1mm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that controls WSJT-X for amateur radio weak-signal modes (FT8/FT4, etc.) via UDP, enabling observation of status and decodes, and transmit operations like replying to CQs or sending free text.
      14
      33 PyPI
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables logging amateur-radio QSOs to N3FJP logging software via MCP tools, including automatic logging, dupe checking, and band/mode management.
      10
      140 PyPI
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.
      8
      25 PyPI
      GPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.
      6
      3
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets an LLM operate an amateur radio shack: query live APRS traffic, predict satellite passes, schedule SDR captures, and monitor FT8/WSPR band activity.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for agents to control MultiViewer, the best way to watch motorsports. Works locally or remotely.
      19
      MIT

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct resources (contacts, bandmap, clock, lookup), but multiplier data bleeds across three tools: n1mm_bandmap (unworked mults), n1mm_performance (per-band breakdown), and n1mm_multipliers. The status trio of get_version_info, n1mm_current_state, and n1mm_diagnostics also overlap somewhat, though descriptions explicitly differentiate version attestation vs health probe vs full snapshot.

    Naming Consistency3/5

    Eight tools share an n1mm_ prefix but are bare noun phrases (n1mm_clock, n1mm_bandmap), while get_version_info drops the prefix entirely and is the only verb_noun name. Readable, but the convention is noticeably mixed across the set.

    Tool Count5/5

    Nine tools is well-scoped for a contest-station monitoring server, and each tool maps to a coherent domain area (state, contacts, bandmap, performance, multipliers, clock, health, identity). No tool appears redundant enough to remove.

    Completeness4/5

    The monitoring surface is comprehensive — live state, log, spots, rates, mults, clock, and diagnostics all covered. It is essentially read-only, with no control/write operations (e.g. logging a QSO, tuning radio, posting a spot), which is a modest gap if agents are meant to act rather than observe.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues