io.github.qso-graph/jt-mcp
PYPI · JT-MCP
WSJT-X over UDP for AI apps: status, decodes, who is calling CQ, stations heard, WSPR. Read-only.
Available components
Last scanned (22 hours ago)
Scores higher than 82% of PyPI servers
Category IoT and Hardware
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/jt-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 Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 803 tokens (~114/item across 7 items; 7 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 66
First indexed and scored.
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/jt-mcp@0.2.0
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/jt-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/jt-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3566301145 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b8497ae39080639d8722033168f3a49d01dfde55c07623d3495f10bfa9ce48d5 |
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 ~26
Get this server's version, what it does, and where its work is tracked.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
jt_cq Jt Cq ~169
Who is calling CQ, and what kind of CQ: plain, DX, an activity (POTA, SOTA, WWFF, IOTA), a contest (TEST, FD, RU, WW), a region (NA, EU, ...), or a frequency (CQ 290). The latest CQ per station, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | e.g. "20m". |
| cq_type | – | – | one of plain, dx, activity, contest, region, frequency, other. |
| instance | – | – | one WSJT-X by its Id; every one if left out. |
| modifier | – | – | the exact word after CQ, e.g. "POTA" or "NA". |
| since_minutes | integer | – | how far back, 1 to 1440 (default 5). |
Structured output declared, but exposes no named fields.
No examples provided.
jt_decodes Jt Decodes ~163
Recent decodes, newest first, each read into its parts: CQ (with its type), or who is calling whom, with the grid, report or sign-off it carries.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | e.g. "20m". |
| callsign | – | – | decodes sent by or to this call. |
| cq_only | boolean | – | CQ calls only. |
| instance | – | – | one WSJT-X by its Id; every one if left out. |
| limit | integer | – | at most this many, 1 to 500 (default 50). |
| min_snr | – | – | this SNR in dB or better (-50 to 50). |
| since_minutes | integer | – | how far back, 1 to 1440 (default 15). |
Structured output declared, but exposes no named fields.
No examples provided.
jt_diagnostics Jt Diagnostics ~46
The listener itself: where it listens, who may send, what has arrived, what was dropped and from where, and each WSJT-X instance's version and last heartbeat.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
jt_heard Jt Heard ~107
Stations heard since this server started: how often, last SNR, last grid sent, mode and band, first and last heard.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | – | – | one station only. |
| limit | integer | – | at most this many, 1 to 500 (default 50). |
| since_minutes | integer | – | heard within this many minutes, 1 to 1440 (default 60). |
| sort | string | – | last_heard (default), snr or count. |
Structured output declared, but exposes no named fields.
No examples provided.
jt_status Jt Status ~85
What each running WSJT-X is doing now: dial frequency and band, mode, the station being worked (DX call and grid), whether Tx is enabled or transmitting, and your own call and grid.
| Name | Type | Req | Description |
|---|---|---|---|
| instance | – | – | one WSJT-X by the Id it sends (e.g. "WSJT-X - FT-991A"); every one if left out. |
Structured output declared, but exposes no named fields.
No examples provided.
jt_wspr Jt Wspr ~95
WSPR spots WSJT-X has decoded, newest first: call, grid, power, SNR, drift.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | e.g. "30m". |
| callsign | – | – | one station only. |
| limit | integer | – | at most this many, 1 to 500 (default 50). |
| since_minutes | integer | – | how far back, 1 to 1440 (default 60). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/jt-mcp server?
io.github.qso-graph/jt-mcp runs locally as a PyPI package, launched with uvx jt-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 · jt-mcp
claude mcp add qso-graph-jt-mcp -- uvx jt-mcp
What is the io.github.qso-graph/jt-mcp server?
io.github.qso-graph/jt-mcp is listed in the public MCP registry as io.github.qso-graph/jt-mcp. WSJT-X over UDP for AI apps: status, decodes, who is calling CQ, stations heard, WSPR. Read-only. This page covers its PyPI package (jt-mcp).
Is the io.github.qso-graph/jt-mcp server safe to use?
io.github.qso-graph/jt-mcp scores 81 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/jt-mcp server expose?
io.github.qso-graph/jt-mcp exposes 7 tools: get_version_info, jt_status, jt_cq, jt_decodes, jt_heard, and 2 more. Their descriptions and schemas cost roughly 691 tokens of context every time the server is loaded.
Is the io.github.qso-graph/jt-mcp server still maintained?
io.github.qso-graph/jt-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/jt-mcp server under?
io.github.qso-graph/jt-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.