io.github.qso-graph/n1mm-mcp
PYPI · N1MM-MCP
N1MM Logger+ MCP server. Live contest state: QSOs, bandmap, score, rate, multipliers.
Available components
Last scanned (9 minutes ago)
Scores higher than 74% of PyPI servers
Category Entertainment and Games
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 Security49
- Malware scan not yet available for this package.Unverified
- 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 16 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/n1mm-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
- 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 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.
- 15 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 +39
- Injection markers: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.53 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.7 → 0.2.1 functional
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.7 → 0.2.1 functional
- 12 Oct 26 −20
- 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.7 → 0.2.1 functional
- 5 Oct 26 +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.
- 4 Oct 26 +2
- Dependency health: 0.98 → 0.90 ▼ functional
- Stability: unverified → 0.20 ▲ functional
- Package version: 0.1.6 → 0.1.7 functional
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 17 Oct 2026 · Analysed pypi/n1mm-mcp@0.2.1
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/n1mm-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/n1mm-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3197590365 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5b70f61b862d09b2ad103a8dfda930c8b3d70b025b8f2b081a046208779e4a0f |
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 16 packages
| Packages resolved | 16 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_version_info Get Version Info ~123
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_bandmap N1Mm Bandmap ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_clock N1Mm Clock ~101
Contest clock — timing, off-time, and pacing in one view.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_contacts N1Mm Contacts ~139
QSO log — recent contacts, edits, and deletes. Returns the last QSO, filtered recent QSOs, recent edits, and recent deletes in one coherent snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_current_state N1Mm Current State ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| station_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_diagnostics N1Mm Diagnostics ~48
Server health and diagnostics — connection, parse errors, memory. Essential for production debugging. First tool to call when something goes wrong during a contest.
| Name | Type | Req | Description |
|---|---|---|---|
| station_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_lookup N1Mm Lookup ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| station_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_multipliers N1Mm Multipliers ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter to specific band. |
| station_name | – | – | Station to query. |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_network N1Mm Network ~133
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_performance N1Mm Performance ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter rate/breakdown to specific band. |
| mode | – | – | Filter to specific mode. |
| station_name | – | – | Station to query. |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_pileup N1Mm Pileup ~167
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).
| Name | Type | Req | Description |
|---|---|---|---|
| station_name | – | – | Station to query. |
| window_minutes | integer | – | How far back to look, in minutes. |
Structured output declared, but exposes no named fields.
No examples provided.
n1mm_so2r N1Mm So2R ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| station_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · n1mm-mcp
claude mcp add qso-graph-n1mm-mcp -- uvx n1mm-mcp
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.