Official links
Relationships
| From | Type | To | Evidence |
|---|---|---|---|
| evt-mastercard-agentic-payments | DISCUSSES | mpp | Verified |
| evt-mcp-paid-tools-gap | DISCUSSES | mpp | Verified |
| evt-openai-apps-agents-commerce | DISCUSSES | mpp | Verified |
| evt-stablecoin-agent-wallets-pattern | DISCUSSES | mpp | Observed |
| evt-stripe-mpp-blog | DISCUSSES | mpp | Verified |
| evt-tempo-mainnet-mpp-2026-03-18 | DISCUSSES | mpp | Verified |
| mpp | IMPLEMENTS | http | Verified |
| stripe | BUILDS | mpp | Verified |
| tempo | SUPPORTS | mpp | Verified |
Recent events
Paid MCP is still an overlay, not a core MCP feature
MCP specifies how tools are described and invoked. It does not specify settlement. Cloudflare’s gateway, x402 challenge-handoff and MPP all propose to hang payment on the same tool call. Until the MCP spec itself names a payment profile, “paid MCP” remains a market category, not a single standard.
VerifiedSourceMastercard is named as a Tempo/MPP design partner for agent payments
Tempo’s mainnet note lists Mastercard among partners working on mainnet payment use cases, and says MPP is extensible to card networks. This is partnership language, not a settlement-volume disclosure. zFinia files it as TIER_B/A official corporate communication depending on the primary source.
VerifiedSourceAgent commerce protocols proliferate beyond crypto-native stacks
Through 2025–2026, incumbent payments and model vendors published overlapping agent-commerce interfaces. Stripe describes an Agentic Commerce Protocol alongside MPP and x402 support. Visa shipped Intelligent Commerce. The overlapping vocabulary is a classification problem for buyers and a coverage obligation for zFinia.
VerifiedSourceAgent wallets converge on stablecoins plus policy limits
Across Visa Intelligent Commerce, x402 and MPP, the shared design is: the human sets a budget and allowed counterparties; the agent spends inside that envelope; settlement is a stable unit or a card token. The protocols disagree on rail, not on the control problem.
ObservedSourceStripe documents MPP as an internet-native way for agents to pay
Stripe published MPP as an open standard co-authored with Tempo. Agents request an API, MCP server or HTTP resource; the service returns a payment request; the agent authorizes; Stripe businesses see the payment like any other PaymentIntent. Stripe also states payment support for both MPP and x402 inside a broader agentic commerce stack.
VerifiedSourceTempo mainnet ships with Stripe-coauthored Machine Payments Protocol
On 18 March 2026 Tempo announced public mainnet RPC and introduced MPP, co-authored with Stripe. MPP lets an agent request a resource, receive a 402 challenge, authorize payment, and receive the resource. Tempo says Visa, Stripe and Lightspark have extended MPP across cards, platform methods and Lightning. Stripe’s own blog presents MPP as an open standard for agent payments, including settlement into existing Stripe balances.
VerifiedSource
Source
verified · https://zfinia.com/methodology