Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.qso-graph/sota-mcp

PYPI · SOTA-MCP

Summits on the Air MCP server. Summit lookup, spots, alerts, nearby summits.

Available components

+14 this week 92 Trust /100

Last scanned (1 day ago)

Scores higher than 95% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

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 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/sota-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 Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 375 tokens (~75/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 −5
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.67 functional
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 30 Oct 26 +18
    • Malware scan: unverified → pass ▲ security
    • Stability: fail → pass ▲ security
  • 29 Oct 26 0
    • Package version: 0.4.0 → 0.4.1 functional
  • 27 Oct 26 0
    • Package version: 0.3.0 → 0.4.0 functional
Diagnostics

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/sota-mcp@0.4.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/sota-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/qso-graph/sota-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560579543
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:e82fde3cdfa6bd6b4ce8509193f8084eaf2062fb2896a7acf745387c392fed5d

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 →

MCP tools · 5 exposed · ~337 tokens

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 →

Tool Tokens
get_version_info ~76

Get sota-mcp service version and upstream spec version. Returns the running PyPI version of sota-mcp and the SOTA api2 endpoint contract 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.

sota_alerts ~52

Get upcoming SOTA activation alerts.

NameTypeReqDescription
association––Filter by SOTA association (e.g., W7I). Empty for all.
hours––Look-ahead window in hours (default 16).

Structured output declared, but exposes no named fields.

No examples provided.

sota_spots ~86

Get current and recent SOTA spots. Returns live spot feed with summit details.

NameTypeReqDescription
association––Filter by SOTA association (e.g., W7I, G, VK). Empty for all.
hours––Time window in hours (default 24).
mode––Filter by mode (e.g., CW, SSB, FT8). Empty for all.

Structured output declared, but exposes no named fields.

No examples provided.

sota_summit_info ~49

Get detailed summit information by SOTA reference code.

NameTypeReqDescription
summit_codestringyesSOTA reference (e.g., W7I/SI-001, G/LD-001).

Structured output declared, but exposes no named fields.

No examples provided.

sota_summits_near ~74

Find SOTA summits near a geographic location.

NameTypeReqDescription
latitudenumberyesCenter latitude (decimal degrees).
limit––Maximum number of results (default 20).
longitudenumberyesCenter longitude (decimal degrees).
radius_km––Search radius in km (default 50).

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.qso-graph/sota-mcp server?

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

# add to Claude Code
claude mcp add qso-graph-sota-mcp -- uvx sota-mcp
Common questions

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

io.github.qso-graph/sota-mcp is listed in the public MCP registry as io.github.qso-graph/sota-mcp. Summits on the Air MCP server. Summit lookup, spots, alerts, nearby summits. This page covers its PyPI package (sota-mcp).

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

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

io.github.qso-graph/sota-mcp exposes 5 tools: get_version_info, sota_spots, sota_alerts, sota_summit_info, sota_summits_near. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.

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

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

io.github.qso-graph/sota-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.