io.github.qso-graph/pota-mcp
PYPI · POTA-MCP
Parks on the Air MCP server. Park lookup, activator and hunter stats, live spots.
Available components
Last scanned (1 day ago)
Scores higher than 74% of PyPI servers
Category Maps and Location
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 Security50
- 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
- 1 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/pota-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 5 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 1139 tokens (~103/item across 11 items; 11 tools + 0 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 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.67 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.0 → 0.7.1 functional
- 29 Oct 26 0
- Package version: 0.7.0 → 0.7.1 functional
- Package version: 0.4.0 → 0.7.0 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.6.0 → 0.7.0 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.0 → 0.6.0 functional
- Package version: 0.4.0 → 0.4.3 functional
- Package version: 0.4.0 → 0.4.2 functional
- Package version: 0.4.0 → 0.4.1 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 4 Nov 2026 · Analysed pypi/pota-mcp@0.7.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/pota-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/pota-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560358961 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5e7549c20bb467704d88e401b685b1a218526482f61458c8e0576291ad8a2632 |
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 | 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 →
get_version_info Get Version Info ~77
Get pota-mcp service version and upstream spec version. Returns the running PyPI version of pota-mcp and the POTA API revision currently 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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pota_location_parks Pota Location Parks ~52
List all POTA parks in a state, province, or country.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Location code (e.g., US-ID for Idaho, CA-ON for Ontario, G for England). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_nearby_parks Pota Nearby Parks ~144
Find POTA parks near a geographic point. Fetches all parks in the given location and filters by distance. Useful for finding 2-fer candidates near an activation site.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Center point latitude (e.g., 43.617). |
| limit | – | – | Maximum parks to return (default 25, max 100). |
| location | string | yes | Location code (e.g., US-ID, CA-ON). Required to scope the search. |
| longitude | number | yes | Center point longitude (e.g., -115.993). |
| radius_km | – | – | Search radius in km (default 50, max 500). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_park_activations Pota Park Activations ~84
List recent activations of a POTA park, most recent first. Answers "when was this park last activated?" and "is it often on the air?".
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | How many recent activations to return (default 10, max 50). |
| reference | string | yes | Park reference code (e.g., US-0062). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_park_info Pota Park Info ~49
Get detailed park information by POTA reference code.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Park reference code (e.g., US-0001, CA-5580, G-0001). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_park_leaderboard Pota Park Leaderboard ~113
Top activators and hunters of a POTA park. Three boards: most activations, most QSOs as an activator, most QSOs as a hunter. Each row is a callsign and a count and nothing else.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Rows per board (default 10, max 25). POTA currently publishes five per board, so a higher limit changes nothing until it does. |
| reference | string | yes | Park reference code (e.g., US-0062). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_park_stats Pota Park Stats ~41
Get activation and QSO counts for a POTA park.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Park reference code (e.g., US-0001). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_rare_parks_near Pota Rare Parks Near ~168
Find the least-activated POTA parks near a point. Answers "which parks near me have never, or rarely, been activated?" — for an activator looking for something unworked, or a hunter looking for a rare one. Least activated first, nearest first among equals.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Center point latitude (e.g., 43.617). |
| limit | – | – | Maximum parks to return (default 25, max 100). |
| location | string | yes | Location code (e.g., US-ID, CA-ON). Required to scope the search. |
| longitude | number | yes | Center point longitude (e.g., -115.993). |
| radius_km | – | – | Search radius in km (default 50, max 500). |
Structured output declared, but exposes no named fields.
No examples provided.
pota_scheduled Pota Scheduled ~185
Get upcoming scheduled POTA activations. All filters are optional and combine with AND — omit them all and the whole schedule comes back, as before.
| Name | Type | Req | Description |
|---|---|---|---|
| activator | – | – | Filter by activator callsign (e.g., N3VEM). Empty for all. |
| location | – | – | Filter by location code (e.g., US-ID, CA-ON). Matches a park that spans regions, so US-MD finds a park listed as US-VA,US-MD. Empty for all. |
| reference | – | – | Filter by park reference (e.g., US-0058). Empty for all. |
| within_hours | – | – | Only activations whose start time falls between now and this many hours from now. An activation already under way is not included — pota_spots is what reports the air now. Omit for no time limit. |
Structured output declared, but exposes no named fields.
No examples provided.
pota_spots Pota Spots ~137
Get current POTA activator spots. Returns live spot feed with park details, grid squares, and coordinates. All filters are optional — omit to get all active spots.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m, 40m). Empty for all bands. |
| location | – | – | Filter by location code (e.g., US-ID, CA-ON). Empty for all. |
| mode | – | – | Filter by mode (e.g., CW, FT8, SSB). Empty for all modes. |
| program | – | – | Filter by program prefix (e.g., US, VE, G). Empty for all. |
Structured output declared, but exposes no named fields.
No examples provided.
pota_user_stats Pota User Stats ~48
Get POTA activator and hunter statistics for a callsign.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | string | yes | Callsign to look up (e.g., K4SWL, KI7MT). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/pota-mcp server?
io.github.qso-graph/pota-mcp runs locally as a PyPI package, launched with uvx pota-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 · pota-mcp
claude mcp add qso-graph-pota-mcp -- uvx pota-mcp
What is the io.github.qso-graph/pota-mcp server?
io.github.qso-graph/pota-mcp is listed in the public MCP registry as io.github.qso-graph/pota-mcp. Parks on the Air MCP server. Park lookup, activator and hunter stats, live spots. This page covers its PyPI package (pota-mcp).
Is the io.github.qso-graph/pota-mcp server safe to use?
io.github.qso-graph/pota-mcp scores 77 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/pota-mcp server expose?
io.github.qso-graph/pota-mcp exposes 11 tools: get_version_info, pota_spots, pota_park_info, pota_park_stats, pota_park_activations, and 6 more. Their descriptions and schemas cost roughly 1,098 tokens of context every time the server is loaded.
Is the io.github.qso-graph/pota-mcp server still maintained?
io.github.qso-graph/pota-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/pota-mcp server under?
io.github.qso-graph/pota-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.