io.github.Nikolife2016/pulsefeed-x402

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "pulsefeed-x402": {
      "url": "https://pulsefeed.dev/mcp-server",
      "transport": "streamable-http"
    }
  }
}

Measured tools (11)

• check_x402_endpoint read-only

  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.

  Parameters:

  • url (required) — string — The x402 endpoint URL to verify

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• mcp_check_server read-only

  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.

  Parameters:

  • package (required) — string — npm package name of the MCP server, e.g. @scope/name

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• mcp_drift_check read-only

  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.

  Parameters:

  • days — integer — Window in days (default 30)
  • packages — array — npm package names to check, e.g. your installed MCP servers. Omit for the whole ecosystem feed.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• mcp_security_report read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• pulsefeed_products read-only

  List PulseFeed's paid products and how to pay via x402 (USDC on Base): deep trust check, endpoint track record, bulk trust dataset, full MCP drift series, the cross-domain Data API and on-chain token signals. Includes the client-side spend-cap gotcha for x402-fetch.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_changes read-only

  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.

  Parameters:

  • days — integer — Window in days (default 7)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_data_sample read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_ecosystem_stats read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_incidents read-only

  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.

  Parameters:

  • days — integer — Look-back window in days (default 30)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_leaderboard read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• x402_working_services read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.