v0.4.2 — the package can start again

If you installed seleniumboot-mcp on or after 2026-07-28, it could not start. This release fixes that. Upgrade with pip install --upgrade seleniumboot-mcp.

Fixed

• The package no longer installs against an mcp SDK it cannot run on. The dependency was declared mcp>=1.0.0 with no upper bound, so once mcp 2.0.0 went stable (2026-07-28) every fresh pip / uv install resolved to it — and 2.0.0 removed the Server.list_tools / Server.call_tool decorators this server registers all 85 tools with. The result was an AttributeError at import time: the entry point died before a single tool was registered, with no workaround available. The dependency is now bounded mcp>=1.0.0,<2.0.0. (Fixes #2)

Migrating to the mcp 2.0 API is the real fix and is tracked separately; this release exists to unbreak installs now.

Thanks to @hakanngul for the report, which included an accurate root-cause diagnosis.