# x402 Conformance (oci · ghcr.io/atsp-protocol/x402-conformance) x402 payment safety checks: validate a 402 answer, prove a server never serves before settlement. - Trust score: 44/100 (low) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - npm · `x402-conformance-mcp`: 39/100, [markdown](https://verifymcp.io/servers/atsp-protocol-x402-conformance/x402-conformance-mcp.md), [page](https://verifymcp.io/servers/atsp-protocol-x402-conformance/x402-conformance-mcp) - oci · `ghcr.io/atsp-protocol/x402-conformance`: 44/100 (this document), [markdown](https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance.md), [page](https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance) ## Channel facts - Registry: `oci` - Package: `ghcr.io/atsp-protocol/x402-conformance` - Version: `1.6.0` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - 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. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (Apache-2.0). - Actively maintained (last published 11 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 73/100 - AI-judged instruction clarity (good). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 43/100 - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 88/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 64% of tool parameters carry a description. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 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. - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **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. ## Install ### 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. ### Claude ```bash claude mcp add atsp-protocol-x402-conformance -- docker run --rm -i ghcr.io/atsp-protocol/x402-conformance:1.6.0 ``` ### Cursor ```json { "mcpServers": { "atsp-protocol-x402-conformance": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0" ] } } } ``` ### VS Code ```json { "servers": { "atsp-protocol-x402-conformance": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0" ] } } } ``` ### Codex ```bash codex mcp add atsp-protocol-x402-conformance -- docker run --rm -i ghcr.io/atsp-protocol/x402-conformance:1.6.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "atsp-protocol-x402-conformance": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: atsp-protocol-x402-conformance: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0"] ``` ### Netclaw ```json { "McpServers": { "atsp-protocol-x402-conformance": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0" ] } } } ``` ### Other ```json { "mcpServers": { "atsp-protocol-x402-conformance": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/atsp-protocol/x402-conformance:1.6.0" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 44, +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. ### 2026-11-02 (score 43, +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. ### 2026-10-30 (score 42, +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. ### 2026-10-28 (score 41, +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. ### 2026-10-26 (score 40, +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. ### 2026-10-25 (score 39, 0) - [functional] Package version: 1.5.0 → 1.6.0 ### 2026-10-24 (score 39, +1) - [functional] Package version: 1.4.0 → 1.5.0 ### 2026-10-23 (score 38) First indexed and scored. ## MCP tools (7) ### `x402_check_payment_required` (~131 tokens) Check an x402 402 answer (P1-P7) 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. Input parameters: - `url` (string, required): The paid URL, http or https ### `x402_demo` (~82 tokens) Run the suite end to end on a built-in demo server 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. Input parameters: - `fault` (string): none (default) or serve_on_any_settle ### `x402_explain_check` (~80 tokens) Explain a check and how to fix it 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. Input parameters: - `id` (string, required): Check id, e.g. R3 or P5 ### `x402_share_case` (~116 tokens) Prepare an anonymised corpus case 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. Input parameters: - `framework` (string) - `network` (string) - `report` (object, required): A report returned by another x402 tool - `sdk` (string) - `sdk_version` (string) ### `x402_start_facilitator_double` (~107 tokens) Start the facilitator double 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. Input parameters: - `port` (integer): Loopback port; 0 or omitted picks a free one ### `x402_probe_resource_server` (~154 tokens) Probe your resource server (R0-R10) 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. Input parameters: - `network` (string): Network to pay on; default auto - `resource_url` (string, required): Your paid route on loopback, e.g. http://127.0.0.1:4020/paid ### `x402_stop_facilitator_double` (~27 tokens) Stop the facilitator double Stops the facilitator double started by x402_start_facilitator_double. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance#diagnostics ## Score history - 2026-11-05: 44 - 2026-11-04: 44 - 2026-11-03: 43 - 2026-11-02: 43 - 2026-11-01: 42 - 2026-10-31: 42 - 2026-10-30: 42 - 2026-10-29: 41 - 2026-10-28: 41 - 2026-10-27: 40 - 2026-10-26: 40 - 2026-10-25: 39 - 2026-10-24: 39 - 2026-10-23: 38 ## Common questions ### 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. ## Links - GitHub Container Registry: https://ghcr.io/atsp-protocol/x402-conformance - Repository: https://github.com/atsp-protocol/x402-conformance - Website: https://github.com/atsp-protocol/x402-conformance/blob/main/docs/USING.md - Changelog RSS feed: https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance.xml - Changelog JSON feed: https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance.json - HTML version of this page: https://verifymcp.io/servers/atsp-protocol-x402-conformance/ghcr-io-atsp-protocol-x402-conformance