Pulsefeed X402 MCP server
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.
0 stars48 downloads/wk
Reviews
Write oneNobody has reviewed Pulsefeed X402 yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pulsefeed X402 tools (11)
write = sends, deletes, buys or postscheck_x402_endpointFreeBefore paying an unknown x402 endpoint, check whether it is safe: liveness, trust score (0-100), anomaly flags (receiver address changed between observations, catalog price vs. challenge price, invalid receiver, testnet listed as production, scheme outside the x402 spec), receiver stability and observation-count-qualified uptime — with a pay/avoid verdict. Reads the challenge from both the response body and the v2 PAYMENT-REQUIRED header. Free.
mcp_check_serverFreeBefore installing an MCP server or npm package, audit it: does it run an INSTALL SCRIPT (arbitrary code execution at `npm i`), is it abandoned, does it ship a repository and license, weekly downloads, provenance — with a safe/caution/avoid verdict. ~11% of audited MCP servers run install scripts. Free.
mcp_drift_checkFreeThe rug pull check. `mcp_check_server` answers whether a package is safe TODAY; this answers what CHANGED after it was adopted: an install script added in a later version (arbitrary code on `npm i` that was not there at review time), package ownership swapped, repository removed, package unpublished, build provenance lost. Pass your own dependency list to check it in one call. Derived from a daily external re-audit of the whole MCP package population — an event exists only because a snapshot from before it exists. Free.
mcp_security_reportFreeState of MCP Security: how many audited MCP servers run an arbitrary install script, are abandoned, ship no repository or license — with day-over-day deltas and a sample of currently-flagged servers. From a daily audit of the MCP server catalog. Free.
pulsefeed_productsFreeList PulseFeed's products. All data endpoints are FREE since 2026-09-02 (trust checks, track records, datasets, drift history); only on-chain token signals are x402 pay-per-call. Formerly: deep trust check, endpoint track record, bulk trust dataset, and the cross-domain Data API. Includes the client-side spend-cap gotcha for x402-fetch.
x402_changesFreeWhat changed in the x402 ecosystem recently: services that stopped returning a valid challenge, receiver (payTo) changes, price changes, recoveries, newly-seen services. Derived from compounding time-series that cannot be reconstructed after the fact. Free.
x402_data_sampleFreeFREE sample of the PulseFeed Data API: top-10 live x402 services as FULL records (compounding payTo/price history, anomaly flags, on-chain receiver profile), top-10 MCP servers with full audit profile, and 3 live incidents.
x402_ecosystem_statsFreeLive health of the whole x402 agent-payment ecosystem: tracked/alive/dead counts, catalog-accuracy audit (what share of listings called 'healthy' actually work), risk-level distribution, receiver stability and on-chain receiver profiles. Free.
x402_incidentsFreeAnomalies observed in live x402 endpoints by continuous independent measurement: receiver-address changes between observations, catalog price vs. challenge price mismatches, invalid receivers, testnet endpoints listed as production, payment schemes outside the x402 spec — EACH WITH AN ON-CHAIN REFERENCE on Base. Measurements, not accusations of intent. Check before paying anything. Free.
x402_leaderboardFreeTop x402 services ranked by the open PulseFeed Trust Score (0-100), with price and network — the most reliable live agent-payment endpoints right now. Free.
x402_working_servicesFreeList x402 agent-payment services that are currently ALIVE and return a valid x402 challenge, ranked by PulseFeed Trust Score, plus ecosystem risk map. Use this to pick a service with a track record instead of paying an endpoint you have not checked. Free.
Public scan report
scanner v0.1.9 · 2026-09-21 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- Live reliabilityremote reachable in 1871ms20/20
- Tool poisoning11 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the Pulsefeed X402 repository's README, as published. We do not edit it. Read it on GitHub
PulseFeed
Verify before you pay or install.
Two questions an agent has to answer before it acts, and neither is answered by a scanner that only looks at the present:
(receiver swapped, catalog price ≠ challenge price, honeypot receiver, testnet listed as production), with a pay/avoid verdict and on-chain proof links on Base.
- Is this x402 endpoint safe to pay? — liveness, a 0–100 trust score, scam flags
script added in a later version, ownership swapped, repository removed, package unpublished, build provenance lost.
- Did this MCP server or npm package change after people adopted it? — an install
The second question is the one static scanners cannot answer. A rug pull is clean at review time by construction: the package collects installs for weeks, and only then ships the patch that runs code on npm i. Answering it requires yesterday's snapshot to exist, which is why the series here starts on 2026-07-30 and cannot be reconstructed after the fact.
PulseFeed re-audits the whole MCP registry every night and diffs it against the previous day's snapshot, and re-probes the x402 endpoint population daily. Everything below is free, needs no key, and no account.
MCP server
Hosted, no install:
https://pulsefeed.dev/mcp-serverStreamable HTTP. Also on the official MCP registry, Smithery and Glama.
Or run it locally — see mcp/:
npx pulsefeed-x402-mcpTools include checkx402endpoint (is this endpoint safe to pay), mcpcheckserver (audit before installing), mcpdriftcheck (the rug-pull check — pass your own dependency list), mcpsecurityreport, x402incidents and x402changes.
Drift badge
Put it in your README. It states what changed in your package after people adopted it:
[](https://pulsefeed.dev/mcp/drift)Use your registry name (io.github.you/your-server) or your npm package name.
A green badge is a public claim about your package, so it is only issued when the package is actually in our snapshot. When it is not, the badge reads unwatched in grey — never green. Reporting absence of measurement as evidence of cleanliness is a mistake we made once publicly and will not repeat; see the correction.
CI check
Fails the build when something you already depend on changes dangerously:
- uses: Nikolife2016/mcp-drift-action@v1Marketplace · source. Run it on a schedule, not only on pull requests — drift happens between your commits.
Free API
No key, CORS enabled, safe to call from a browser or a catalog page:
# what changed, whole registry
curl -s "https://pulsefeed.dev/mcp/drift.json?days=7"
# only your dependencies
curl -s "https://pulsefeed.dev/mcp/drift.json?packages=pkg-a,pkg-b&days=7"
# is this x402 endpoint payable
curl -s "https://pulsefeed.dev/verify?endpoint=<url>"Subscribe without signing up — the filter lives in the URL, so there is no subscriber database and nothing to leak:
https://pulsefeed.dev/mcp/drift.rss?packages=pkg-a,pkg-bFull spec: /openapi.json.
Open data
- Live feed: pulsefeed.dev/mcp/drift
- Ecosystem state: pulsefeed.dev/status.json
- Dataset: Nikolife/pulsefeed-x402-security
On being wrong in public
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add --transport http pulsefeed-x402 https://pulsefeed.dev/mcp-server
Pulsefeed X402: common questions
- Is Pulsefeed X402 MCP server safe?
- Yes, by our scan: it is graded A (93/100). Read the Pulsefeed X402 safety report
- How do I install Pulsefeed X402?
- It runs remotely at pulsefeed.dev. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Pulsefeed X402 need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Pulsefeed X402 maintained?
- The last commit was in the last day (2026-09-21). The latest release is v1.1.0.
- Is Pulsefeed X402 up?
- 100% of our last 14 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Pulsefeed X402?
- Servers from other publishers that do the same job: three.ws Agent Payments MCP server, X402 List MCP server and PipRail MCP server. Compare all Pulsefeed X402 alternatives.
Alternatives to Pulsefeed X402
Same job from other publishers: the closest match first, then the best rated.
three.ws Agent PaymentsGoverned x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.not reviewedEstablishedB
X402 ListFind and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.not reviewedEstablishedA- PipRailBudget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.not reviewedGrowingB
- X402lintLint an HTTP endpoint's x402 402 conformance; decode X-PAYMENT blobs; inspect a facilitator.not reviewedGrowingA
- gate402 merchant checkoutDrop-in x402 checkout for merchants: issue terms, verify payment. $0.01 each.not reviewedGrowingA
