x402 Triage MCP
NPM · X402-TRIAGE-MCP
MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.
Available components
Last scanned (59 minutes ago)
Scores higher than 94% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TateLyman/x402-triage-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 169 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 341 tokens (~85/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/x402-triage-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | TateLyman/x402-triage-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TateLyman/x402-triage-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 1573681874 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d48c6e4576c42e4328435f9f1400a7102ce161a7424cf1c97577ba5cbf7f360b1d7dac7d568470c4562679c6e7262341fdcc766f8d27f2c03dccc3650 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
triage_x402_surface Triage x402 payment surface ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | No-payment probe method. Use POST only for endpoints that intentionally expose a public paid POST route. |
| origin | string | – | Optional browser Origin for CORS/payment-header readability checks. |
| url | string | yes | Public HTTPS manifest, OpenAPI file, paid endpoint, or discovery URL to review. |
No output schema declared.
No examples provided.
watch_402_index Watch 402 Index listings ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| health | string | – | Optional health filter. |
| limit | number | – | Maximum records to return. |
| protocol | string | – | Protocol filter. |
| q | string | yes | 402 Index search term, provider name, domain, service URL, or endpoint URL. |
No output schema declared.
No examples provided.
x402_paid_paths Return x402 paid API paths ~35
Return the Tate Programs paid x402 API endpoints, service catalog, AgentCard, and fixed-scope review handoff URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the x402 Triage MCP server?
x402 Triage MCP runs locally as an npm package, launched with npx -y x402-triage-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · x402-triage-mcp
claude mcp add tatelyman-x402-triage-mcp -- npx -y x402-triage-mcp
What is the x402 Triage MCP server?
x402 Triage MCP is listed in the public MCP registry as io.github.TateLyman/x402-triage-mcp. MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff. This page covers its npm package (x402-triage-mcp).
Is the x402 Triage MCP server safe to use?
x402 Triage MCP scores 91 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the x402 Triage MCP server expose?
x402 Triage MCP exposes 3 tools: triage_x402_surface, watch_402_index, x402_paid_paths. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.
Is the x402 Triage MCP server still maintained?
x402 Triage MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the x402 Triage MCP server under?
x402 Triage MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.