x402-triage-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@x402-triage-mcp triage x402 surface on https://api.example.com/.well-known/x402"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
x402-triage-mcp
MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.
It exposes three MCP tools:
triage_x402_surfacechecks one public x402, MPP, Pay.sh, OpenAPI, manifest, or HTTP 402 endpoint through the Tate Programs public triage API.watch_402_indexsearches public 402 Index metadata for provider health, payment-validity, and domain-verification signals.x402_paid_pathsreturns the paid x402 API endpoints, service catalog, AgentCard, and fixed-scope review links.
The tools do not send X-PAYMENT, wallet signatures, API keys, private credentials, or paid calls.
Tool page: https://tateprograms.com/x402-surface-check.html
Paid x402 API catalog: https://tateprograms.com/services.json
AgentCard: https://the402.tateprograms.com/.well-known/agent-card.json
Install
Run directly with npx:
npx --yes x402-triage-mcpRelated MCP server: PreFlight
MCP Config
Add this server to an MCP client that supports stdio servers:
{
"mcpServers": {
"x402-triage": {
"command": "npx",
"args": ["--yes", "--package", "x402-triage-mcp", "x402-triage-mcp"]
}
}
}STDIO MCP client config launches a local command. Review the command, args, and any env values before running generated configs, and pin versions when repeatability matters.
Tools
triage_x402_surface
{
"url": "https://api.example.com/.well-known/x402",
"method": "GET",
"origin": "https://app.example.com"
}Returns status, payment headers, parsed challenge summary, attack-class checks, findings, and paid handoff paths.
watch_402_index
{
"q": "example.com",
"protocol": "x402",
"limit": 10
}Returns matching public 402 Index records, health summary, visible launch blockers, and paid handoff paths.
x402_paid_paths
Returns:
https://the402.tateprograms.com/api/x402/triagehttps://the402.tateprograms.com/api/x402/index-watchhttps://tateprograms.com/services.jsonhttps://tateprograms.com/x402-five-attack-review.htmlhttps://tateprograms.com/x402-fix-sprint.html
Payment And Safety Boundary
Use this server only on public launch surfaces that you own or are authorized to inspect. Do not submit private URLs, tokenized URLs, customer data, wallet seed phrases, or production secrets.
This MCP server is read-only. It does not initiate payments, send X-PAYMENT headers, sign wallet messages, call paid endpoints, create invoices, settle balances, or grant purchasing authority. The only paid paths it returns are static Tate Programs handoff URLs for teams that choose to buy a separate review.
For agent-commerce reviews, the server reports whether the target surface exposes the safety controls buyers expect before real spend is enabled:
Spend limits: per-call and total budget caps should be explicit before an agent can pay.
Approval checkpoints: payment setup and high-risk spend should require a visible user or policy approval step.
Recipient validation: paid requests should be constrained to expected domains, merchants, wallet addresses, or signed registry entries.
Replay protection: challenges and settlement callbacks should use nonces, expirations, idempotency keys, signed resources, or equivalent controls.
Metadata minimization: payment metadata should avoid private user context, secrets, and unnecessary resource detail.
Receipts and audit trails: successful payments should produce transaction IDs, recipient, amount, reason, and policy evidence.
Development
npm install
npm run checkAvailable Tools
3 toolstriage_x402_surfaceTriage x402 payment surfaceARead-onlyIdempotent
Run a no-payment external pass against one public x402, MPP, Pay.sh, OpenAPI, manifest, or HTTP 402 endpoint. The tool calls the Tate Programs public triage API and returns status, payment headers, parsed challenge shape, attack-class checks, cache/CORS notes, and paid review handoff. It does not send X-PAYMENT, wallet signatures, API keys, private tokens, or paid calls.
Inputs: url (required), method, origin.
watch_402_indexWatch 402 Index listingsARead-onlyIdempotent
Look up public 402 Index service records by provider, domain, endpoint URL, or search term. Use this before listing, outreach, launch review, or re-check work to spot down services, invalid payment requirements, and unverified domains. This is public metadata only and does not send payment headers or paid calls.
Inputs: q (required), limit, health, protocol.
x402_paid_pathsReturn x402 paid API pathsARead-onlyIdempotent
Return the Tate Programs paid x402 API endpoints, service catalog, AgentCard, and fixed-scope review handoff URLs.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct function: triaging a live endpoint, looking up public index metadata, and retrieving paid service paths. There is no overlap in purpose or output.
The naming convention is inconsistent: triage_x402_surface and watch_402_index follow a verb_noun pattern, but x402_paid_paths is a noun phrase. Additionally, the use of 'x402' vs '402' varies across tool names.
Three tools is well-scoped for a specialized triage service, covering the core actions without redundancy. Each tool earns its place in the set.
The set covers the main workflows: triage, index lookup, and paid path discovery. Minor gaps exist such as not offering a way to update index records, but these are likely external concerns.
Maintenance
Related MCP Connectors
402xAgent is the check an agent calls before paying any x402 endpoint. It probes the endpoint's 402 without paying and returns a pay / skip / recheck verdict with a reason. Every check leaves a public receipt. It never pays the target.
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence.
Authorize x402 payments before signing with request-bound, signed safety decisions.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceEnables MCP clients to use paid tools for secret scanning, agent-config auditing, and OG image rendering, with payments handled over the x402 protocol on Base.MIT- FlicenseNot gradedqualityCmaintenanceEnables agents to discover and verify paid agent services through x402 payment validation and release gate checks.-
- AlicenseAqualityAmaintenanceEnables agents and developers to check x402 endpoints, assess scores and wallet risks, authorize payments with spending rules, and report outcomes before an agent pays.62MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to fetch x402-paywalled URLs while enforcing spending policies, and to inspect budgets, recent payments, and policy rules. Flagged payments wait for human approval on the dashboard.381 npmMIT