Skip to content

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 29 Oct 11:41
· 17 commits to main since this release
c9d0be6

Added

  • A WSJT-X listener, and the first working tools. WSJT-X's UDP Server
    messages, decoded by qso-graph-lib (qso_graph_lib.jt), the code
    qso-graph-sim plays them with:
    • jt_cq: who is calling CQ, and what kind (plain, DX, activity such as
      POTA or SOTA, contest, region, frequency), the latest per station.
    • jt_status: dial frequency and band, mode, DX call and grid, Tx enabled
      or transmitting, your call and grid, per WSJT-X instance.
    • jt_decodes: recent decodes, each read into who is calling whom, grid,
      report and sign-off, filtered by callsign, CQ, SNR or band.
    • jt_heard, jt_wspr, and jt_diagnostics for the listener itself.
  • The listener follows the fleet's "Servers that listen" rule
    (QGD-INT-0005/0006): 127.0.0.1 by default, every interface refused, --allow
    required on a network address, names refused, a sender not on the list
    dropped unread, counted and shown, and everything keyed by what a datagram
    says capped. Each rule has a test, and the sender check was removed once to
    prove the tests fail without it.
  • Still read-only: nothing in the package sends a datagram, so WSJT-X's
    Reply, Halt Tx and Free Text cannot be sent from here, and the conformance
    test asserts it. openWorldHint is true for the tools that read WSJT-X.

Changed

  • Renamed from js8call-mcp to jt-mcp, and the scope is the JT family.
    WSJT-X and JS8Call would have meant one listener each across separate servers.
    One server covers them.

    WSJT-X is first, and it defines the protocol: the
    message definitions come from the WSJT-X project, Network/NetworkMessage.hpp
    at the schema WSJT-X states, because the project that owns a definition is its
    authority. A variant is supported where it works with those definitions; where
    it does not, its difference is not implemented here.

    The GitHub repository redirects from the old name. On PyPI, js8call-mcp
    cannot be renamed: its six releases are yanked (2026-10-29), so nothing
    installs it unless pinned, and the project is kept rather than deleted, because
    a deleted PyPI name can be registered by anyone and the MCP Registry and old
    configurations still name it. jt-mcp is a new project; nothing depended on
    the old one beyond get_version_info. Its first release is 0.2.0, because
    this repository's history already holds v0.1.0.