mcp server
pulsefeed-x402
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.
Description as published by the maintainer. Source
- version 1.0.7
- active
active — Registry entry last updated 2026-08-06.
What this server can do
11 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_x402_endpoint(url)- Before 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. Required: url.
mcp_check_server(package)- Before 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. Required: package.
mcp_drift_check(days, packages)- The 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_report- State 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_products- List PulseFeed's paid products and how to pay via x402 (USDC on Base): 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_changes(days)- What 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_sample- FREE 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_stats- Live 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_incidents(days)- Anomalies 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_leaderboard- Top 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_services- List 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.
Last successful function declaration observed on . Source: https://pulsefeed.dev/mcp-server. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://pulsefeed.dev/mcp-server.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.7 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 11 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | pulsefeed.dev | |
| mcp endpoint status | ok | The server listed 11 functions when asked. | as of probe | pulsefeed.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json