Anthropic introduced the Model Context Protocol in November 2024 as an open standard for connecting AI assistants to external tools, systems and data sources. The protocol lets developers expose capabilities through MCP servers, while AI applications act as MCP clients that connect to those servers.
The discovery layer is now more formalized through the official, community-driven MCP Registry, which Anthropic later described as a directory for finding available MCP servers. The registry itself is maintained in the open, and its GitHub documentation says it provides MCP clients with a list of MCP servers, similar to an app store for server integrations.
USDC Payments Are an Integration Pattern, Not a Native Anthropic Feature
The payments side should be framed carefully. The strongest available evidence points to third-party x402 integrations that make paid MCP tool calls possible, not to a single Anthropic announcement bundling the MCP Registry with native USDC payments. Coinbase’s x402 documentation says the protocol enables instant, automatic stablecoin payments over HTTP for humans and AI agents.
The x402 MCP guide explains how an MCP server can bridge a compatible client, including Claude Desktop, to a paid API. When a tool call reaches a paid endpoint, the server detects the payment requirement, handles payment through a wallet and returns the paid result to the client.
That flow can involve USDC. The x402 MCP documentation lists prerequisites including an Ethereum wallet with USDC on Base Sepolia or Base Mainnet, or a Solana wallet with USDC on Devnet or Mainnet. Civic’s X402 MCP documentation separately describes pay-per-use MCP tools with automatic USDC payments on Base during tool invocation.
Discovery and Payment Are Adjacent, but Not the Same Layer
Operationally, the pattern is clear: MCP Registry can help users and clients discover servers, while x402-style tooling can add payment requirements to specific tool calls. That creates a path for paid AI-agent workflows, but the registry itself should not be described as enforcing USDC payments or billing rules unless an individual server or registry entry documents that behavior.
Base’s own MCP payment guide shows a related user-controlled flow, where an assistant prepares an x402 request, checks the payment challenge and asks the user to approve a USDC payment before completing the request. That reinforces the idea that paid MCP access can exist through external payment rails, with approval caps and chain-specific limits.
The clean editorial framing is therefore narrow: MCP server discovery and on-chain paid tool access are converging through the broader MCP and x402 ecosystems, but there is no single primary-source confirmation that Anthropic has launched native USDC payments inside the official MCP Registry. Broader claims about pay-per-call MCP markets, registry-wide monetization or standardized billing should remain tied to the specific third-party implementation that supports them.