MCP Drift Watch

Why a separate feed — every MCP scanner answers one question: is this package safe today? A rug pull is the other question: the package was clean when it was reviewed, collected installs for weeks, and only then shipped a patch that runs code on npm i. Existing defences against that are local — a CLI diff you have to run yourself, a runtime proxy inside your own perimeter, or a changelog the vendor writes voluntarily. All of them mean the first victim is never protected.

What this is — the whole MCP package population re-audited daily from the outside, with every transition recorded. An event exists here because there is a snapshot from before it.

Check your own list (free, no key — put it in CI):

curl -s "https://pulsefeed.dev/mcp/drift.json?packages=pkg-a,pkg-b&days=7"

Put it in your CI — one step, no key, fails the build when a dependency you already trust changes dangerously:

- uses: Nikolife2016/mcp-drift-action@v1

github.com/Nikolife2016/mcp-drift-action

Subscribe to your own list (RSS, no signup — drop it in Slack, a reader, or a CI step):

https://pulsefeed.dev/mcp/drift.rss?packages=pkg-a,pkg-b

Get woken up, not notified later — a webhook fires the moment we see it, for your packages only:

curl -X POST https://pulsefeed.dev/mcp/alerts/subscribe   -H 'content-type: application/json'   -d '{"url":"https://your-endpoint","packages":["io.github.you/your-server","your-npm-pkg"]}'

We post a confirmation to that webhook containing a link; opening it activates the subscription. A webhook nobody confirms never receives anything — otherwise anyone could point our traffic at your endpoint. Only ownership changes, install scripts appearing, removals, lookalike names and resurrections are sent; new versions are not, because being woken for a release is how you learn to ignore the channel.

Unlike the RSS filter, this does mean we store something: your webhook URL, your package list and timestamps. No email, no name, nothing about who you are, and the URL is never published — /mcp/alerts/status shows counts only. The unsubscribe link travels in every delivery.

Put the badge in your README — it states what changed in your package after people adopted it, and it goes grey rather than green when we have nothing to say:

[![MCP drift](https://pulsefeed.dev/badge/mcp.svg?package=YOUR-PACKAGE)](https://pulsefeed.dev/mcp/drift)

Use your registry name (io.github.you/your-server) or your npm package name. A green badge is a claim about your package, so we only make it when the package is in the snapshot — otherwise it reads unwatched.

Free: the last 7 days across the whole population (/mcp/drift.json), any depth for your own packages (?packages=), the badge, the webhook alerts and the CI action — no key, no payment, CORS-enabled. Paid: the full series since 2026-07-30 in one call, /mcp/drift/history ($0.10 via x402; windows of up to 7 days are free). Each day's dataset manifest is signed (Ed25519) and anchored in Bitcoin via OpenTimestamps so the series cannot be quietly rewritten: /anchors/latest.json · key /.well-known/manifest-signing-key.json. Full feed: /mcp/drift.json · /mcp/drift.rss · single package: GET /mcp/verify?package=<name>