Nikolife/pulsefeed-x402-security

PulseFeed — x402 Agent-Payment Security & Trust (open data)

Independent, daily-updated trust & safety data for the x402 agent-payment economy (HTTP 402 + stablecoins on Base) and the MCP server ecosystem — by PulseFeed.

AI agents increasingly pay for APIs autonomously over x402 and connect to MCP servers that can run code on install. But ~76% of listed x402 endpoints are dead or invalid, and among the live ones there are recurring scams. This dataset is the free, public slice of PulseFeed's continuous audit. Last updated: 2026-07-22T04:00:02+00:00.

The audit, incident feed and reports are free and open. Live pages: /incidents · /status · /reports. Machine feeds: /incidents.json · /incidents.rss. Full per-service cross-domain data feed (paid, x402): /data.

Files

File	What
incidents.csv / incidents.json	Active security incidents in the x402 economy — receiver hijacks, bait-and-switch pricing, honeypots, unverified receivers, price gouging — each with an on-chain proof URL.
ecosystem.json	Ecosystem aggregates: totals & dead %, catalog-accuracy audit, risk distribution, receiver-stability & on-chain receiver-profile distributions, top providers.
mcp_security.json	MCP server security summary: how many audited servers run an install script, are abandoned, ship no repo, etc.

incidents schema

Field	Meaning
category	payto_hijack | bait_and_switch | honeypot | unverified_receiver | price_gouging | asset_mismatch | went_dark
severity	high | medium
at	ISO timestamp of the observation
domain / endpoint	the x402 service
network	payment network (e.g. base)
detail	plain-language description of the finding
payTo	the receiver address
onchain_proof_url	Base block-explorer link to verify the receiver yourself
flags	raw detector flags (`

Honesty note

Findings are stated as facts from the data, not accusations of intent. "bait-and-switch" = advertised price != amount actually charged; "unverified receiver" = payTo has no on-chain USDC history (a risk signal, not a conviction); "possible hijack" = receiver changed on an established baseline (could be a legitimate key rotation). By-design receiver rotation is excluded.

Why it's unique

The signals here (receiver-stability over time, payTo/price change history, on-chain receiver profiles) are longitudinal — derived from continuously re-probing endpoints and recording changes as they happen. This history cannot be reconstructed after the fact.

License & attribution

CC-BY-4.0. Attribution: "x402/MCP trust data by PulseFeed (pulsefeed.dev)". The full per-service cross-domain feed is a separate paid product at pulsefeed.dev/data.

Writeup: I audited the entire x402 agent-payment economy — 76% is dead, and the live half has scams.