Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.qso-graph/netlogger-mcp

PYPI · NETLOGGER-MCP

NetLogger MCP server. Nets on the air, live check-ins and who's up, past nets.

Available components

+20 this week 90 Trust /100

Last scanned (23 hours ago)

Scores higher than 93% of PyPI servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to qso-graph/netlogger-mcp). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-or-later).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 534 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +55
    • Injection markers: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.53 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 0.1.4 → 0.2.0 functional
  • 13 Oct 26 0
    • Package version: 0.1.4 → 0.2.0 functional
  • 12 Oct 26 −36
    • Stability: 0.23 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.4 → 0.2.0 functional
    • Package version: 0.1.4 → 0.1.10 functional
  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.4 functional
    • Package version: 0.1.1 → 0.1.3 functional
    • Package version: 0.1.1 → 0.1.2 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed pypi/netlogger-mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo qso-graph/netlogger-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/qso-graph/netlogger-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3235981065
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1d9187e028e999de3a5e632d7ed2a82a5797c0e3e8ef18c500e02f3189cb0fe8

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 17 packages
Packages resolved 17
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~402 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_version_info ~37

Get netlogger-mcp's version, the NetLogger API version it is built for, and the version of the records it returns.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

netlogger_active_nets ~44

List nets on the air now.

NameTypeReqDescription
name_like––Only nets whose name contains this text, ignoring case (e.g. ARES). Empty for all.

Structured output declared, but exposes no named fields.

No examples provided.

netlogger_checkins ~81

Get a live net's check-in list, and the pointer: the serial number of the station net control is working now.

NameTypeReqDescription
net_namestringyesThe net's name, from netlogger_active_nets.
server_namestringyesThe net's server, from netlogger_active_nets (e.g. NETLOGGER2).

Structured output declared, but exposes no named fields.

No examples provided.

netlogger_past_checkins ~80

Get a closed net's check-in list.

NameTypeReqDescription
net_idstringyesThe net ID, from netlogger_past_nets.
net_namestringyesThe net's name, from netlogger_past_nets.
server_namestringyesThe net's server, from netlogger_past_nets.

Structured output declared, but exposes no named fields.

No examples provided.

netlogger_past_nets ~78

List closed nets over the last few days, with the net IDs netlogger_past_checkins needs.

NameTypeReqDescription
interval_days––How many days back (default 7). Over 7 needs name_like (NetLogger's rule).
name_like––Only nets whose name contains this text (e.g. ARES).

Structured output declared, but exposes no named fields.

No examples provided.

netlogger_set_callsign ~82

Save the user's amateur radio callsign. Needed once, before the first lookup. NetLogger is told which station is asking, in every request, so it can tell one user from another. Ask the user for their own callsign; don't guess it.

NameTypeReqDescription
callsignstringyesThe user's callsign (e.g. KI7MT).

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.qso-graph/netlogger-mcp server?

io.github.qso-graph/netlogger-mcp runs locally as a PyPI package, launched with uvx netlogger-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · netlogger-mcp

# add to Claude Code
claude mcp add qso-graph-netlogger-mcp -- uvx netlogger-mcp
Common questions

What is the io.github.qso-graph/netlogger-mcp server?

io.github.qso-graph/netlogger-mcp is listed in the public MCP registry as io.github.qso-graph/netlogger-mcp. NetLogger MCP server. Nets on the air, live check-ins and who's up, past nets. This page covers its PyPI package (netlogger-mcp).

Is the io.github.qso-graph/netlogger-mcp server safe to use?

io.github.qso-graph/netlogger-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.qso-graph/netlogger-mcp server expose?

io.github.qso-graph/netlogger-mcp exposes 6 tools: get_version_info, netlogger_set_callsign, netlogger_active_nets, netlogger_checkins, netlogger_past_nets, netlogger_past_checkins. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.

Is the io.github.qso-graph/netlogger-mcp server still maintained?

io.github.qso-graph/netlogger-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.qso-graph/netlogger-mcp server under?

io.github.qso-graph/netlogger-mcp declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.