Skip to main content
Glama
qso-graph

netlogger-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to netlogger-mcp

No user-submitted related servers found.

    Related Servers

    • activities-mcp

      kyowon1108
      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
      -

    • lotw-mcp

      qso-graph
      A
      license
      A
      quality
      C
      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
      1
      GPL 3.0

    • ResMed-Data-MCP

      sfls1397
      A
      license
      Not graded
      quality
      C
      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.
      151 npm
      MIT

    • mcp-local-redes

      FerAHMz
      F
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that exposes fleet telemetry queries as tools for language models, enabling natural language questions about vehicle positions, trips, and alerts. Runs on the operator's machine and returns aggregated results from a SQLite database.
      -
    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.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

    Resources