v0.7.0
[0.7.0] - 2026-07-31
Changed
-
Migrated to the
mcpPython SDK 2.x.mcp[cli]moves from>=1.28.1,<2
to>=2.0.0,<3,FastMCP→MCPServer(mcp.server.mcpserver). The lower
bound is hard: 2.0.0 removedmcp.server.fastmcpwithout a compatibility
shim, so this code no longer runs on 1.x, and an open range would let a
resolver pick a version that fails at import.This landed in
20a6d41without a changelog entry, which is why the section
below still described the opposite fix. Recorded here so the release notes
match what actually ships.
Fixed
-
The published 0.6.0 dies on a fresh install. It imports
mcp.server.fastmcp, whichmcp2.0.0 removed on 2026-07-28. With its
declared range open at the top, every newpip install swiss-statistics-mcp
resolved to 2.0.0 and failed withModuleNotFoundErrorbefore the server
could start. The migration above fixes it — but the fix sat onmainunder
the same version number PyPI was already serving, so nothing could be
published and every fresh install kept breaking. Hence this bump.Verified:
maininstalled into a clean venv resolvesmcp2.0.0, imports
and starts.
Superseded
- An earlier commit (
9b7d7a0) announced cappingmcpat<2as the fix.
That was correct when written and is no longer what the code does — the
migration replaced it. Noted rather than deleted: the cap reached nobody, and
a changelog that quietly rewrites its own history is worth less than one that
shows the correction.
What's Changed
- fix(deps): cap mcp at <2 — 2.0.0 removed mcp.server.fastmcp by @malkreide in #19
- ci: Versions-Sync-Check übernehmen — und den Fallback-Marker angleichen by @malkreide in #20
- feat!: migrate to mcp Python SDK 2.x by @malkreide in #21
- chore(release): v0.7.0 — kaputten Fresh-Install beheben by @malkreide in #22
Full Changelog: v0.6.0...v0.7.0