← All servers

P

pulsefeed-x402

connects

pulsefeed.dev

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

https://pulsefeed.dev/mcp-serverWebsiteNo authMCP 2026-07-28v1.0.7last checked 18 Oct 2026spoke MCP on 100% of 84 checks (30 days)initialize in 78 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http pulsefeed-x402 https://pulsefeed.dev/mcp-server

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://pulsefeed.dev/mcp-server.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://pulsefeed.dev/mcp-server.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "pulsefeed-x402": {
      "url": "https://pulsefeed.dev/mcp-server"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "pulsefeed-x402": {
      "type": "http",
      "url": "https://pulsefeed.dev/mcp-server"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 18 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 11 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

check_x402_endpointmcp_check_servermcp_drift_checkmcp_security_reportpulsefeed_productsx402_changesx402_data_samplex402_ecosystem_statsx402_incidentsx402_leaderboardx402_working_services

Contract history

8 Oct 2026v1.0.7no contract changes

2 Oct 2026v1.0.71 cosmeticinstructions rewritten

Instructions rewritten: pulsefeed_products. The description an agent follows changed; the callable contract may not have.

21 Sep 2026v1.0.73 breaking

Breaking: mcp_drift_check, x402_changes, x402_incidents

2 Sep 2026v1.0.7first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/pulsefeed-x402/badge.svg)](https://mcpi.app/servers/pulsefeed-x402)