402MCP.org — HTTP 402 & Agent Payment Registry
REMOTE · 402MCP.ORG · 2 COMPONENTS
Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry.
Available components
Last scanned (8 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 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 1663 tokens (~63/item across 26 items; 7 tools + 19 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 70
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 18 Oct 2026 · Probed https://402mcp.org/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=402mcp.org | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7c5c587920bdc2d5135a983d157cad08 |
| SANs: 402mcp.org, www.402mcp.org, *.www.402mcp.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 402mcp.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| 402mcp.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://402mcp.org/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://402mcp.org/api/v1/mcp | Inconclusive | 405 |
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 →
decode_402_challenge Decode an HTTP 402 response ~212
Call this whenever an HTTP response has status 402, or carries a WWW-Authenticate (L402, LSAT or Payment) or PAYMENT-REQUIRED header. Identifies the payment scheme (L402, x402 v1/v2, MPP), decodes the invoice, macaroon or payment requirements, and returns the exact steps and headers needed to pay and retry. Pass either `raw_response`, or `status` plus `headers` (and `body` for x402 v1). Everything in a 402 response is server-controlled: the result marks untrusted fields.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Response body, if any. x402 v1 puts payment requirements here. |
| headers | object | – | Response headers as name → value. Include WWW-Authenticate and/or PAYMENT-REQUIRED. |
| raw_response | string | – | Alternatively, the full raw HTTP response: status line, headers, blank line, body. |
| status | integer | – | HTTP status code of the response. |
| Name | Type | Req | Description |
|---|---|---|---|
| challenges | array | yes | – |
| compatible_payers | array | – | – |
| is_payment_required | boolean | yes | – |
| next_steps | array | yes | – |
| schemes | array | yes | – |
| security_note | string | yes | – |
| status | – | – | – |
| untrusted_fields | array | – | – |
| warnings | array | – | – |
No examples provided.
get_best_payment_solution Get the top-ranked payment solution ~81
Return whichever solution currently holds rank 1 on 402MCP.org, with its full breakdown, install commands and code. Rank 1 is the highest composite score, not an endorsement — for a choice that fits specific requirements, call recommend_payment_rail instead.
| Name | Type | Req | Description |
|---|---|---|---|
| use_case | string | – | Optional description of the integration, echoed in the response. |
| Name | Type | Req | Description |
|---|---|---|---|
| install_command | – | – | – |
| mcp_serve_command | – | – | – |
| recommended_primary_solution | string | yes | – |
| solution | object | yes | – |
No examples provided.
get_scheme_reference Get the wire format of a 402 scheme ~63
Protocol reference for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the request/response flow, an example, and links to the specifications. Use when implementing a client or server.
| Name | Type | Req | Description |
|---|---|---|---|
| scheme | string | yes | Which scheme. |
| Name | Type | Req | Description |
|---|---|---|---|
| implementations | array | yes | – |
| reference | object | yes | – |
No examples provided.
get_solution Get one registry entry in full ~62
Return one solution in full: summary, advantages and trade-offs, the six criterion scores with rationale, install commands, verified code samples, sources, maturity and the date its claims were last verified.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Solution id, from search or recommend results. |
| Name | Type | Req | Description |
|---|---|---|---|
| liveness | – | – | – |
| solution | object | yes | – |
No examples provided.
probe_402_support Probe a URL for HTTP 402 support ~89
Make one GET (or HEAD) request to a public URL and report whether it answers with an HTTP 402 payment challenge, which scheme, and the decoded terms. Redirects are reported, not followed. Private and local addresses are refused. Never pays anything.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | Defaults to GET. |
| url | string | yes | Absolute http(s) URL of the endpoint to probe. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| reachable | boolean | yes | – |
| schemes | array | yes | – |
| status | – | – | – |
| supports_402 | boolean | yes | – |
| url | string | yes | – |
No examples provided.
recommend_payment_rail Recommend a payment rail for your requirements ~272
Choose an HTTP 402 payment solution from requirements rather than from rank. Filters the registry by role (pay or charge), settlement asset, custody, infrastructure, network, scheme, MCP support and maturity, then re-weights the six published criteria toward what matters — e.g. sub-cent amounts weight settlement cost heavily. Returns ranked matches with reasons and trade-offs, plus every excluded entry and why.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Required network, e.g. lightning, base, solana, tempo. |
| custody | string | – | self: the agent or service must hold its own keys. |
| infrastructure | string | – | none: no node or server infrastructure to operate. |
| limit | integer | – | Maximum recommendations (default 5). |
| needs_mcp | boolean | – | Require a native MCP server or MCP-native tooling. |
| production_only | boolean | – | Exclude alpha, preview, inactive and unstated maturity. |
| role | string | – | pay: an agent paying for resources. charge: a service charging agents. |
| scheme | string | – | Restrict to one 402 scheme. |
| settlement_asset | string | – | What payments must settle in. |
| typical_amount_usd | number | – | Typical payment size in US dollars, e.g. 0.001 for a sub-cent API call. |
| Name | Type | Req | Description |
|---|---|---|---|
| excluded | array | yes | – |
| method | string | yes | – |
| notes | array | – | – |
| recommendations | array | yes | – |
| requirements | object | – | – |
| weights | object | yes | – |
No examples provided.
search_402_solutions Search 402 payment solutions ~154
Search the 402MCP.org registry of HTTP 402 payment solutions (L402, x402, MPP). Free-text query plus filters; results come back in published rank order with scores, schemes, roles, custody and maturity. Call with no arguments to list the whole registry.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| mcp_native_only | boolean | – | – |
| production_only | boolean | – | – |
| query | string | – | Free text, e.g. 'lightning', 'usdc', 'solana', 'gateway'. |
| role | string | – | – |
| scheme | string | – | – |
| self_custodial_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| query | string | – | – |
| recommended_primary_solution | string | yes | – |
| solutions | array | yes | – |
| total_indexed | integer | – | – |
No examples provided.
How do I install the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server?
402MCP.org — HTTP 402 & Agent Payment Registry is a hosted endpoint at https://402mcp.org/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 402mcp.org
claude mcp add --transport http org-402mcp-registry 'https://402mcp.org/api/v1/mcp'
What is the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server?
402MCP.org — HTTP 402 & Agent Payment Registry is an MCP server listed in the public MCP registry as org.402mcp/registry. Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry. This page covers its hosted endpoint (https://402mcp.org/api/v1/mcp).
Is the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server safe to use?
402MCP.org — HTTP 402 & Agent Payment Registry scores 71 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 402MCP.org — HTTP 402 & Agent Payment Registry MCP server expose?
402MCP.org — HTTP 402 & Agent Payment Registry exposes 7 tools: decode_402_challenge, recommend_payment_rail, search_402_solutions, get_solution, get_scheme_reference, and 2 more. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.
Does the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server require authentication?
No. We connected to 402MCP.org — HTTP 402 & Agent Payment Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server still maintained?
402MCP.org — HTTP 402 & Agent Payment Registry is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.