Security & Testing
pulsefeed.dev
Provides security and trust assessments for x402 endpoints and MCP servers, including liveness checks, audits, and ecosystem monitoring.
ENDPOINT 1
https://pulsefeed.dev/mcp-server
MCP server metadata
- Name
- pulsefeed-x402
- Version
- 1.0.5
PulseFeed — verify before you pay or install. Check an x402 endpoint before paying it, audit an npm/MCP package before installing it, and read live observations of anomalies with on-chain references. All tools here are free and read-only.
Known tools 10
check_x402_endpointBefore 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.
Inferred read-onlymcp_check_serverBefore 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.
Inferred read-onlymcp_security_reportState 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.
Inferred read-onlypulsefeed_productsList 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.
Potential side effectsx402_changesWhat changed in the x402 ecosystem recently: services that stopped returning a valid challenge, receiver (payTo) changes, price changes, recoveries, newly-seen services.
Inferred read-onlyx402_data_sampleFREE 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.
Inferred read-onlyx402_ecosystem_statsLive 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.
Potential side effectsx402_incidentsAnomalies observed in live x402 endpoints by continuous independent measurement: receiver-address changes between observations, catalog price vs.
Inferred read-onlyx402_leaderboardTop x402 services ranked by the open PulseFeed Trust Score (0-100), with price and network — the most reliable live agent-payment endpoints right now.
Potential side effectsx402_working_servicesList x402 agent-payment services that are currently ALIVE and return a valid x402 challenge, ranked by PulseFeed Trust Score, plus ecosystem risk map.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pulsefeed-x402]
url = "https://pulsefeed.dev/mcp-server"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pulsefeed-x402": {
"type": "http",
"url": "https://pulsefeed.dev/mcp-server"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pulsefeed-x402
Remote MCP URL: https://pulsefeed.dev/mcp-server
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pulsefeed-x402": {
"url": "https://pulsefeed.dev/mcp-server"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pulsefeed-x402": {
"type": "http",
"url": "https://pulsefeed.dev/mcp-server"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pulsefeed-x402",
"transport": "streamable-http",
"url": "https://pulsefeed.dev/mcp-server"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for pulsefeed.dev was fetched 2026-08-03T02:09:13.847Z.
pulsefeed.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.