Base MCP shipped may 26 — what the OAuth 2.1 + on-chain approval model means for server operators
Coinbase shipped Base MCP on may 26, 2026. Claude and ChatGPT can now connect to Base Accounts via OAuth 2.1 to propose on-chain DeFi transactions for user approval. separately, a Payments MCP enables autonomous agent payments across Base, Polygon, and Solana.
two distinct things shipped here and they're worth separating.
the first is user-approval-gated transaction signing — agents propose, humans approve. that's the conservative path: agent autonomy is real but every transaction clears a human gate before it settles. it works for DeFi use cases where the user is present and involved.
the second is the Payments MCP — autonomous agent payments. no human gate. the agent spends within parameters and settles. that's the path where payment infrastructure complexity actually lives.
what the Payments MCP means for MCP server operators
if your MCP server accepts payment, you're now potentially receiving payment requests from agents running on Base, Polygon, or Solana. those are three different settlement chains with different finality guarantees, different gas mechanics, and different confirmation times.
an agent paying over Base settles in USDC with ~2 second finality on the L2. an agent paying over Polygon settles on a different validator set with different confirmation guarantees. an agent paying over Solana has fast finality but different token standards.
your server's receipt logic has to handle all three — not just "did we get paid" but "is this payment final, which chain settled it, and is the on-chain record tamper-evident enough to use as an audit trail."
the Base MCP / x402 relationship
Base MCP and x402 aren't the same protocol. x402 is Coinbase's HTTP 402 extension for micropayments — a request-response payment protocol for API calls. Base MCP is a broader agent connectivity layer that uses OAuth 2.1 for identity and transaction signing.
an agent using x402 to pay your API is a different technical path than an agent using Base MCP to propose a DeFi transaction. but both paths can settle on Base, and both are shipping now.
this is the multi-surface payment problem: as a server operator you're not choosing between x402 or Base MCP. you're getting agents that arrive over x402, over Base MCP's Payments MCP, over AP2 (Google), over MPP (Stripe). you need to handle whichever shows up.
what multi-chain + multi-protocol actually requires
the combination of multi-chain settlement (Base, Polygon, Solana) and multi-protocol auth (x402, OAuth 2.1, AP2, MPP) means the surface area for payment infrastructure on any serious MCP server is now meaningfully large.
the operators who built their payment layer in q1 2026 around a single protocol and a single chain are going to need to extend it as the traffic diversifies. the question is whether they extend it themselves (new auth stack per protocol, new receipt logic per chain) or use a normalization layer that handles the detection, translation, and routing.
MnemoPay handles multi-protocol inbound detection, auth validation, settlement routing, and tamper-evident per-call receipts. 672 tests, v1.0.0-beta.1, 1.4K weekly npm downloads.
Top comments (0)