x402 Conformance
OCI · GHCR.IO/ATSP-PROTOCOL/X402-CONFORMANCE · 2 COMPONENTS
x402 payment safety checks: validate a 402 answer, prove a server never serves before settlement.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of OCI servers
Category Testing and QA
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 811 tokens (~115/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "x402_check_payment_required" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Package version: 1.5.0 → 1.6.0 functional
- 24 Oct 26 +1
- Package version: 1.4.0 → 1.5.0 functional
- 23 Oct 26 38
First indexed and scored.
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 oci/ghcr.io/atsp-protocol/x402-conformance@1.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
x402_check_payment_required Check an x402 402 answer (P1-P7) ~131
Sends ONE unpaid GET to an x402 paid URL and checks its 402 answer against the x402 spec (P1-P7): HTTP 402, a decodable PAYMENT-REQUIRED header (V2) or JSON body (V1), x402Version, resource, accepts[], amounts in atomic units, CAIP-2 networks, and scheme fields (EVM name/version, Solana feePayer). Never pays or signs. Use it before paying an unfamiliar x402 endpoint, or to check your own route.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The paid URL, http or https |
No output schema declared.
No examples provided.
x402_demo Run the suite end to end on a built-in demo server ~82
Runs P1-P7 and R0-R10 against a built-in demo x402 server on loopback, with no wallet, no keys and no network. fault=serve_on_any_settle shows what a failing server looks like. Use it to see what the suite checks.
| Name | Type | Req | Description |
|---|---|---|---|
| fault | string | – | none (default) or serve_on_any_settle |
No output schema declared.
No examples provided.
x402_explain_check Explain a check and how to fix it ~80
Returns what a check (S0-S4, P1-P7, F1-F11, R0-R11) tests, why it matters for the seller's money, and how to fix a failure, from the suite's FIXES.md.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Check id, e.g. R3 or P5 |
No output schema declared.
No examples provided.
x402_probe_resource_server Probe your resource server (R0-R10) ~154
Grades your x402 resource server under fault injection (R0-R10): it must never serve content on a /settle timeout, an HTML 502, a 503 with a success body, a non-JSON or truncated answer, settlement_pending, a failed transaction or a duplicate payment. Pays with test payloads through the facilitator double only; the URL must be on loopback and your server must use the double (x402_start_facilitator_double) as its facilitator.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network to pay on; default auto |
| resource_url | string | yes | Your paid route on loopback, e.g. http://127.0.0.1:4020/paid |
No output schema declared.
No examples provided.
x402_share_case Prepare an anonymised corpus case ~116
Turns a failing report into an anonymised case for the public x402 failure corpus (no URLs, hosts, IPs, addresses or transaction data) and returns a link to a pre-filled GitHub issue. Sends nothing: show the case and the link to the user, who decides whether to submit it.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | – |
| network | string | – | – |
| report | object | yes | A report returned by another x402 tool |
| sdk | string | – | – |
| sdk_version | string | – | – |
No output schema declared.
No examples provided.
x402_start_facilitator_double Start the facilitator double ~107
Starts the x402 facilitator double on 127.0.0.1 and returns its URL. Start YOUR resource server with this URL as its facilitator (for example X402_FACILITATOR_URL) and offering Solana devnet or Base Sepolia, then call x402_probe_resource_server. The double never touches a chain, key or network beyond loopback.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | – | Loopback port; 0 or omitted picks a free one |
No output schema declared.
No examples provided.
x402_stop_facilitator_double Stop the facilitator double ~27
Stops the facilitator double started by x402_start_facilitator_double.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the x402 Conformance MCP server?
x402 Conformance runs locally as a container image, launched with docker run --rm -i ghcr.io/atsp-protocol/x402-conformance:1.6.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/atsp-protocol/x402-conformance
claude mcp add atsp-protocol-x402-conformance -- docker run --rm -i ghcr.io/atsp-protocol/x402-conformance:1.6.0
What is the x402 Conformance MCP server?
x402 Conformance is an MCP server listed in the public MCP registry as io.github.atsp-protocol/x402-conformance. x402 payment safety checks: validate a 402 answer, prove a server never serves before settlement. This page covers its container image (ghcr.io/atsp-protocol/x402-conformance).
Is the x402 Conformance MCP server safe to use?
x402 Conformance scores 44 out of 100 on VerifyMCP. 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 Conformance MCP server expose?
x402 Conformance exposes 7 tools: x402_check_payment_required, x402_demo, x402_explain_check, x402_share_case, x402_start_facilitator_double, and 2 more. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.
Is the x402 Conformance MCP server still maintained?
x402 Conformance 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 Conformance MCP server under?
x402 Conformance declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.