Skip to content

Releases

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 17:13
bceedd0
  • Guard the release gate's own precondition
  • Re-authenticate on each Registry retry

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 16:58
3a53780

Changed

  • Python 3.11 is the minimum. 3.10 reached end of life in October 2026
    (PEP 619), so it gets no further security
    releases on any platform. On Windows it was worse than unsupported: uv's 3.10
    is built against OpenSSL 1.1.1w, end of life since September 2023, so HTTPS
    from this server ran over an unmaintained TLS library. certifi does not help
    with that — it supplies the root store, not the implementation.

    3.10 support was already nominal. This package has linted with
    ruff target-version = "py311" and type-checked with mypy python_version = "3.11" for some time, so nothing ever verified the 3.10 claim.

    uv.lock is regenerated and the diff is large, but nothing is upgraded —
    it is the 3.10 resolution branch disappearing. Packages that carried two pins,
    one per Python branch, now carry the single 3.11+ pin they already resolved to.
    An install on 3.11 or later is unchanged.

v0.2.3

Choose a tag to compare

@github-actions github-actions released this 26 Oct 12:32
696bb5b

Changed

  • --transport streamable-http now says where it bound, and the help text says
    it too. It binds 127.0.0.1, and FastMCP takes no host option, so it was
    never reachable from another machine or from outside a container — and nothing
    said so. The bind address is unchanged: loopback-only is deliberate for a
    server that holds credentials and has no authentication of its own.

v0.2.2

Choose a tag to compare

@github-actions github-actions released this 26 Oct 09:27
9ae0ea3

Fixed

  • --version and --help now print and exit. They were ignored, so the
    command started the MCP server on stdio and waited for JSON-RPC — leaving a
    FastMCP banner on screen and an apparently hung terminal. Seven servers in
    this fleet already behaved correctly; this brings the rest in line, and a
    test asserts it.

v0.2.1

Choose a tag to compare

@watson-qg watson-qg released this 26 Oct 01:11
5edd55a
  • Move every Node 20 action to its first Node 24 major
  • The locked-dependency audit blocked every release
  • Four upgrades arrived as 57 pull requests
  • Nothing was auditing the lockfile
  • Close every open security advisory in the lockfile
  • A release is a workflow, not a merge

v0.2.0

Choose a tag to compare

@watson-qg watson-qg released this 26 Oct 01:11
e041768

Upgrading: a tool that rejects your input now returns isError: true instead of a successful
result whose payload carried an error key. Anything reading result["error"] should read the
error flag instead. The messages are unchanged.

MCP specification 2026-07-28 (#8)

  • Tool errors are flagged isError. _err built {"error": message} and nine call sites
    returned it, so on the wire a refusal arrived as a successful result. It raises ToolError
    now, typed NoReturn. The issue reports "2 occurrences"; measured, it is one payload
    construction reached from nine sites.
  • All five tools declare the four annotation hints, sharing one block.
  • The reason for the block is this server's own, not a sibling's. The owner-list servers answer
    openWorldHint: false because their data ships in the wheel; the live-service servers answer
    true because they call somebody's API. This one has no data at all — the moon's position is
    Meeus chapter 47 evaluated at a moment, path loss is the free-space formula. EM-C12 asserts
    that: no data directory, and no file opened at run time.
  • idempotentHint is a stronger claim here than anywhere else in the fleet. An owner-list
    server is idempotent only until the package is upgraded and its data changes underneath. A
    closed-form calculation gives the same answer in 2026 and in 2036. EM-C20 pins a moment and
    checks two calls agree; EM-C21 holds the case that looks like a counterexample and is not —
    when left empty means now, which is the argument defaulting rather than the tool behaving
    differently. It also records plainly that eme_moon_window takes no when and so cannot be
    pinned at all, which is why the stronger claim is demonstrated on the tools that accept a moment.
  • The refusal messages are the useful half, and they survive. A frequency outside 30 MHz to
    25 GHz, a band this server does not name, a time it cannot parse — EM-C31 checks each still
    says what to send instead, including that a refused band names the ones it knows.
  • tests/test_mcp_conformance.py (EM-C01 onward, 14 tests). Every check falsified — 11 of 11.
  • Nothing moved on the wire but the annotations. Every name, description, inputSchema and
    outputSchema dumped through a real fastmcp.Client before and after: byte-identical.

Lint (#7)

  • E501 is adopted. Four lines, not one a defect.
  • Every tool description came out byte-identical, because none of the long lines was in a
    docstring — unlike the owner-list servers, where reflowing a summary line reached a client.
  • The publisher-name exemption the issue was filed for does not apply: this server names no
    publisher's field, because it serves no publisher's list. Zero exemptions; the only noqa is a
    pre-existing F401 on a deliberately planted import in test_security.py.
  • Falsified: a long line planted in src/, caught.

Not applicable here

  • No certifi work and no issue for it (qso-graph-devel#73): there is no outbound call of any
    kind anywhere in the package. EM-C10 keeps it that way and names certifi in its failure
    message.

v0.1.1

Choose a tag to compare

@watson-qg watson-qg released this 26 Oct 01:11
072dfec
  • The MCP Registry refused 0.1.0: server.json's description was 133 characters and the
    Registry's limit is 100. PyPI had already accepted the upload by then, so 0.1.0 exists there
    but was never registered or tagged. The description is now 91 characters, and a test asserts
    the limit so it cannot be found by a failing publish again. Every other server in the fleet
    sits between 72 and 93 characters; this one was the outlier.