YawLabs/tailscale-mcp v0.21.1 on GitHub

release.sh survives an immediate re-run, and rides out the MCP Registry lagging npm. Step 5's "already published" check and step 8 now read npm's per-version document, which is served uncached, instead of npm view, whose packument Cloudflare's edge caches for up to 5 minutes -- so a re-run right after a failed later step could miss the version, publish again, and die on npm's E403 "cannot publish over the previously published versions" as if the token were bad. That E403 now counts as already published. The npm propagation gate already polled that document with curl, and now shares the same check. The MCP Registry publish is tried up to four times, 30/60/90s apart, on the registry's own "not found (status: 404)" naming the version, "Likely transient, retry later" and "failed to fetch package metadata from NPM" answers, or its HTTP 429, 502, 503 or 504 (with a fresh registry login before each retry), and a duplicate version counts as done; any other registry error still fails on the first attempt.

The README's Add to Yaw MCP button now sits directly under the title, and the follow badge links to @YawLabs. The one-click install button and its one-line caption moved up from further down the page, so they are the first thing under the name on npm and GitHub, and the X badge at the bottom points at @YawLabs instead of @TokenLimitNews. npm shows the README from the published package, which is why it takes a release to carry this there; the package's code is unchanged from 0.21.0.