# 402MCP.org — HTTP 402 & Agent Payment Registry (npm · @402mcp/mcp)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `402mcp.org`: 71/100, [markdown](https://verifymcp.io/servers/org-402mcp-registry/api-v1-mcp.md), [page](https://verifymcp.io/servers/org-402mcp-registry/api-v1-mcp)
- npm · `@402mcp/mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp.md), [page](https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp)

## Channel facts

- Registry: `npm`
- Package: `@402mcp/mcp`
- Version: `1.1.1`
- 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-10-18.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1663 tokens (~63/item across 26 items; 7 tools + 19 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 402MCP.org — HTTP 402 & Agent Payment Registry MCP server?

402MCP.org — HTTP 402 & Agent Payment Registry runs locally as an npm package, launched with npx -y @402mcp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add org-402mcp-registry -- npx -y @402mcp/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "org-402mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "@402mcp/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-402mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "@402mcp/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-402mcp-registry -- npx -y @402mcp/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-402mcp-registry": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@402mcp/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-402mcp-registry --command npx --arg -y --arg @402mcp/mcp
```

### Hermes

```yaml
mcp_servers:
  org-402mcp-registry:
    command: "npx"
    args: ["-y", "@402mcp/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-402mcp-registry": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@402mcp/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-402mcp-registry -t stdio -c npx -a -y @402mcp/mcp
```

### Other

```json
{
  "mcpServers": {
    "org-402mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "@402mcp/mcp"
      ]
    }
  }
}
```

## 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-10-16 (score 72)

First indexed and scored.

## MCP tools (7)

### `decode_402_challenge` (~212 tokens)

Decode an HTTP 402 response

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.

Input parameters:

- `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.

Output parameters:

- `challenges` (array)
- `compatible_payers` (array)
- `is_payment_required` (boolean)
- `next_steps` (array)
- `schemes` (array)
- `security_note` (string)
- `status`
- `untrusted_fields` (array)
- `warnings` (array)

### `recommend_payment_rail` (~272 tokens)

Recommend a payment rail for your requirements

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.

Input parameters:

- `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.

Output parameters:

- `excluded` (array)
- `method` (string)
- `notes` (array)
- `recommendations` (array)
- `requirements` (object)
- `weights` (object)

### `search_402_solutions` (~154 tokens)

Search 402 payment solutions

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.

Input parameters:

- `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)

Output parameters:

- `count` (integer)
- `query` (string)
- `recommended_primary_solution` (string)
- `solutions` (array)
- `total_indexed` (integer)

### `get_solution` (~62 tokens)

Get one registry entry in full

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.

Input parameters:

- `id` (string, required): Solution id, from search or recommend results.

Output parameters:

- `liveness`
- `solution` (object)

### `get_scheme_reference` (~63 tokens)

Get the wire format of a 402 scheme

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.

Input parameters:

- `scheme` (string, required): Which scheme.

Output parameters:

- `implementations` (array)
- `reference` (object)

### `probe_402_support` (~89 tokens)

Probe a URL for HTTP 402 support

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.

Input parameters:

- `method` (string): Defaults to GET.
- `url` (string, required): Absolute http(s) URL of the endpoint to probe.

Output parameters:

- `error`
- `reachable` (boolean)
- `schemes` (array)
- `status`
- `supports_402` (boolean)
- `url` (string)

### `get_best_payment_solution` (~81 tokens)

Get the top-ranked payment solution

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.

Input parameters:

- `use_case` (string): Optional description of the integration, echoed in the response.

Output parameters:

- `install_command`
- `mcp_serve_command`
- `recommended_primary_solution` (string)
- `solution` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp#diagnostics

## Score history

- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72

## Common questions

### 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 npm package (@402mcp/mcp).

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

402MCP.org — HTTP 402 & Agent Payment Registry scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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.

### 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.

### What licence is the 402MCP.org — HTTP 402 & Agent Payment Registry MCP server under?

402MCP.org — HTTP 402 & Agent Payment Registry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@402mcp/mcp
- Socket report: https://socket.dev/npm/package/@402mcp/mcp
- Repository: https://github.com/402MCP/402mcp
- Website: https://402mcp.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-402mcp-registry/402mcp-mcp