# 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.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `jt-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp.md), [page](https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp)

## Channel facts

- Registry: `pypi`
- Package: `jt-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 16 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to qso-graph/jt-mcp).
  - Clear OSI-approved license (GPL-3.0-or-later).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
claude mcp add qso-graph-jt-mcp -- uvx jt-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "qso-graph-jt-mcp": {
      "command": "uvx",
      "args": [
        "jt-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "qso-graph-jt-mcp": {
      "command": "uvx",
      "args": [
        "jt-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add qso-graph-jt-mcp -- uvx jt-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qso-graph-jt-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "jt-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qso-graph-jt-mcp --command uvx --arg jt-mcp
```

### Hermes

```yaml
mcp_servers:
  qso-graph-jt-mcp:
    command: "uvx"
    args: ["jt-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "qso-graph-jt-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "jt-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add qso-graph-jt-mcp -t stdio -c uvx -a jt-mcp
```

### Other

```json
{
  "mcpServers": {
    "qso-graph-jt-mcp": {
      "command": "uvx",
      "args": [
        "jt-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 66)

First indexed and scored.

## MCP tools (7)

### `get_version_info` (~26 tokens)

Get Version Info

Get this server's version, what it does, and where its work is tracked.

### `jt_status` (~85 tokens)

Jt Status

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.

Input parameters:

- `instance`: one WSJT-X by the Id it sends (e.g. "WSJT-X - FT-991A"); every one if left out.

### `jt_cq` (~169 tokens)

Jt Cq

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.

Input parameters:

- `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).

### `jt_decodes` (~163 tokens)

Jt Decodes

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.

Input parameters:

- `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).

### `jt_heard` (~107 tokens)

Jt Heard

Stations heard since this server started: how often, last SNR, last grid sent,
mode and band, first and last heard.

Input parameters:

- `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.

### `jt_wspr` (~95 tokens)

Jt Wspr

WSPR spots WSJT-X has decoded, newest first: call, grid, power, SNR, drift.

Input parameters:

- `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).

### `jt_diagnostics` (~46 tokens)

Jt Diagnostics

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.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp#diagnostics

## Score history

- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 66
- 2026-10-29: 66

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/jt-mcp/
- Socket report: https://socket.dev/pypi/package/jt-mcp
- Repository: https://github.com/qso-graph/jt-mcp
- Changelog RSS feed: https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qso-graph-jt-mcp/jt-mcp