io.github.qso-graph/adif-mcp
PYPI · ADIF-MCP
ADIF 3.1.7 spec engine for amateur radio logs: validation, parsing, enumerations, geospatial.
Available components
Last scanned (20 hours ago)
Scores higher than 93% of PyPI servers
Category Health and Science
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 Security100
- 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
- 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to qso-graph/adif-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 403 tokens (~44/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (88% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 3 Nov 26 −4
- Stability: pass → 0.67 functional
- 30 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 29 Oct 26 −44
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 2.1.0 → 2.1.1 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Malware scan: pass → unverified ▼ security
- Package version: 2.0.0 → 2.1.0 functional
- Package version: 2.0.0 → 2.0.3 functional
- Package version: 2.0.0 → 2.0.2 functional
- Package version: 2.0.0 → 2.0.1 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed pypi/adif-mcp@2.1.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/adif-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/adif-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3570727494 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:96687b0d66e9bf07eb990d96f872c91733a12b8acd36285f73c86b3420d8fd71 |
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 | 1 |
| 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 →
calculate_distance Calculate Distance ~33
Calculates distance (km) between Maidenhead locators.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | number | yes | – |
No examples provided.
calculate_heading Calculate Heading ~34
Calculates heading (azimuth) between Maidenhead locators.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | number | yes | – |
No examples provided.
get_version_info Get Version Info ~22
Returns the version of the ADIF-MCP server and spec.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_enumerations List Enumerations ~68
Lists the 26 enumerations: ADIF 3.1.7's 25 plus Country (derived). Each entry's ``source`` says whether it is ADIF's own export or derived by adif-mcp, so a consumer loading reference tables can tell them apart.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
parse_adif Parse Adif ~68
Streaming parser for large ADIF files with record seeking. SECURITY NOTE: This tool reads files from the local filesystem using the provided path. Only pass paths to ADIF log files you own.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
| limit | – | – | – |
| start_at | – | – | – |
No output schema declared.
No examples provided.
read_specification_resource Read Specification Resource ~83
Reads an ADIF 3.1.7 specification resource (e.g., 'mode', 'fields', 'all'). An unknown or unreadable name is a tool execution error, so the model can see it failed and correct the name rather than being handed an error document that looks like a successful result.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_enumerations Search Enumerations ~42
Searches ADIF 3.1.7 enumerations. Optionally filter by enumeration name.
| Name | Type | Req | Description |
|---|---|---|---|
| enumeration | – | – | – |
| search_term | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_adif_record Validate Adif Record ~37
Validates an ADIF record against 3.1.7 rules including enum membership.
| Name | Type | Req | Description |
|---|---|---|---|
| adif_string | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/adif-mcp server?
io.github.qso-graph/adif-mcp runs locally as a PyPI package, launched with uvx adif-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 · adif-mcp
claude mcp add qso-graph-adif-mcp -- uvx adif-mcp
What is the io.github.qso-graph/adif-mcp server?
io.github.qso-graph/adif-mcp is listed in the public MCP registry as io.github.qso-graph/adif-mcp. ADIF 3.1.7 spec engine for amateur radio logs: validation, parsing, enumerations, geospatial. This page covers its PyPI package (adif-mcp).
Is the io.github.qso-graph/adif-mcp server safe to use?
io.github.qso-graph/adif-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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/adif-mcp server expose?
io.github.qso-graph/adif-mcp exposes 8 tools: get_version_info, calculate_distance, calculate_heading, parse_adif, read_specification_resource, and 3 more. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.
Is the io.github.qso-graph/adif-mcp server still maintained?
io.github.qso-graph/adif-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 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/adif-mcp server under?
io.github.qso-graph/adif-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.