{
  "id": 15102683,
  "title": "mcpreflight scanned all 293 x402 payment endpoints in the MCP registry. They pass handshakes at 74.4%, well above the rest.",
  "url": "https://urgent.news/2026/10/17/mcpreflight-scanned-all-293-x402-payment-endpoints-in-the-mcp",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-17T02:56:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/eidon_ze_598ff4e987ed54d2/mcpreflight-scanned-all-293-x402-payment-endpoints-in-the-mcp-registry-they-pass-handshakes-at-5k0"
  },
  "original_language": "en",
  "account": "mcpreflight, a read-only checker for MCP servers and x402 endpoints, recently scanned 293 payment endpoints in the MCP registry. The scan revealed that 74.4% of these endpoints passed handshakes, a rate significantly higher than the registry-wide baseline of 48.8%. This is the second report from mcpreflight, with the first one covering the entire registry. The gap in handshake rates is due to the unique requirements of payment servers, which must maintain a clean handshake specification for commercial reasons. However, the rate is fragile and may change as agent payment volume grows. If you run an x402 endpoint, there's no need to fix anything if it passes the check. To ensure your endpoint remains compliant, you can run the same check in your CI pipeline. This number is worth keeping fresh as it provides a trend rather than a one-time snapshot, and the raw data is publicly available.",
  "summary": "mcpreflight scanned all 293 x402 payment endpoints in the MCP registry. They pass handshakes at 74.4%, well above the rest. This is the second report from mcpreflight, a read-only checker for MCP servers and x402 endpoints. The first one covered the whole registry. This one zooms into the payment corner of it, because that corner behaves differently and nobody has the numbers. what we measured We…",
  "key_points": [
    "mcpreflight scanned 293 payment endpoints in MCP registry",
    "74.4% passed handshakes, above 48.8% baseline",
    "Gap due to payment servers' unique handshake requirements"
  ],
  "editors_take": "The high handshake success rate among payment endpoints reflects the commercial necessity for strict specification compliance, though these standards face potential instability as agent payment volumes increase.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}