Skip to main content
Glama

PulseFeed

Wellknown npm

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:

  • Is this x402 endpoint safe to pay? — liveness, a 0–100 trust score, scam flags (receiver swapped, catalog price ≠ challenge price, honeypot receiver, testnet listed as production), with a pay/avoid verdict and on-chain proof links on Base.

  • Did this MCP server or npm package change after people adopted it? — an install script added in a later version, ownership swapped, repository removed, package unpublished, build provenance lost.

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-server

Streamable HTTP. Also on the official MCP registry, Smithery and Glama.

Or run it locally — see mcp/:

npx pulsefeed-x402-mcp

Tools include check_x402_endpoint (is this endpoint safe to pay), mcp_check_server (audit before installing), mcp_drift_check (the rug-pull check — pass your own dependency list), mcp_security_report, x402_incidents and x402_changes.

Related MCP server: x402 Preflight

Drift badge

Put it in your README. It states what changed in your package after people adopted it:

[![MCP drift](https://pulsefeed.dev/badge/mcp.svg?package=YOUR-PACKAGE)](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@v1

Marketplace · 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-b

Full spec: /openapi.json.

Open data

On being wrong in public

We once published that 76% of x402 endpoints were dead. That measured our own parser, not the market, and the figure was corrected twice more after that — each time downward, each time for the same class of reason: our own behaviour recorded as somebody else's track record. The whole mechanism, every correction and the checklist that came out of it are kept at pulsefeed.dev/correction rather than quietly deleted.

If you find a number here that does not hold, open an issue — that page is where it will end up.

What's in this repository

mcp/

the MCP server (pulsefeed-x402-mcp on npm)

lint/

x402-payable — is your x402 endpoint actually payable

data/

published series and snapshots

server.json

manifest for the official MCP registry

License

MIT

Available Tools

3 tools
check_x402_endpointAInspect

Before paying an unknown x402 endpoint, check whether it is live and returns a valid x402 payment challenge. Returns liveness, price, network and a pay/avoid verdict. For full uptime + reputation, use PulseFeed's paid /trust API.

Inputs: url (required).

pulsefeed_productsAInspect

List PulseFeed's paid x402 products — real-time Base on-chain intelligence for AI agents: token pulse, whale alerts, smart-money accumulation/distribution, momentum, and the x402 trust oracle — and how to pay via x402.

Inputs: no named parameters.

x402_working_servicesAInspect

List x402 agent-payment services that are currently ALIVE and return a valid x402 challenge, ranked by trust score. About 85% of x402 endpoints are dead or invalid — use this to avoid paying broken or scam endpoints. Free.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing live services, checking a specific endpoint, and listing paid products. No overlap in functionality.

    Naming Consistency4/5

    Uses snake_case consistently, but the prefix varies ('x402_', 'check_x402_', 'pulsefeed_'), so the pattern is not fully uniform though still clear.

    Tool Count4/5

    Three tools is slightly low but appropriate for the focused domain of x402 endpoint discovery and product listing; each tool earns its place.

    Completeness3/5

    Core workflow is covered (list live endpoints, check endpoint, list products), but missing tools to actually pay or access detailed trust data from the paid API.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Archived and no longer maintained. Tools and prices shown here are out of date. Use the maintained server: glama.ai/mcp/servers/OceanAlt666/oceanalt-aml-mcp (GitHub: OceanAlt666/oceanalt-aml-mcp).
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents to inspect and audit unfamiliar x402 endpoints before spending USDC, using bounded read-only probes to surface payment challenges, pricing, network, receiver, and operational signals without signing or spending funds.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Pay-per-call checks an AI agent runs before it moves money: token safety verdicts and wallet risk profiles on Base, on-chain payment verification, IBAN/VAT/BIC/LEI/ISIN validation, and live TLS and email-spoofing posture for a domain. Paid in USDC over x402 with no API key or account; the free payment_info tool explains the pricing.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      alalanet-agent is the open local client of alalanet.com, the free service an AI agent asks before it installs, connects or pays. A stdio MCP server whose key stays on your machine: it signs agent passports, receipts, skill and package releases, mail and memory locally (16 tools) and checks files and agents against alalanet's public transparency log. Hosted checks: https://alalanet.com/mcp.
      2
      16
      Apache 2.0