Check public x402 surfaces before an agent spends.

`x402-triage-mcp` gives MCP clients three read-only tools for public 402 challenge checks, 402 Index health lookups, and paid review handoff paths. It never sends wallet signatures, `X-PAYMENT`, private credentials, or paid calls.

open repo npm package mcp registry browser check

price: free
package: 0.1.1
mode: no-payment

install

$ npx --yes --package x402-triage-mcp x402-triage-mcp

tools:
  triage_x402_surface
  watch_402_index
  x402_paid_paths

boundary:
  no wallet signatures
  no payment headers
  no paid calls

tools

Three MCP tools for the first launch pass.

registry proof

triage_x402_surface

Public 402 route check

Checks one manifest, OpenAPI URL, direct endpoint, or pasted challenge for CORS, cache policy, resource binding, declared price, and launch-control findings.

watch_402_index

Index health lookup

Searches public 402 Index metadata by provider, host, URL, health state, and protocol so broken paid routes can be found before buyers hit them.

x402_paid_paths

Handoff paths

Returns the live paid x402 endpoints, AgentCard, service catalog, and fixed-scope review links when a public no-payment triage needs a deeper private pass.

boundary

Spend stays out of scope

The server does not submit payment headers, sign wallet messages, access private accounts, or call paid endpoints. It is built for pre-spend inspection.

config

Drop it into an MCP client with `npx`.

mcp.json

{
  "mcpServers": {
    "x402-triage": {
      "command": "npx",
      "args": [
        "--yes",
        "--package",
        "x402-triage-mcp",
        "x402-triage-mcp"
      ]
    }
  }
}

fit

Use it when the public launch surface needs proof, not a wallet.

send surface

registry pr

Before listing

Check whether a registry PR points to a route that returns a real 402, has readable payment headers, and names the exact paid resource.

provider

Before buyers arrive

Look for degraded 402 Index listings, stale metadata, routes that return 200/401/500 instead of a challenge, or browser preflight blockers.

review

Before private work

Use the free MCP tool to decide whether a paid fix sprint is justified, then keep any route-specific patch notes private-first.