A server can change its remote URL — your agent's traffic goes somewhere new. A new version can start demanding environment variables — that's your secrets. Directories score servers as they are today. Nobody watches what changes. mcpwatch does.
servers in the official registry, snapshotted Aug 28 2026
version rows archived — every version, every run
of hosted servers declare no authentication metadata
$ mcpwatch check mcpwatch check · 5 MCP servers configured on this machine ✓ GitKraken claude-code ✓ dart cursor ? unregistered internal-tools codex ▲ ALERT search-api claude-code REMOTE_CHANGED: {"from":["https://api.old.example"],"to":["https://api.new.example"]}
→ This week in MCP, issue 1: 457 new servers, 15 vanished, 30 newly demanding secrets
| event | severity | why it matters |
|---|---|---|
| REMOTE_CHANGED | high | traffic redirection under a stable name — the rug-pull shape |
| PACKAGE_CHANGED | high | you'd execute different code tomorrow than yesterday |
| ENV_ADDED | high | a server newly asking for secrets |
| VANISHED / STATUS | medium | takedowns and deprecations — the registry forgets, the archive doesn't |
Deleted servers vanish from every directory — but not from an append-only archive that was recording. Version lineages, URL changes, deletions: none of it can be reconstructed by anyone who started later. Recording began August 28, 2026.
Zero dependencies. Only network calls: GETs to registry.modelcontextprotocol.io. Client configs read-only. No probing of anyone's servers. MIT.