{"uid":"cap_iJqLit5vMbkLwuRhGL1IF","slug":"pulsefeed-mcp-supply-chain-drift-history-840a1834","name":"PulseFeed MCP Supply-Chain Drift History","description":"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.","url":"https://pulsefeed.dev/mcp/drift/history","method":"POST","headers":{},"bodySchema":null,"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.1","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.1/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_iU2_erxjjRxpgW3MT7twz","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.1","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"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.","exampleAgentPrompt":"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.","exampleUseCases":[{"title":"Audit MCP dependencies for takeover risk","prompt":"Check the PulseFeed MCP drift history for any packages where ownership changed hands or a name was unpublished and republished by a different owner — I want to know if any of my agent's tools may have been hijacked."},{"title":"Detect install-script injection over time","prompt":"Pull the full MCP supply-chain drift history and show me every case where an install script was added in a later version of a package that didn't have one at first release — I'm looking for post-publication injection attacks."},{"title":"Compliance report on registry integrity","prompt":"I need a complete audit report of every MCP registry drift event recorded since 2026-07-30 — ownership changes, removed repos, unpublished packages, all of it — so I can document supply-chain integrity for our security review."}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T00:36:22.593Z","isFirstParty":false}