Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Nikolife2016/pulsefeed-x402

NPM · PULSEFEED-X402-MCP · 2 COMPONENTS · SCANNED SEP 20

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

−1 this week 89 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Nikolife2016/pulsefeed-x402). View diagnostics → Pass
  • License check failed: no license is declared. See how to fix → Fail
  • Actively maintained (last published 44 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 192 tokens (~64/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Nikolife2016/pulsefeed-x402 MCP server?

io.github.Nikolife2016/pulsefeed-x402 runs locally as an npm package, launched with npx -y pulsefeed-x402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · pulsefeed-x402-mcp

# add to Claude Code
claude mcp add nikolife2016-pulsefeed-x402 -- npx -y pulsefeed-x402-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "nikolife2016-pulsefeed-x402": {
      "command": "npx",
      "args": [
        "-y",
        "pulsefeed-x402-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nikolife2016-pulsefeed-x402": {
      "command": "npx",
      "args": [
        "-y",
        "pulsefeed-x402-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add nikolife2016-pulsefeed-x402 -- npx -y pulsefeed-x402-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nikolife2016-pulsefeed-x402": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pulsefeed-x402-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nikolife2016-pulsefeed-x402 --command npx --arg -y --arg pulsefeed-x402-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nikolife2016-pulsefeed-x402:
    command: "npx"
    args: ["-y", "pulsefeed-x402-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nikolife2016-pulsefeed-x402": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pulsefeed-x402-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add nikolife2016-pulsefeed-x402 -t stdio -c npx -a -y pulsefeed-x402-mcp
// mcp.json
{
  "mcpServers": {
    "nikolife2016-pulsefeed-x402": {
      "command": "npx",
      "args": [
        "-y",
        "pulsefeed-x402-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 19 Sept 26 +1
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 12 Sept 26 +1
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/pulsefeed-x402-mcp@1.0.7

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Nikolife2016/pulsefeed-x402
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Nikolife2016/pulsefeed-x402/.github/workflows/publish-mcp.yml@refs/heads/master
Rekor log index 2355960319
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:9ef4bb01f982527447b5b3c5df5062e4fb091c386366fdde14802b5263393df11f17dea6bce26f97fe772c00f2ba29dae31a3a7f209ea4518e1609c70

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~192 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_x402_endpoint ~75

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.

NameTypeReqDescription
urlstringyesThe x402 endpoint URL to verify

No output schema declared.

No examples provided.

pulsefeed_products ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_working_services ~60

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.Nikolife2016/pulsefeed-x402 MCP server?

io.github.Nikolife2016/pulsefeed-x402 is an MCP server listed in the public MCP registry as io.github.Nikolife2016/pulsefeed-x402. Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores. This page covers its npm package (pulsefeed-x402-mcp).

Is the io.github.Nikolife2016/pulsefeed-x402 MCP server safe to use?

io.github.Nikolife2016/pulsefeed-x402 scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Nikolife2016/pulsefeed-x402 MCP server expose?

io.github.Nikolife2016/pulsefeed-x402 exposes 3 tools: x402_working_services, check_x402_endpoint, pulsefeed_products. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.

Is the io.github.Nikolife2016/pulsefeed-x402 MCP server still maintained?

io.github.Nikolife2016/pulsefeed-x402 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.