X402 Triage MCP
Triage HTTP x402 payment surfaces, check 402 Index health, and route paid human review when your agent implements or audits paywalled APIs.
Overview
x402 Triage MCP is an MCP server for the Ship phase that triages x402 payment surfaces without payment, validates 402 Index health, and supports paid review escalation.
What is this MCP server?
- No-payment x402 surface triage from the agent
- 402 Index health checks for protocol alignment
- Handoff path to paid review when automated triage is insufficient
- stdio npm package x402-triage-mcp (v0.1.1)
- Package version 0.1.1
- Transport: stdio via npm identifier x402-triage-mcp
- Capabilities: no-payment triage, 402 Index health, paid review handoff
What problem does it solve?
You added x402 or 402-gated endpoints but are unsure the surface, index, and error behavior are safe to launch without a dedicated payments security consultant on day one.
Who is it for?
Solo API and agent-tool builders shipping experimental paid endpoints who want MCP-driven x402 hygiene before traffic arrives.
Skip if: Products with no HTTP 402 monetization, teams needing full PCI audits, or builders who want a generic OWASP scanner only.
What do I get? / Deliverables
You get structured triage and index health signal in the agent, plus a clear path to paid review when issues exceed self-serve checks.
- Triage notes on x402 exposure and configuration risks
- 402 Index health status suitable for launch checklists
- Documented handoff when paid review is recommended
Recommended MCP Servers
Journey fit
How it compares
Specialized x402 triage MCP, not a general payments SDK or Stripe dashboard integration.
Common Questions / FAQ
Who is X402 Triage MCP for?
Indie API and MCP authors implementing x402 payment surfaces who want agent-run triage and optional paid expert review.
When should I use X402 Triage MCP?
Use it during ship security work after x402 routes exist but before you promote them to production or list them in paid agent marketplaces.
How do I add X402 Triage MCP to my agent?
Add the x402-triage-mcp npm stdio server in your MCP client configuration and point tools at your staged x402 endpoints per the project docs.