MCP, the Linux Foundation, and What Neutral Governance Means for Payments

Last updated: 2026-06-10

In December 2025, Anthropic donated the Model Context Protocol (MCP) to the Agentic AI Foundation, a Linux Foundation project, with Anthropic, Block, and OpenAI as co-founding members. That governance move matters more for payments than most people realize: neutral stewardship is the precondition for serious financial infrastructure to trust a protocol. Without it, banks, card networks, and enterprise procurement teams won't build on something one company controls.

Key takeaways

What is the Agentic AI Foundation?

The Agentic AI Foundation is a Linux Foundation project created to provide neutral, open governance for protocols that underpin AI agent infrastructure. Its model is the same one governing Linux, Kubernetes, and the OpenAPI Specification: a foundation-run structure where no single company can unilaterally change the protocol, fork it for competitive advantage, or restrict who implements it.

MCP was the first major protocol donated to the foundation. The donation happened in December 2025, roughly 13 months after Anthropic first published the spec.

Why the Linux Foundation specifically? It has a track record financial institutions recognize. Banks and payment networks run legal and procurement processes built around evaluating open standards with independent governance. Proprietary protocols from a single AI vendor don't pass that filter, regardless of technical quality. The Linux Foundation structure gives MCP a clear IP ownership policy (the spec and official SDKs are MIT-licensed), a public process for proposing changes, and a governance board any contributing organization can join.

Who co-founded the foundation and why does the mix matter?

Three organizations are announced co-founders: Anthropic, Block, and OpenAI.

Anthropic is MCP's creator. Its continued involvement means the original authors are steering, not just handing off. Without that continuity, the spec risks drifting from production implementations.

Block (parent of Square, Cash App, and Spiral) brings payment infrastructure credibility. Block processes billions in payments annually, holds money transmitter licenses across the US, and is a regulated payments provider in the UK, Australia, and other markets. A company with serious payments DNA co-founding the governance structure signals that MCP is being designed with payment use cases in mind from the start.

OpenAI brings the other dominant frontier model developer. OpenAI also has a direct commercial relationship with Stripe through its Agentic Commerce Protocol (ACP) work. Having OpenAI at the table makes MCP-compatible integrations across both Claude and GPT-based agents more likely, not less.

Google isn't a co-founder, which stands out given its own protocols (A2A, AP2, UCP). But it's in the room: Google was announced as a supporting member at the foundation's December 2025 formation, alongside Microsoft, AWS, Cloudflare, and Bloomberg. That's a meaningful distinction. Co-founders shape the governance structure; supporting members work within it.

the co-founder mix includes both companies building AI models and a company that actually moves money. That combination makes MCP credible as payment-adjacent infrastructure, not just developer tooling.

What does neutral stewardship change for payment builders?

Before the donation, MCP was governed by Anthropic's internal decision-making. Fine for developers building experiments. A real obstacle for organizations with enterprise procurement requirements, bank-grade security reviews, or financial regulatory obligations.

Three things change with neutral governance.

Procurement approval. Enterprise software procurement, especially at banks, insurers, and regulated fintechs, requires that critical protocols not be controlled by a single vendor. An Anthropic-controlled MCP creates a vendor dependency that procurement processes flag. A Linux Foundation-governed MCP doesn't. The same dynamic drove OpenAPI adoption over bespoke API documentation and FIDO2 over proprietary authentication schemes.

Regulatory conversation. Regulators in the EU (under DORA and the incoming PSD3/PSR), the UK (FCA operational resilience rules), and the US (OCC third-party risk guidance) have questions about concentration risk from single-vendor infrastructure dependencies. Neutral governance gives compliance teams a framework to work within. A Linux Foundation project with transparent governance is a different risk profile than a proprietary protocol.

Implementation breadth. When one company controls a protocol, others build against it cautiously. Neutral governance removes that hesitation. More implementations mean more merchant tooling, more payment processor integrations, and more compatibility across the agent stack. That matters specifically for payments because an agent needs to transact across many merchants.

For a deeper look at what MCP does and doesn't handle at the protocol level, see Introducing the Shatale MCP Server.

What does governance not solve?

Governance solves the trust and adoption problem. It doesn't solve MCP's technical gaps for payment use cases.

MCP carries tool invocations. It doesn't carry spend policy, delegation rules, per-agent authorization controls, or audit trails. Donating MCP to the Linux Foundation doesn't ship those capabilities. It makes MCP a more credible substrate for building the infrastructure that adds them.

The control plane (per-agent virtual cards, real-time policy at the authorization moment, approval workflows, immutable logs) remains outside the MCP specification. The governance move makes it more likely that standards eventually emerge here, but it doesn't accelerate that timeline. Builders deploying agents that spend money need to solve the control plane now.

The governance donation is the infrastructure story getting cleaner. The control gap is the production story staying urgent.

What should builders do with this?

Two things.

Treat MCP as a stable substrate. The Linux Foundation governance structure makes MCP a reasonable long-term bet for the tool-invocation layer of your agent stack. You're not betting on Anthropic's competitive position, you're betting on a governed open standard.

Don't conflate "MCP is now well-governed" with "the payments problem is solved." The protocol layer is cleaner. The control plane is still missing from most deployments. Agents that invoke payment tools via MCP still need a layer that enforces policy, issues scoped credentials, routes approvals, and creates audit trails before any of that spending counts as controlled.

Frequently asked questions

When did Anthropic donate MCP to the Linux Foundation? Anthropic donated MCP to the Agentic AI Foundation, a Linux Foundation project, in December 2025, about 13 months after Anthropic originally published the protocol specification. The donation made MCP a vendor-neutral open standard with independent governance.

Who are the co-founders of the Agentic AI Foundation? The announced co-founders are Anthropic, Block, and OpenAI. Anthropic created MCP and continues in stewardship. Block brings payment infrastructure credibility across Square, Cash App, and Spiral. OpenAI brings the other dominant frontier model developer to the governance table.

Why does neutral MCP governance matter for payments? Financial institutions, enterprises, and payment processors won't build critical payment infrastructure on a protocol controlled by a single private company. Neutral governance under the Linux Foundation gives those organizations the vendor-independence, IP clarity, and change-management process they require before approving a protocol for production payment use.

Does the Linux Foundation governance change what MCP does? No. MCP remains a data-plane protocol: it handles tool discovery and invocation, not money movement. The governance change affects who controls the spec and how changes are made, not the protocol's technical scope. Payment controls, per-agent cards, and spend policy still require a separate control-plane layer.

Will MCP eventually include payment control features? Possibly, but unlikely as core spec. The Linux Foundation's approach is to keep protocols narrowly scoped and composable. Payment control standards are more likely to emerge as a separate layer or companion specification. As of mid-2026, no such proposal is publicly on the roadmap.

To understand the full agentic payments stack and where MCP sits relative to settlement and control layers, read The Agentic Payments Stack Explained.