# PulseFeed MCP Supply-Chain Drift History

> PulseFeed MCP Supply-Chain Drift History is a paid API for AI agents from pulsefeed.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Returns the complete historical series of MCP registry supply-chain drift events since 2026-07-30, including ownership changes, install script additions, repository removals, unpublished packages, and name republications by new owners.

## Facts

- Endpoint: POST https://pulsefeed.dev/mcp/drift/history
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pulsefeed-mcp-supply-chain-drift-history-840a1834
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iJqLit5vMbkLwuRhGL1IF

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability pulsefeed-mcp-supply-chain-drift-history-840a1834 -d '<json body>'
```

Example prompt: Pull the full MCP registry supply-chain drift history from PulseFeed — I want every recorded event since 2026-07-30, including ownership swaps, install script additions, removed repositories, unpublished packages, and names republished by someone new.

## When to prefer this

Choose this endpoint when you need the complete longitudinal drift history across the entire MCP registry — not just current state — especially for supply-chain security audits, dependency risk assessments, or forensic investigation of when a specific package changed. Unlike point-in-time lookups, this series preserves events that cannot be reconstructed after the fact because they rely on historical snapshots. Prefer this over individual package lookups when you need cross-registry breadth or a full timeline.

## Known failure modes

- Request outside free 7-day window without payment may return partial or gated data
- No events returned if registry was stable in the queried period
- Snapshot gaps may mean some drift events between infrequent snapshots are not captured
- Payment failure via x402 results in 402 response with no data
- Malformed POST body returns 400 with validation error

## How this service works

The full MCP supply-chain drift series in one call: every recorded change since 2026-07-30 across the whole registry — ownership swapped, install script added in a later version, repository removed, package unpublished, a removed name republished by someone else. An event exists only because a snapshot from before it does, so this series cannot be rebuilt after the fact. Free feed: last 7 days.

## Output

A structured time-series of all recorded MCP registry supply-chain drift events since 2026-07-30, each event tagged by type (ownership transfer, install script added, repository removed, package unpublished, name republished by new owner), with before/after snapshot references, timestamps, and package identifiers. The free tier covers the last 7 days of events.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pulsefeed-mcp-supply-chain-drift-history-840a1834/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pulsefeed.dev](https://www.zero.xyz/host/pulsefeed.dev/llms.txt)