A protocol owned by one company is a product. A protocol owned by a foundation is infrastructure. In December 2025, MCP crossed that line.
TL;DR
- Anthropic donated the Model Context Protocol to the Agentic AI Foundation, a Linux Foundation fund co-founded with Block and OpenAI.
- Vendor-neutral governance is what lets a standard become shared infrastructure rather than one vendor's moat.
- For builders, it lowers the risk of investing in MCP servers and skills.
What happened
The Model Context Protocol began as Anthropic's open standard in late 2024. By December 2025 it had crossed into mainstream agent infrastructure — tens of millions of monthly SDK downloads, thousands of community servers, first-party support across major platforms. Then Anthropic did the thing that mattered most: it donated MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation, co-founded with Block and OpenAI.
In one move, MCP stopped being "Anthropic's protocol" and became shared infrastructure — governed in the open, the way HTTP and TCP/IP are.
Why governance beats features
It is easy to fixate on a protocol's capabilities. But for anything meant to be a standard, governance is the feature that underwrites all the others.
- Neutrality invites investment. Competitors will build on a protocol no single rival controls. They will hesitate to build on one that a competitor can change or revoke.
- Open process means longevity. Spec Enhancement Proposals, working groups, and a formal process mean the standard evolves predictably rather than at one company's whim.
- No single point of failure. If the originating company pivots, the standard does not die with its roadmap.
You do not pour concrete on land you do not control. Vendor-neutral governance is what makes a protocol safe to build a business on.
What it means for you
If you were weighing whether to invest in MCP — writing servers, exposing your systems, building skills around it — the governance move strengthens the case:
- Lower lock-in risk. You are building on shared infrastructure, not a single vendor's feature.
- A real ecosystem. Multi-vendor governance is correlated with multi-vendor adoption, which is what makes your MCP server valuable across many clients.
- Stability to plan around. A formal process and roadmap make it safer to bet roadmap time on MCP.
The bigger pattern
We have seen this movie before with the web. Technologies become durable infrastructure not at the moment they are clever, but at the moment they become neutral — owned by a community, governed in the open, safe for rivals to share. MCP just had that moment.
The protocol was already useful. Now it is also trustworthy in the specific way that turns a good idea into a standard you can build a decade on.