What it does
The server decodes HTTP 402 payment challenges, including the L402, x402 and MPP formats, so an agent can read what a service is asking for before paying. It also helps select the agent payment rail to use, drawing on an open registry of options.
It would be reached for when an agent meets a 402 Payment Required response and needs to interpret the challenge, or when it must pick between several payment methods for machine-to-machine transactions.
The source gives no detail on setup or runtime requirements beyond its description as an MCP server.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
402MCP.org — HTTP 402 & Agent Payment Registry
Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry.
v1.1.1As shown on registry.modelcontextprotocol.io when we last read it