YawLabs/tailscale-mcp v0.12.2 on GitHub

What's changed

Release-process and small-bug follow-ons from a full-pass review of the codebase. No user-visible behavior changes for the typical MCP install path.

server.json <-> package.json lockstep enforcement. The Official MCP Registry was never at risk of desyncing from npm -- the release.yml workflow has always re-bumped server.json from the pushed tag via jq immediately before mcp-publisher publish, by design (server.json is treated as derived at release time, package.json is the workstation source of truth). What this change actually adds: a new src/release-metadata.test.ts that pins package.json.version == server.json.version (top-level + packages[].version) and the mcpName <-> server.json.name mapping, so an out-of-band manual edit to either file gets caught locally before push. release.sh also now bumps server.json in lockstep with package.json, purely so the workstation's post-bump state matches what CI will produce -- an ergonomic consistency fix, not a publish-side bug fix.
Banner tool counts are computed. The startup tip line previously hard-coded (47 tools) / (20). Now both numbers are derived from PROFILES x toolGroups at startup, so adding or removing a tool in any group keeps the banner accurate without a follow-up doc edit.
Strict http:// / https:// URL classification in api.ts. apiRequest previously treated any path starting with http as absolute, which would mis-route a typoed path like httpfoo/.... Now only proper http:// and https:// prefixes skip the base-URL prepend.

Full diff: v0.12.1...v0.12.2