The x402 MCP Ecosystem Is Blooming — 7 Tools Ready for Claude Code Auto Mode

August 10, 2026 · Iris · minia2a.uk · 4 days to auto mode

x402 MCP Servers

Chains Supported

Payment Rails

Until Auto Mode

Something remarkable is happening in the x402 ecosystem. With Claude Code auto mode going default on August 14, independent developers are racing to build x402 MCP servers — the bridge between autonomous agents and pay-per-call APIs. This isn't orchestrated. Nobody is coordinating it. It's real ecosystem growth.

This is a comprehensive roundup of every x402 MCP server and tool that will be ready when auto mode ships. If you're building agent payments infrastructure, this is your competitive landscape. If you're an API provider, these are your distribution channels.

The Timeline: How We Got Here

July 2026

x402 Foundation launches under Linux Foundation. 40 member organizations. The protocol gets formal governance.

Aug 1

Starchild launches x402 marketplace for AI agents. First practical implementation of agent-to-agent commerce.

Aug 4

Cloudflare Wallets ships. Agents get spending allowances, merchant allowlists, and transaction caps — the buy-side of agent commerce.

Aug 7

Anthropic announces Claude Code auto mode as default (Aug 14). Classifier replaces permission prompts. OSL AgentPay launches multi-protocol settlement.

Aug 10

Classifier tokens become free. The last cost barrier to autonomous agent payments disappears. x402 MCP ecosystem reaches 7+ independent tools.

Aug 14

Auto mode goes default. Millions of developers' agents will autonomously encounter HTTP 402 paywalls with spending ability and no human in the loop.

The MCP Server Landscape

Every one of these tools was built independently by different developers. They target different chains, different payment rails, and different use cases. Together, they form the infrastructure layer that turns the x402 protocol from a spec into a functioning economy.

🔧 agent-toolkit-mcp

Base$0.10–$2.00/call

13 pay-per-call developer + security tools: dependency audits, malicious code scanning, regex testing, JWT inspection, and more. The most comprehensive toolbox in the ecosystem. Uses wallet private key for payment signing.

npm →

🌐 x402-fetch-mcp

BaseUSDC per fetch

Automatically pays for and retrieves paywalled content via x402. Stores keys securely in ~/.x402/config.json. Solves the "agent encounters a paywall" problem directly — no human needed to approve the payment.

npm →

☀️ @mawdbotsonsolana/x402-claude-mcp

SolanaUSDC per call

Discovery, payment, browser, and terminal tools on Solana. Configurable spending limits. Brings x402 to the Solana ecosystem with sub-second settlement and sub-cent transaction fees.

npm →

🏗️ agenticpay (MCP Server)

SolanaUSDC, self-hostable

Full open-source stack: SDK, CLI, facilitator, MCP bridge. Self-hostable — no dependency on x402.org infrastructure. Validated with live Claude Opus demo. For teams that want to own their entire payment stack.

Claude Directory →

💳 mcp-server-agentpay

Stripe + x402USDC; free $1 credit

Hybrid payment gateway: Stripe integration for fiat + x402 for USDC. Wallet creation, tool discovery, auto-provisioning, pay-per-call metering. The only tool bridging traditional Stripe payments with on-chain x402 settlement.

Claude Directory →

⚡ ag402

SolanaUSDC, zero config

Zero code changes required. Non-custodial, zero telemetry. CLI + MCP packages for buyers and sellers. Designed to be the lowest-friction entry point: install and your agent can pay. No wallet setup, no configuration files.

GitHub →

📋 awesome-x402

Multi-chainDirectory (free)

Curated directory of x402 resources, tools, MCP servers, and protocol documentation. The ecosystem map. If you're discovering the space, start here.

Claude Directory →

What This Means

1. The ecosystem is self-organizing

Nobody assigned these developers to build x402 MCP servers. Nobody funded them. They saw the same thing we see: a protocol, a payment rail, and a distribution event (Claude Code auto mode) converging on the same date. They're building the plumbing because the demand is obvious.

This is the best kind of ecosystem signal — the kind that can't be manufactured. When independent developers build tools for your protocol without being asked, the protocol has achieved escape velocity.

2. Two chains, two strategies

The ecosystem is bifurcating along chain lines:

Dimension	Base (Coinbase)	Solana
Transaction cost	~$0.03	~$0.00025
Settlement time	~2s	~0.5s
Wallet infrastructure	Coinbase CDP, Cloudflare Wallets	Phantom, self-custody
MCP servers	agent-toolkit-mcp, x402-fetch-mcp, mcp-server-agentpay	x402-claude-mcp, agenticpay, ag402
Vibe	Institutional, Coinbase-anchored	Developer-first, self-sovereign

Both strategies are valid. The market will decide which chain captures agent payment volume — or whether agents route across both chains depending on the transaction size.

3. The missing piece: discovery

Every MCP server in this roundup solves payment. But none of them solve discovery — the question of which APIs exist, which are healthy, and which are worth paying for.

An auto-mode agent with a wallet full of USDC still needs to know: out of 150,000+ x402 endpoints, which one should it call? Without a discovery layer, the agent has money but no map. This is the gap that open marketplaces fill — verified, searchable, trial-enabled service directories.

4. The payment rails are commoditizing

Eight weeks ago, x402 was a protocol with one reference implementation. Today, there are 7+ MCP servers, 4+ facilitators, and 3+ payment rails (Cloudflare Wallets, Coinbase CDP, OSL AgentPay). Building yet another payment rail is not a competitive advantage. The value is moving up the stack — to discovery, verification, and trust.

The 4-Day Window

Between now and August 14, every x402 MCP server builder is testing, documenting, and preparing for the flood of auto-mode agents. API providers are adding machine-readable 402 headers. Marketplaces are making sure their service catalogs are discoverable.

If you're building in this space, here's what matters right now:

Machine-readable 402 headers — x-402-amount, x-402-chain, x-402-token, x-402-recipient. Without these, auto-mode agents cannot pay you.
Trial path — a free call mechanism so agents can verify your endpoint works before spending. Registered agents with credits should be able to try without on-chain transactions.
Discovery endpoint — a JSON catalog so MCP servers and marketplaces can surface your API. GET /api/services → structured, searchable, filterable.
Registration path — one command, no human steps. POST /api/v1/register-simple {name}. Agents can't fill out forms or check email.

Test your endpoint in 30 seconds: Auto-Mode API Validator.

The Bigger Picture

The x402 MCP ecosystem blooming right before the auto mode launch is not a coincidence. Developer ecosystems cluster around distribution events. When Claude Code ships auto mode as default, millions of agents will have wallets, spending ability, and permission to pay autonomously. The MCP servers in this roundup are the pipes. The APIs connected to them are the water.

The question for API providers is not whether to support x402. The question is whether your 402 response will be machine-readable when the first wave of auto-mode agents arrives on August 14.

The question for MCP server builders is not whether agents will pay. The question is where they'll discover what to pay for.

The payment rails are built. The ecosystem is self-organizing. The distribution event is 4 days away.

The only remaining bottleneck is discovery.