netlogger-mcp
Related Servers
Alternatives to netlogger-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables 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.1285 PyPIGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.114 npm1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP 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-
- AlicenseAqualityDmaintenanceExposes real-time ADS-B aircraft data from a feeder, enabling natural language queries for aircraft positions, receiver statistics, and flight searches.69GPL 3.0
- AlicenseAqualityAmaintenanceMCP 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.675 PyPI1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceServes 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.77 npmMIT
TDQS
Scored across 6 tools
The active/past net and active/past check-in pairs are the only potential confusion points, but descriptions explicitly say "live" vs "closed," so an agent can choose correctly. get_version_info and netlogger_set_callsign are clearly separate from the lookup tools.
Five tools use clean snake_case and four share a netlogger_ prefix, forming a readable family. Minor deviations: get_version_info drops the prefix, and set_callsign is the only verb-first name while the rest are adjective_noun.
Six tools is well-scoped for a focused read-only NetLogger client, with one tool per operation. Nothing feels padded or missing at this size.
The core lifecycle is covered: set callsign, discover live/past nets, and pull live/past check-in lists with the pointer for current activity. Minor gaps: no net metadata (frequency, net control) or per-station history beyond the raw check-in list, but agents can work around these.