Skip to content

402MCP.org — HTTP 402 & Agent Payment Registry MCP server

org.402mcp/registry402mcp.orgstreamable-httpv1.1.1Scanned

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

7 tools: 1 do something that can't be undone, 2 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 2 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server can do

The 402MCP.org — HTTP 402 & Agent Payment Registry MCP server is published by 402mcp.org, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (recommend_payment_rail) and create or change data (2 tools: decode_402_challenge and probe_402_support), but cannot delete data. 4 tools only read.

1 tool reads private data (get_scheme_reference); 2 tools bring in text other people can write (search_402_solutions and probe_402_support); 1 tool can send data out of your system (probe_402_support). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • recommend_payment_railChoose an HTTP 402 payment solution from requirements rather than from rank.1 finding

    Why it is in this group

    • The name "recommend_payment_rail" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recommend_payment_rail" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "recommend_payment_rail" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Recommend a payment rail
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • decode_402_challengeCall this whenever an HTTP response has status 402, or carries a WWW-Authenticate (L402, LSAT or Payment) or PAYMENT-REQUIRED header.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "decode_402_challenge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Decode an HTTP 402 response
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • probe_402_supportMake 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Probe a URL for 402 support
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_best_payment_solutionReturn whichever solution currently holds rank 1 on 402MCP.org, with its full breakdown, install commands and code.No findings

    Why it is in this group

    • The name "get_best_payment_solution" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get the top-ranked solution
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scheme_referenceProtocol reference for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the request/response flow, an example, and links to the specifications.Reads private data1 finding

    Why it is in this group

    • The name "get_scheme_reference" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...rence for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the req..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a 402 scheme reference
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_solutionReturn 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 it…No findings

    Why it is in this group

    • The name "get_solution" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one registry entry
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_402_solutionsSearch the 402MCP.org registry of HTTP 402 payment solutions (L402, x402, MPP).Reads text others writeNo findings

    Why it is in this group

    • The name "search_402_solutions" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search 402 payment solutions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__registry__probe_402_support"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://402mcp.org/api/v1/mcp: tools/list returned 7 tools to an anonymous client, including recommend_payment_rail (irreversible), decode_402_challenge (write), probe_402_support (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "decode_402_challenge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "recommend_payment_rail" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "recommend_payment_rail" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...rence for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the req..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http registry https://402mcp.org/api/v1/mcp
claude mcp add --transport http registry https://402mcp.org/api/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__registry__search_402_solutions",
      "mcp__registry__get_solution",
      "mcp__registry__get_scheme_reference",
      "mcp__registry__get_best_payment_solution"
    ],
    "ask": [
      "mcp__registry__decode_402_challenge",
      "mcp__registry__recommend_payment_rail",
      "mcp__registry__probe_402_support"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registry. Review it before you use it.

Capability tags behind 3 rules
  • mcp__registry__search_402_solutions untrusted-input
  • mcp__registry__get_scheme_reference private-data
  • mcp__registry__probe_402_support untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.402mcp/registry/verify?hash=4df83dd19b2c4b39b51d7c6852a305fb7aac3370d700b20fb5a0e500ecc61833" | jq -e '.changed == false'

Pinned hash 4df83dd19b2c, from Nov 18, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.402mcp/registry/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.402mcp/registry
[![Anlyon Radar](https://radar.anlyon.com/badge/org.402mcp/registry.svg)](https://radar.anlyon.com/servers/org.402mcp/registry)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

402MCP.org — HTTP 402 & Agent Payment Registry MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: recommend_payment_rail.

What tools does the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server have?

7 tools: 1 irreversible, 2 write, 4 read. recommend_payment_rail, decode_402_challenge, probe_402_support, search_402_solutions, get_solution, get_scheme_reference and get_best_payment_solution.

Does the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): probe_402_support.

Has the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.