Mcp X402

io.github.codesparPublished by GitHub account codesparv0.1.5Updated Oct 27, 2026

DEPRECATED: no live endpoint (api.x402.org does not resolve)

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Deprecated local MCP server for the x402 HTTP micropayment protocol; its only endpoint no longer resolves, so its tools reach no service.

What you can do
  • Pay for 402-protected resources and verify on-chain settlement of x402 payments
  • Create, read, list and delete x402 paywall configurations for endpoints
  • Check USDC balance and browse or inspect payment history
  • List supported networks, tokens and facilitators
  • Note: the README states the package is deprecated and no tool reaches a service.
When to use it
Only as a reference or starting point if you already have a working x402 facilitator endpoint to point it at; not suitable for live agent payments as published.
Requirements
Runs locally via npx from the npm package @codespar/mcp-x402, typically configured in Claude Desktop, Claude Code, Cursor or VS Code. Needs a facilitator API key in X402_API_KEY and a wallet address in X402_WALLET_ADDRESS, plus optional X402_NETWORK (base or solana).
Before you install
The package is deprecated and its only host does not resolve in DNS, so the tools cannot reach a service. The tools are designed to send USDC payments on-chain and to create or delete paywalls, so any working configuration would spend real funds and change endpoint settings. It requires a facilitator API key and a wallet address as environment variables.

Installation

In SourceWeft

  1. Open Mcp X402 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-x402

Deprecated: no live endpoint. Measured on 2026-09-27 against two public DNS resolvers (8.8.8.8 and 1.1.1.1): api.x402.org, the only host this server calls, does not resolve in DNS. x402 has no central API: it is an HTTP 402 protocol, and each seller picks the facilitator that verifies payment. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it with X402_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.

MCP server for x402 — HTTP-native micropayments protocol by Coinbase (USDC on Base/Solana)

[npm] [License: MIT]

What is x402?

x402 is an open protocol that enables machine-to-machine micropayments at the HTTP layer. When an AI agent requests a resource and receives HTTP 402 Payment Required, it automatically sends a USDC payment on-chain and retries — no checkout UI, no merchant integration, pure HTTP.

This is the payment rail purpose-built for agentic commerce.

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json
{  "mcpServers": {    "x402": {      "command": "npx",      "args": ["-y", "@codespar/mcp-x402"],      "env": {        "X402_API_KEY": "your-key",        "X402_WALLET_ADDRESS": "your-wallet-address"      }    }  }}

Claude Code

bash
claude mcp add x402 -- npx @codespar/mcp-x402

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

json
{  "servers": {    "x402": {      "command": "npx",      "args": ["-y", "@codespar/mcp-x402"],      "env": {        "X402_API_KEY": "your-key",        "X402_WALLET_ADDRESS": "your-wallet-address"      }    }  }}

Tools (10)

ToolPurpose
pay_requestPay for a 402-protected resource.
verify_paymentVerify if a x402 payment was received and settled on-chain
create_paywallCreate a x402 paywall configuration for an endpoint.
get_paywallGet paywall configuration for a specific URL
list_paywallsList all configured x402 paywalls
delete_paywallRemove a x402 paywall from an endpoint
get_balanceGet available USDC balance for x402 payments
list_paymentsList x402 payment history with optional filters
get_paymentGet details of a specific x402 payment
get_supported_networksList supported blockchain networks, tokens, and facilitators for x402 payments

Authentication

x402 uses a Bearer API key from a registered facilitator.

Get your credentials

  1. Visit the x402 documentation
  2. Set up a facilitator or use Coinbase's hosted facilitator
  3. Generate an API key
  4. Get your wallet address (Base or Solana)
  5. Set the environment variables

Environment Variables

VariableRequiredDescription
X402_API_KEYYesAPI key for x402 facilitator
X402_WALLET_ADDRESSYesWallet address for sending/receiving payments
X402_NETWORKNoBlockchain network: base (default) or solana

Use Cases

  • Agent accessing premium APIs — AI agent pays per-request for data feeds, LLM APIs, or premium content
  • Micropayment monetization — Protect your API endpoints with sub-cent paywalls
  • Machine-to-machine commerce — Agents autonomously purchasing compute, data, or services

Roadmap

v0.2 (planned)

  • create_subscription — Set up recurring micropayments for an endpoint
  • estimate_cost — Estimate cost before paying for a resource
  • batch_pay — Pay for multiple resources in a single transaction

v0.3 (planned)

  • Multi-token support (ETH, SOL beyond USDC)
  • Streaming payments for long-running agent tasks

Want to contribute? Open a PR or request a tool.

Links

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/crypto/x402/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.5LatestSep 27, 2026
  2. v0.1.4Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts