The x402 protocol has been live since early 2026. Coinbase shipped it, Cloudflare integrated it, and the developer conversation has been running hot ever since. But there is a gap between protocol availability and actual adoption. We went through every server in the AgentNDX directory to count how many MCP servers support x402 today.
The short answer: not many.
The Numbers
Out of 724 curated MCP servers in the AgentNDX directory, 5 support x402. That is 0.7% of the index.
Here is how auth breaks down across all listed servers:
| Auth Type | Servers | Share |
|---|---|---|
| API Key | 465 | 64.2% |
| OAuth | 139 | 19.2% |
| None | 108 | 14.9% |
| x402 | 2 | 0.3% |
Five servers have x402 enabled in their protocol support, but only two use x402 as their primary authentication mechanism. The rest pair it with other auth methods. API keys still run the show by a wide margin.
The 5 Servers That Support x402
1. AgentNDX
The AgentNDX directory itself runs an MCP server with x402 payment gating at $0.005 per query. Agents can search, browse, and query the full server registry without an API key. Payment is handled inline via stablecoin settlement on Base.
Category: Data Auth: x402 Price: $0.005 per request
2. AWS Bedrock AgentCore Payments
Amazon’s first managed payment capability built specifically for autonomous agents. Co-developed with Coinbase and Stripe, it lets AI agents running on Bedrock pay for APIs, MCP servers, web content, and other agents using USDC. This is the first major cloud provider to ship native x402 support in a managed agent runtime.
Category: Payments Auth: OAuth + x402
3. Coinbase Payments MCP Server
Coinbase’s own MCP server gives agents access to crypto wallets, fiat onramps, and stablecoin payment capabilities through x402. Works with Claude, ChatGPT, Codex, and Gemini. Users set spend limits and manage permissions through a desktop interface. No API key needed for setup — agents create wallets and execute USDC payments on Base with sub-penny transaction costs.
Category: Payments Auth: x402
4. Coinbase Base MCP Server
Connects AI assistants to the Base Layer 2 network for onchain interactions through natural language. Agents can check wallet balances, view transaction history, initiate transfers, execute swaps on Uniswap and Aerodrome, and interact with lending protocols. Non-custodial design — the server never holds private keys. Every transaction generates a secure approval link for explicit user sign-off.
Category: Payments Auth: OAuth
5. Cryptorefills MCP Server
An agentic commerce server that lets AI agents discover products, build orders, and complete purchases with x402 stablecoin settlement. This is the closest thing to an “agent shopping” MCP server in the directory — the agent handles the full purchase flow from discovery to checkout.
Category: Payments Auth: API Key + x402
Why Adoption Is Still Low
Five out of 724. That is not a rounding error — it is the entire adoption curve so far, six months after x402 launched.
The biggest blocker is wallets. x402 requires the agent (or its user) to have a funded crypto wallet. An API key is one line in a .env file. A wallet requires onboarding to a chain, funding with USDC, and managing spend limits. Most developers building MCP servers do not want to impose that on users.
Then there is the competition from free. Over 14% of servers require no auth at all, and another 64% use API keys that cost nothing to generate. The business case for x402 gating only clicks when you want instant micropayments without managing accounts — and most server builders have not hit that need yet.
The tooling gap compounds both problems. There is no npm install mcp-x402 that handles the payment flow out of the box. Until someone ships drop-in middleware, adoption will track with the number of developers willing to wire up stablecoin settlement by hand. And four of the five x402 servers sit in the payments category — they were already handling money, so adding x402 was a natural extension. The real question is when data or infrastructure servers start treating it as a viable auth model.
What Would Change the Numbers
Three things could move x402 from 0.7% to something real.
Drop-in middleware is the obvious one. A single library that wraps any MCP server in x402 payment gating — similar to how OAuth middleware works in Express — would cut the integration cost from days to minutes. Somebody will build this. The question is when.
The demand side matters more. If Claude, ChatGPT, or Codex shipped with built-in USDC wallets (or easy wallet provisioning), the entire equation flips. Right now x402 is supply-constrained because agents do not have wallets by default.
Price discovery is the sleeper factor. The servers that do support x402 are pricing at fractions of a cent per request. Whether $0.005 per query actually covers compute costs at scale — nobody has published that data yet. If it works, others will follow. If it does not, x402 stays a loss-leader for ecosystem positioning.
The Bottom Line
x402 is real, it works, and it is running in production on five servers today. But calling it widely adopted would be generous. The MCP server world is still overwhelmingly API-key-driven, and the plumbing to make x402 easy for both server builders and agent operators is not there yet.
The servers that do support it — AWS, Coinbase, Cryptorefills — are not small players. Amazon shipping native x402 in a managed agent runtime is worth paying attention to. But 0.7% is 0.7%. The protocol needs middleware and agent wallets before it can become anything more than a bet on the future of agentic commerce.
We will update these numbers as the directory grows. Browse the full AgentNDX server directory to see which servers support x402 and filter by auth type.
FAQ
Q: Can any MCP server add x402 support? A: In theory, yes. x402 is an open protocol. In practice, the server operator needs to integrate stablecoin payment verification into their request handling. There is no standardized middleware for this yet, so it requires custom work.
Q: Does x402 replace API keys? A: It can, but it does not have to. Some servers use x402 alongside other auth methods. The Coinbase Payments server, for example, uses x402 as its primary auth. The Cryptorefills server pairs x402 with an API key. The two models are not mutually exclusive.
Q: How much does a typical x402 request cost? A: The only server with a published per-request price is AgentNDX at $0.005. Most x402 servers have not disclosed their pricing publicly, which makes comparison difficult. Expect sub-cent pricing to be the norm for simple queries, with higher costs for compute-intensive operations.