Skip to main content
Glama
qso-graph

netlogger-mcp

by qso-graph

Related Servers

Alternatives to netlogger-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables users to query live N1MM Logger+ contest state over UDP broadcasts, including recent QSO logs, bandmap spots, multiplier needs, score and rate, off-time pacing, and server diagnostics. Supports multiple stations and works with any MCP-compatible client through stdio or streamable HTTP.
      9
      157 PyPI
      GPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying a local SQLite index of FCC ULS licensing data to look up licenses by callsign, licensee, or FRN, find licensed transmitter sites near a coordinate, and see who is authorized on a frequency or band. Runs over STDIO or Streamable HTTP with no API key required at request time.
      61 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides read-only access to cached metadata of public activities, contests, and competitions from multiple sources via SQLite, enabling search and listing without hitting external sites.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for ARRL Logbook of The World (LoTW) that enables querying confirmations, uploaded QSOs, DXCC credits, and user activity through any MCP-compatible AI assistant. Part of the qso-graph project, it is read-only and requires LoTW credentials for authenticated tools.
      6
      221 PyPI
      1
      GPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Serves read-only archived ResMed CPAP data from a local SQLite database, enabling MCP clients to query nightly summaries, raw signals, and sync status over the LAN.
      183 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: version info, user setup, active nets, live check-ins, past nets, and past check-ins. No two tools overlap in function, and descriptions make the active/live vs past/closed distinction explicit.

    Naming Consistency4/5

    All tool names use snake_case, and five of six follow a netlogger_verb_noun pattern. The lone get_version_info breaks the prefix convention, but the deviation is minor and doesn't hinder readability.

    Tool Count5/5

    Six tools is a well-scoped set for a read-only NetLogger client, covering setup, discovery, and retrieval for both active and past nets. Each tool earns its place without redundancy.

    Completeness4/5

    The surface covers version info, user identification, active/past net listing, and check-in retrieval, which is a complete read lifecycle. However, there is no tool to submit a check-in or retrieve detailed net metadata, which may be a gap depending on intended use.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive