Name: 402MCP.org — HTTP 402 & Agent Payment Registry
Author: 402mcp

402MCP.org — HTTP 402 & Agent Payment Registry

Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry.

Grade A Remote or local · Streamable HTTP · stdio No auth needed 7 tools v1.1.1 · 16 Oct 2026

No reviews yet by 402mcpnpm Runs on your machine or at its publisher’s address — not through us

96/100

trust score

tools declared

local

or remote

—

downloads a day

What it does

Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user 402mcp-org-http-402-agent-payment-registry '--' npx -y @402mcp/mcp

# 2 — ask your agent for something these tools do
#   decode_402_challenge, recommend_payment_rail, search_402_solutions and 4 more

402MCP.org — HTTP 402 & Agent Payment Registry costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

402mcp1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user 402mcp-org-http-402-agent-payment-registry '--' npx -y @402mcp/mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Or connect to its publisher’s address

Its publisher also runs it at https://402mcp.org/api/v1/mcp: nothing to start on your machine, and this marketplace is not in the path.

claude mcp add --scope user --transport http 402mcp-org-http-402-agent-payment-registry https://402mcp.org/api/v1/mcp

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take MCP_402_OFFLINE (Set to 1 to use the bundled registry snapshot and never fetch.) if you want to set it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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

Parameter	Type	Required	Notes
status	integer	no	HTTP status code of the response.
headers	object	no	Response headers as name → value. Include WWW-Authenticate and/or PAYMENT-REQUIRED.
body	string	no	Response body, if any. x402 v1 puts payment requirements here.
raw_response	string	no	Alternatively, the full raw HTTP response: status line, headers, blank line, body.

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

Parameter	Type	Required	Notes
role	string	no	pay: an agent paying for resources. charge: a service charging agents.
typical_amount_usd	number	no	Typical payment size in US dollars, e.g. 0.001 for a sub-cent API call.
settlement_asset	string	no	What payments must settle in.
custody	string	no	self: the agent or service must hold its own keys.
infrastructure	string	no	none: no node or server infrastructure to operate.
chain	string	no	Required network, e.g. lightning, base, solana, tempo.
scheme	string	no	Restrict to one 402 scheme.
needs_mcp	boolean	no	Require a native MCP server or MCP-native tooling.
production_only	boolean	no	Exclude alpha, preview, inactive and unstated maturity.
limit	integer	no	Maximum recommendations (default 5).

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.

Parameter	Type	Required	Notes
query	string	no	Free text, e.g. 'lightning', 'usdc', 'solana', 'gateway'.
scheme	string	no	—
role	string	no	—
kind	string	no	—
mcp_native_only	boolean	no	—
self_custodial_only	boolean	no	—
production_only	boolean	no	—
limit	integer	no	—

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.

Parameter	Type	Required	Notes
id	string	yes	Solution id, from search or recommend results.

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.

Parameter	Type	Required	Notes
scheme	string	yes	Which scheme.

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.

Parameter	Type	Required	Notes
url	string	yes	Absolute http(s) URL of the endpoint to probe.
method	string	no	Defaults to GET.

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.

Parameter	Type	Required	Notes
use_case	string	no	Optional description of the integration, echoed in the response.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install 402MCP.org — HTTP 402 & Agent Payment Registry or to call it, at any volume.

ATrust score 96 / 100

Release 1.1.1 · scanned 16 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings0 threat · 1 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digestd2076e7f8d5a5259ab56694f85f1ff3e380b070c1d138ea4d8bb733188e92dfd

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
decode_402_challenge	no tags
recommend_payment_rail	no tags
search_402_solutions	no tags
get_solution	no tags
get_scheme_reference	no tags
probe_402_support	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
get_best_payment_solution	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digestd2076e7f8d5a5259

Scanned2026-10-16

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.