# 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.

- Trust score: 90/100 (high trust)
- Change this week: +20
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `netlogger-mcp`: 90/100 (this document), [markdown](https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp.md), [page](https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp)

## Channel facts

- Registry: `pypi`
- Package: `netlogger-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

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

## 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.

### Claude

```bash
claude mcp add qso-graph-netlogger-mcp -- uvx netlogger-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "qso-graph-netlogger-mcp": {
      "command": "uvx",
      "args": [
        "netlogger-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "qso-graph-netlogger-mcp": {
      "command": "uvx",
      "args": [
        "netlogger-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add qso-graph-netlogger-mcp -- uvx netlogger-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qso-graph-netlogger-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "netlogger-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qso-graph-netlogger-mcp --command uvx --arg netlogger-mcp
```

### Hermes

```yaml
mcp_servers:
  qso-graph-netlogger-mcp:
    command: "uvx"
    args: ["netlogger-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "qso-graph-netlogger-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "netlogger-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add qso-graph-netlogger-mcp -t stdio -c uvx -a netlogger-mcp
```

### Other

```json
{
  "mcpServers": {
    "qso-graph-netlogger-mcp": {
      "command": "uvx",
      "args": [
        "netlogger-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 90, +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.

### 2026-10-14 (score 89, +55)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.53
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 0.1.4 → 0.2.0

### 2026-10-13 (score 34, 0)

- [functional] Package version: 0.1.4 → 0.2.0

### 2026-10-12 (score 34, −36)

- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] 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

### 2026-10-04 (score 70, +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.

### 2026-10-02 (score 69, +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.

### 2026-09-30 (score 68, +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.

### 2026-09-29 (score 67, 0)

- [functional improvement] 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

## MCP tools (6)

### `get_version_info` (~37 tokens)

Get Version Info

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

### `netlogger_set_callsign` (~82 tokens)

Netlogger Set Callsign

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.

Input parameters:

- `callsign` (string, required): The user's callsign (e.g. KI7MT).

### `netlogger_active_nets` (~44 tokens)

Netlogger Active Nets

List nets on the air now.

Input parameters:

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

### `netlogger_checkins` (~81 tokens)

Netlogger Checkins

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

Input parameters:

- `net_name` (string, required): The net's name, from netlogger_active_nets.
- `server_name` (string, required): The net's server, from netlogger_active_nets (e.g. NETLOGGER2).

### `netlogger_past_nets` (~78 tokens)

Netlogger Past Nets

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

Input parameters:

- `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).

### `netlogger_past_checkins` (~80 tokens)

Netlogger Past Checkins

Get a closed net's check-in list.

Input parameters:

- `net_id` (string, required): The net ID, from netlogger_past_nets.
- `net_name` (string, required): The net's name, from netlogger_past_nets.
- `server_name` (string, required): The net's server, from netlogger_past_nets.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp#diagnostics

## Score history

- 2026-10-17: 90
- 2026-10-16: 90
- 2026-10-15: 89
- 2026-10-14: 89
- 2026-10-13: 34
- 2026-10-12: 34
- 2026-10-05: 70
- 2026-10-04: 70
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 68
- 2026-09-30: 68
- 2026-09-29: 67
- 2026-09-28: 67

## 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 17 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 17 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.

## Links

- PyPI project: https://pypi.org/project/netlogger-mcp/
- Socket report: https://socket.dev/pypi/package/netlogger-mcp
- Repository: https://github.com/qso-graph/netlogger-mcp
- Changelog RSS feed: https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qso-graph-netlogger-mcp/netlogger-mcp