mcpwatch v0.3.0

Content-addressed storage (archive grows with change, not registry size — legacy DBs migrate in place), a ~4-minute retry window so a laptop waking up no longer loses a day of history, crawl --if-due with a wake-aware launchd schedule, and the canonical archive moved to GitHub Actions (see the rolling archive release).

npm: npm i -g watchmcp (command is mcpwatch).

Rolling archive (canonical)

The canonical mcpwatch archive, updated daily by GitHub Actions.

• mcpwatch.db — content-addressed SQLite: every server, every version, every run since 2026-08-28
• run-N.jsonl.gz — the verbatim registry response for each run, the ground truth the DB can always be rebuilt from

Seeded from the original laptop lineage (runs 1, 2, 4 — run 3 failed on a dead Wi-Fi link and stored nothing).

mcpwatch v0.2.0

Adds mcpwatch digest — a publishable 'This week in MCP' post generated from real archive events — and sharper severity: package changes without a version bump (the rug-pull shape) stay high, version-accompanied ones drop to info.

npm package name is watchmcp (npm blocks names too similar to the existing mcp-watch); the installed command is mcpwatch. Tarball install:

npm install -g https://github.com/letmeadityakumar66-byte/mcpwatch/releases/download/v0.2.0/watchmcp-0.2.0.tgz

mcpwatch v0.1.0

Supply-chain watchtower for MCP servers. First snapshot: 25,317 servers, 83,784 version rows — 81% of hosted servers declare no authentication metadata.

Install without npm registry:

npm install -g https://github.com/letmeadityakumar66-byte/mcpwatch/releases/download/v0.1.0/mcpwatch-0.1.0.tgz