io.github.Nikolife2016/pulsefeed-x402
REMOTE · PULSEFEED.DEV · 2 COMPONENTS · SCANNED SEP 20
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 981 tokens (~89/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Nikolife2016/pulsefeed-x402 MCP server?
io.github.Nikolife2016/pulsefeed-x402 is a hosted endpoint at https://pulsefeed.dev/mcp-server, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pulsefeed.dev
claude mcp add --transport http nikolife2016-pulsefeed-x402 'https://pulsefeed.dev/mcp-server'
{
"mcpServers": {
"nikolife2016-pulsefeed-x402": {
"url": "https://pulsefeed.dev/mcp-server"
}
}
} {
"servers": {
"nikolife2016-pulsefeed-x402": {
"type": "http",
"url": "https://pulsefeed.dev/mcp-server"
}
}
} [mcp_servers.nikolife2016-pulsefeed-x402] url = "https://pulsefeed.dev/mcp-server"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nikolife2016-pulsefeed-x402": {
"type": "remote",
"url": "https://pulsefeed.dev/mcp-server",
"enabled": true
}
}
} openclaw mcp add nikolife2016-pulsefeed-x402 --url 'https://pulsefeed.dev/mcp-server' --transport streamable-http
mcp_servers:
nikolife2016-pulsefeed-x402:
url: "https://pulsefeed.dev/mcp-server" {
"McpServers": {
"nikolife2016-pulsefeed-x402": {
"Transport": "http",
"Url": "https://pulsefeed.dev/mcp-server"
}
}
} assistant mcp add nikolife2016-pulsefeed-x402 -t streamable-http -u 'https://pulsefeed.dev/mcp-server'
{
"mcpServers": {
"nikolife2016-pulsefeed-x402": {
"type": "http",
"url": "https://pulsefeed.dev/mcp-server"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Sept 26 0
- Tool “pulsefeed_products” rewrote its description, which is the text the model reads security
- 29 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Server version: 1.0.6 → 1.0.7 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Schema quality: 792 → 954 ▼ functional
- Server version: 1.0.5 → 1.0.6 functional
- New tool “mcp_drift_check” functional
- 6 Aug 26 0
- Tool “mcp_security_report” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
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 · Probed https://pulsefeed.dev/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pulsefeed.dev | CN=YE1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 66406ea26f82b98db01871b304199bcd874 |
| SANs: pulsefeed.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pulsefeed.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pulsefeed.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pulsefeed.dev/mcp-server | Verified | 200 | |
| http (plaintext) | http://pulsefeed.dev/mcp-server | HTTPS enforced | 308 | https://pulsefeed.dev/mcp-server |
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 →
check_x402_endpoint Check an x402 endpoint before paying ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The x402 endpoint URL to verify |
No output schema declared.
No examples provided.
mcp_check_server Audit an MCP server before installing ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | npm package name of the MCP server, e.g. @scope/name |
No output schema declared.
No examples provided.
mcp_drift_check Has an MCP package changed since you trusted it? ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Window in days (default 30) |
| packages | array | – | npm package names to check, e.g. your installed MCP servers. Omit for the whole ecosystem feed. |
No output schema declared.
No examples provided.
mcp_security_report State of MCP security ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pulsefeed_products PulseFeed products and pricing ~87
List 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_changes Recent x402 ecosystem changes ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Window in days (default 7) |
No output schema declared.
No examples provided.
x402_data_sample Free sample of the trust dataset ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_ecosystem_stats x402 ecosystem health stats ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_incidents Live x402 security incidents ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (default 30) |
No output schema declared.
No examples provided.
x402_leaderboard x402 trust leaderboard ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_working_services List live x402 services ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 hosted endpoint (https://pulsefeed.dev/mcp-server).
Is the io.github.Nikolife2016/pulsefeed-x402 MCP server safe to use?
io.github.Nikolife2016/pulsefeed-x402 scores 86 out of 100 on VerifyMCP. 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 11 tools: check_x402_endpoint, mcp_check_server, mcp_drift_check, mcp_security_report, pulsefeed_products, and 6 more. Their descriptions and schemas cost roughly 929 tokens of context every time the server is loaded.
Does the io.github.Nikolife2016/pulsefeed-x402 MCP server require authentication?
No. We connected to io.github.Nikolife2016/pulsefeed-x402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.