# io.github.qso-graph/n1mm-mcp (pypi · n1mm-mcp)

N1MM Logger+ MCP server. Live contest state: QSOs, bandmap, score, rate, multipliers.

- Trust score: 74/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `n1mm-mcp`
- Version: `0.2.1`
- 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**: 49/100
  - Malware scan not yet available for this package.
  - 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 16 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/n1mm-mcp).
  - Clear OSI-approved license (GPL-3.0-or-later).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1343 tokens (~111/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 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/n1mm-mcp server?

io.github.qso-graph/n1mm-mcp runs locally as a PyPI package, launched with uvx n1mm-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-n1mm-mcp -- uvx n1mm-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "qso-graph-n1mm-mcp": {
      "command": "uvx",
      "args": [
        "n1mm-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-17 (score 74, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-16 (score 89, +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-15 (score 88, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-14 (score 73, +39)

- [security improvement] Injection markers: unverified → pass
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.53
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 0.1.7 → 0.2.1

### 2026-10-13 (score 34, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.7 → 0.2.1

### 2026-10-12 (score 49, −20)

- [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.7 → 0.2.1

### 2026-10-05 (score 69, +1)

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

### 2026-10-04 (score 68, +2)

- [functional regression] Dependency health: 0.98 → 0.90
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 0.1.6 → 0.1.7

## MCP tools (12)

### `get_version_info` (~123 tokens)

Get Version Info

Get n1mm-mcp service version and upstream UDP contract version.

Returns the running PyPI version of n1mm-mcp and the N1MM Logger+
UDP broadcast contract revision in use. Use this to confirm fleet
alignment across MCP deployments — agents can compare service_version
and spec_version across servers to detect drift without going outside
the MCP protocol.

Note: n1mm_diagnostics remains the canonical health probe (heartbeat,
parse errors, memory). get_version_info is a lighter-weight identity
attestation that succeeds even when N1MM isn't broadcasting.

### `n1mm_current_state` (~71 tokens)

N1Mm Current State

Complete station snapshot — connection, contest, operator, radios.

Returns connection status, contest info, operator callsign, and full
radio state for Radio 1 (and Radio 2 if SO2R). This is the first tool
any AI session should call.

Input parameters:

- `station_name`

### `n1mm_lookup` (~75 tokens)

N1Mm Lookup

Pre-log callsign lookup — THE Contest-Copilot trigger.

Fires when operator types a callsign and presses spacebar in N1MM.
Returns the lookup data plus current band/mode from RadioInfo.
Check lookup_age_ms — if >30000, the advice window has closed.

Input parameters:

- `station_name`

### `n1mm_contacts` (~139 tokens)

N1Mm Contacts

QSO log — recent contacts, edits, and deletes.

Returns the last QSO, filtered recent QSOs, recent edits, and recent
deletes in one coherent snapshot.

Input parameters:

- `band`: Filter by band (e.g., "20m").
- `call_pattern`: Filter by callsign prefix.
- `count` (integer): Number of recent QSOs to return (default 10, max 100).
- `mode`: Filter by mode (e.g., "CW").
- `since`: ISO timestamp — return only QSOs after this time.
- `station_name`: Station to query (auto-detected if only one).

### `n1mm_bandmap` (~109 tokens)

N1Mm Bandmap

Live bandmap — spots, mult targets, and activity summary.

Returns active spots (with TTL eviction), unworked multipliers,
and per-band spot activity counts in one snapshot.

Input parameters:

- `band`: Filter by band (e.g., "20m").
- `callsign`: Search by callsign prefix.
- `mode`: Filter by mode.
- `mults_only` (boolean): If true, only return spots flagged as multipliers.
- `station_name`: Station to query.

### `n1mm_performance` (~106 tokens)

N1Mm Performance

Complete performance snapshot — score, rate, bands, run/S&P, timeline.

Returns score, rolling rates (10m/30m/60m), rate derivative for band
exhaustion detection, per-band breakdown, per-mode breakdown, hourly
summary, and run vs S&P stats in one coherent view.

Input parameters:

- `band`: Filter rate/breakdown to specific band.
- `mode`: Filter to specific mode.
- `station_name`: Station to query.

### `n1mm_multipliers` (~69 tokens)

N1Mm Multipliers

Multiplier status — worked mults, mult map, and available needs.

Returns total mults worked, per-band mult grid, unworked mults
currently spotted, and mult value analysis.

Input parameters:

- `band`: Filter to specific band.
- `station_name`: Station to query.

### `n1mm_clock` (~101 tokens)

N1Mm Clock

Contest clock — timing, off-time, and pacing in one view.

Input parameters:

- `duration_hours`: Contest length (e.g., 48 for CQ WW, 24 for ARRL DX).
- `min_gap_minutes` (integer): Minimum gap to count as off-time (default 30).
- `station_name`: Station to query.
- `target_qsos`: Target QSO count for pacing.
- `target_score`: Target score for pacing.

### `n1mm_so2r` (~164 tokens)

N1Mm So2R

Two-radio (SO2R) view: both radios now, and how they've been used.

Returns each radio's band, frequency, mode and run/transmit state, N1MM's transmit
focus and receive focus, whether both radios are on the same band, each radio's
share of N1MM-keyed transmit time (a paddle or PTT isn't reported by N1MM) and
minutes per band, transmit- and receive-focus swaps, QSOs per radio, and QSOs made
on one radio while the other was running. Timing covers the RadioInfo packets seen
since the MCP server started (or the contest changed). Read from N1MM's
broadcasts; no rig is read.

Input parameters:

- `station_name`

### `n1mm_network` (~133 tokens)

N1Mm Network

Every networked N1MM station at once (multi-op).

Per station: operator, radios (band, mode, running, transmitting), QSOs, rate over
10 and 60 minutes, mults in the last hour, minutes since the last QSO, the band of
its recent QSOs with minutes on it and band changes in the last hour, and when it
was last heard. Also: which stations are on each band, stations sharing a band
and mode, each station's contest score (shared per contest call), and QSOs per
operator this hour against the hour before.

### `n1mm_pileup` (~167 tokens)

N1Mm Pileup

DXpedition pileup view: rate, who's calling, dupes, split, dead air.

Over the last window_minutes (default 60, 5 to 1440): QSOs, unique calls, dupes
(a call already worked on that band and mode), run share, rate over 5, 15 and 60
minutes and the best 10 minutes in the window, QSOs and share by continent, the
top 10 country prefixes, QSOs by band and mode, gaps of 2 minutes or more between
QSOs, and the active radio's split (RX, TX, kHz up).

Input parameters:

- `station_name`: Station to query.
- `window_minutes` (integer): How far back to look, in minutes.

### `n1mm_diagnostics` (~48 tokens)

N1Mm Diagnostics

Server health and diagnostics — connection, parse errors, memory.

Essential for production debugging. First tool to call when something
goes wrong during a contest.

Input parameters:

- `station_name`

## Diagnostics

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

## Score history

- 2026-10-17: 74
- 2026-10-16: 89
- 2026-10-15: 88
- 2026-10-14: 73
- 2026-10-13: 34
- 2026-10-12: 49
- 2026-10-05: 69
- 2026-10-04: 68
- 2026-10-03: 66
- 2026-10-02: 66
- 2026-10-01: 66
- 2026-09-30: 66
- 2026-09-29: 66
- 2026-09-28: 66

## Common questions

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

io.github.qso-graph/n1mm-mcp is listed in the public MCP registry as io.github.qso-graph/n1mm-mcp. N1MM Logger+ MCP server. Live contest state: QSOs, bandmap, score, rate, multipliers. This page covers its PyPI package (n1mm-mcp).

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

io.github.qso-graph/n1mm-mcp scores 74 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/n1mm-mcp server expose?

io.github.qso-graph/n1mm-mcp exposes 12 tools: get_version_info, n1mm_current_state, n1mm_lookup, n1mm_contacts, n1mm_bandmap, and 7 more. Their descriptions and schemas cost roughly 1,305 tokens of context every time the server is loaded.

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

io.github.qso-graph/n1mm-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/n1mm-mcp server under?

io.github.qso-graph/n1mm-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/n1mm-mcp/
- Socket report: https://socket.dev/pypi/package/n1mm-mcp
- Repository: https://github.com/qso-graph/n1mm-mcp
- Changelog RSS feed: https://verifymcp.io/servers/qso-graph-n1mm-mcp/n1mm-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qso-graph-n1mm-mcp/n1mm-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qso-graph-n1mm-mcp/n1mm-mcp