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.sbrunner-atx/fldigi-mcp

PYPI · FLDIGI-MCP

Control fldigi (amateur-radio digital modes) over XML-RPC: modem, frequency, rig, log, transmit.

Available components

−19 this week 72 Trust /100

Last scanned (15 hours ago)

Scores higher than 69% of PyPI servers

Category Communication

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 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
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to sbrunner-atx/fldigi-mcp). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-or-later).Pass
  • Actively maintained (last published 50 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2407 tokens (~114/item across 21 items; 21 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 −5
    • Stability: pass → 0.63 functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 0
    • Stability: pass → 0.97 functional
  • 18 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Oct 26 +17
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.80 → pass security
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 5 Nov 2026 · Analysed pypi/fldigi-mcp@0.3.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 sbrunner-atx/fldigi-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sbrunner-atx/fldigi-mcp/.github/workflows/release.yml@refs/tags/v0.3.1
Rekor log index 2826885175
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:571407749c382d45851e2aa0a0bd1015175d52a64214e72a15246781cda40016

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 21 exposed · ~2,407 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
application ~118

The fldigi program and its process. Info operations: version, version_struct, name, name_version, config_dir, list_methods. Process operations: launch, stop, terminate, is_running. `launch` starts fldigi pointed at the configured XML-RPC endpoint; `stop`/ `terminate` ask it to quit (saving options; optionally the log/macros) and fall back to ending a process this server started.

NameTypeReqDescription
operationstringyes–
save_logboolean––
save_macrosboolean––

No output schema declared.

No examples provided.

band_guidance ~113

Advisory band guidance (experimental, region-aware) — informational / QSY help only. operations: - lookup (frequency_hz, optional mode): what the band plan says at a frequency. - watering_hole (mode, optional band): the preferred calling frequency for a mode. - move_to_watering_hole (mode): set the dial to that frequency (does NOT transmit).

NameTypeReqDescription
band–––
frequency_hz–––
mode–––
operationstringyes–

No output schema declared.

No examples provided.

browser ~173

fldigi's Signal Browser over XML-RPC: every station the multi-channel decoder bank has locked to in the passband, with the text decoded on each channel. This is what the left-hand browser panel shows, and it copies stations far too weak for the waterfall to show. operations: channels (list of {channel, freq, active, text}; text accumulates since the last clear, a newline marks a lost-and-regained signal), clear, available. Runs for PSK, RTTY and CW modems (fldigi's browser covers those). Needs a fldigi built with the patch in fldigi-mcp/patches; stock 4.2.13 has no browser.* methods, and then this tool says so instead of failing. Receive only.

NameTypeReqDescription
operationstring––

No output schema declared.

No examples provided.

controls ~124

fldigi operating controls (the AFC / SQL / Rev / Lock / RxID / TxID buttons) and status. operations: get/set/toggle_afc, get/set/toggle_squelch (SQL), get/set/inc_squelch_level, get/set/toggle_reverse (Rev), get/set/toggle_lock (Lock), get/set/toggle_rxid (RxID), get/set/toggle_txid (TxID), get_status1, get_status2, get_trx_status, get_trx_state.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

diagnostics ~104

Host + network diagnostics for troubleshooting connectivity. Does NOT connect to fldigi. Reports the resolved FLDIGI_HOST/PORT, this process's Python and hostname, the transmit-gate state, and the host's network interfaces — so you can tell whether the process can even see the target's network (e.g. when running host-side vs. sandboxed). If a non- loopback host times out, see mcp-host-bridge (docs/INSTALL.md).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fldigi_call ~74

Escape hatch: call ANY fldigi XML-RPC method by dotted name (e.g. 'rig.get_mode'). Use `station` with operation 'list_methods' to discover every method the running build supports. Keying methods remain callsign-gated.

NameTypeReqDescription
methodstringyes–
params–––

No output schema declared.

No examples provided.

flmsg ~64

flmsg (message forms) interworking. operations: online, available, transfer, squelch, get_data (RX data since the last query). These signal or hand data to a running flmsg; none of them key the transmitter.

NameTypeReqDescription
operationstringyes–

No output schema declared.

No examples provided.

frequency ~59

RF frequency and waterfall sideband. operations: get, set (value=Hz), increment (value=Hz), get_sideband, set_sideband (value='USB'|'LSB').

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

io ~41

ARQ / KISS I/O port. operations: in_use (which port is active), enable_kiss, enable_arq.

NameTypeReqDescription
operationstringyes–

No output schema declared.

No examples provided.

legacy ~121

Deprecated fldigi methods, kept so the whole catalog is reachable. Each has a current equivalent, which you should prefer: get/set_sideband -> frequency get/set_sideband; rsid -> controls toggle_rxid; get/set_rig_name, get/set_rig_frequency, get/set_rig_mode(s), get/set_rig_bandwidth(s) -> the rig tool; log_get_sideband -> frequency get_sideband; flmsg_online/available/transfer/squelch -> the flmsg tool.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

log ~130

Logbook (QSO / contest) fields. operations: get (field=...), set (field=..., value=...), clear, last_record, all_records. Settable fields: call, name, qth, locator, serial_number, exchange, rst_in, rst_out, contest_counter (set only: the starting contest serial number). Gettable fields also include frequency, time_on/off, serial_number_sent, state, province, country, band, notes, az. last_record / all_records return ADIF.

NameTypeReqDescription
field–––
operationstringyes–
value–––

No output schema declared.

No examples provided.

modem ~128

Operating mode (the fldigi "Op Mode" menu) and modem settings. operations: get, list, get_id, get_max_id, set (value=mode name e.g. 'BPSK31'), set_by_id (value=id), get_io_names (modems usable for KISS/ARQ I/O), get/set/inc_carrier, get/set/inc_afc_range, get/set/inc_bandwidth, get_quality, search_up, search_down, olivia_get/set_bandwidth, olivia_get/set_tones.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

navtex ~56

NAVTEX / SitorB mode. operations: get_message (value=timeout seconds), send_message (value=text). send_message transmits and is callsign-gated.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

rig ~118

Rig (CAT) control via flrig/Hamlib/RigCAT. operations: get/set_name, get/set_frequency (value=Hz), get/set_mode (value=name), get_modes, set_modes (value=[...]), get/set_bandwidth, get_bandwidths, set_bandwidths (value=[...]), get/set_notch, enable_qsy (value=1|0), set_smeter / set_pwrmeter (value=int, drives fldigi's meter display).

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

signal_hunt ~366

Find and name the signals in the receiver audio and rank them the way a contest operator reads the waterfall: the station that sits still and calls CQ scores highest. method 'audio' (default): tap `seconds` of audio from the input device (FLDIGI_AUDIO_DEVICE, the device fldigi listens on; or `device` as a name substring or index; `wav` analyses a file instead). Needs the optional extra: pip install 'fldigi-mcp[hunt]'. method 'devices': list the input devices the tap can open. method 'browser': read fldigi's Signal Browser (needs the browser patch, see the `browser` tool): one candidate per channel the decoder bank holds, with its text, for the current modem family (PSK, RTTY or CW). Finds stations the spectrum analyser ranks near the floor, but names no mode: it reports what fldigi is set to. method 'api': blind fallback with no audio access; steps modem.search_up across the passband for each modem (mode='RTTY,BPSK31,...') and reads modem.get_quality. Slow. Each candidate carries carrier_hz, mode (RTTY with shift, CW, BPSK31/63/125, Olivia with tones and bw, MFSK16, DominoEX, MT63, or unknown), db_over_floor, persistence (fraction of the window it was present), periodicity (a CQ loop repeats), score, and fldigi_modem, the name tune_to needs. Nothing here transmits.

NameTypeReqDescription
device–––
methodstring––
mode–––
secondsnumber––
topinteger––
wav–––

No output schema declared.

No examples provided.

spot ~46

Spotting / PSK Reporter. operations: get_auto, set_auto (value=bool), toggle_auto, pskrep_count.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

status ~29

Snapshot: version, modem, frequency (Hz), TX/RX state, transmit gate, region, band.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

text ~129

RX/TX text and data. operations: read (decoded RX text; start/length), rx_length, get_rx (value=[start, length], the raw byte range), clear_rx, add_tx (value=text), add_tx_queue, add_tx_bytes (value=text or bytes), clear_tx, get_rxtx_data, get_rx_data, get_tx_data. `add_tx` / `add_tx_bytes` only stage text in the TX widget; they do not transmit.

NameTypeReqDescription
length–––
operationstringyes–
startinteger––
value–––

No output schema declared.

No examples provided.

transmit ~159

Transmitter control. operations: tx, tune, rx, abort, disable_tx, enable_tx, run_macro (value=id), get_max_macro_id, send (text=...), and timing information: tx_timing (value=test string), char_rates, char_timing (value=one character); both timings return 'samples : sample rate : seconds'. Keying operations (tx, tune, run_macro, send) require a configured callsign; rx, abort, disable_tx and the timing operations never key and are always allowed. `send` queues text and transmits, auto-returning to receive by default.

NameTypeReqDescription
operationstringyes–
return_to_rxboolean––
text–––
value–––

No output schema declared.

No examples provided.

tune_to ~156

Set fldigi to a signal_hunt candidate: modem by fldigi name (e.g. 'RTTY', 'BPSK31', 'OLIVIA-8/250', 'MFSK16', 'DOMEX11', 'MT63-500'), the audio carrier, AFC on, and RxID off by default so another station's RSID burst cannot retune the modem mid-pass. Read the result with `text` read after 20 seconds; `modem` get_quality says whether it locked. Does not transmit.

NameTypeReqDescription
afcboolean––
carrier_hzintegeryes–
fldigi_modemstringyes–
rxidboolean––

No output schema declared.

No examples provided.

wefax ~99

WEFAX (weather fax) mode. operations: state, skip_apt, skip_phasing, tx_abort, end_reception, start_manual_reception, set_adif_log (value=bool), set_max_lines (value=int), get_received_file (value=timeout), send_file (value=[filename, timeout_seconds]). send_file transmits and is callsign-gated.

NameTypeReqDescription
operationstringyes–
value–––

No output schema declared.

No examples provided.

Install

How do I install the io.github.sbrunner-atx/fldigi-mcp server?

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

# add to Claude Code
claude mcp add sbrunner-atx-fldigi-mcp -- uvx fldigi-mcp
Common questions

What is the io.github.sbrunner-atx/fldigi-mcp server?

io.github.sbrunner-atx/fldigi-mcp is listed in the public MCP registry as io.github.sbrunner-atx/fldigi-mcp. Control fldigi (amateur-radio digital modes) over XML-RPC: modem, frequency, rig, log, transmit. This page covers its PyPI package (fldigi-mcp).

Is the io.github.sbrunner-atx/fldigi-mcp server safe to use?

io.github.sbrunner-atx/fldigi-mcp scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.sbrunner-atx/fldigi-mcp server expose?

io.github.sbrunner-atx/fldigi-mcp exposes 21 tools: status, diagnostics, application, modem, frequency, and 16 more. Their descriptions and schemas cost roughly 2,407 tokens of context every time the server is loaded.

Is the io.github.sbrunner-atx/fldigi-mcp server still maintained?

io.github.sbrunner-atx/fldigi-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.sbrunner-atx/fldigi-mcp server under?

io.github.sbrunner-atx/fldigi-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.

What did VerifyMCP test on the io.github.sbrunner-atx/fldigi-mcp server?

VerifyMCP ran 15 checks on io.github.sbrunner-atx/fldigi-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.sbrunner-atx/fldigi-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.