INDIVIDUAL MCP TOOL

get_scheme_reference

Protocol reference for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the request/response flow, an example, and links to the specifications.

402mcp.orgnone authenticationAvailability not checked

LIVE ENDPOINT

https://402mcp.org/api/v1/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_scheme_reference and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name, description or schema mentions credentials.

Parent server

402mcp.org

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.402mcp-org]
url = "https://402mcp.org/api/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "402mcp-org": {
      "type": "http",
      "url": "https://402mcp.org/api/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: 402mcp-org
Remote MCP URL: https://402mcp.org/api/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "402mcp-org": {
      "url": "https://402mcp.org/api/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "402mcp-org": {
      "type": "http",
      "url": "https://402mcp.org/api/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "402mcp-org",
  "transport": "streamable-http",
  "url": "https://402mcp.org/api/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

decode_402_challenge — Call this whenever an HTTP response has status 402, or carries a WWW-Authenticate (L402, LSAT or Payment) or PAYMENT-REQUIRED header.
recommend_payment_rail — Choose an HTTP 402 payment solution from requirements rather than from rank.
search_402_solutions — Search the 402MCP.
get_solution — 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.
probe_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.
get_best_payment_solution — Return whichever solution currently holds rank 1 on 402MCP.