MCP Donated to Linux Foundation’s AAIF — Three Changes for Japanese SaaS AEO Strategy
On December 9, 2025, Anthropic’s Model Context Protocol (MCP) was formally donated to the Agentic AI Foundation (AAIF), a directed fund under the Linux Foundation co-founded by Anthropic, OpenAI, Block, Google, Microsoft, and AWS. This move elevated MCP from a single-company protocol to an industry-standard governed by a neutral body. From KanseiLink’s perspective, we analyze three fundamental shifts this open standardization brings to Japanese SaaS companies’ AEO strategies.
1. What Is AAIF — Background and Significance
The Agentic AI Foundation (AAIF) was established on December 9, 2025 as a directed fund under the Linux Foundation. Its three founding projects are Anthropic’s MCP, Block’s Goose, and OpenAI’s AGENTS.md. Supporting organizations include Google, Microsoft, AWS, Cloudflare, and Bloomberg.
"MCP has rapidly become the universal standard protocol for connecting AI models to tools, data and applications, with more than 10,000 published MCP servers." — Linux Foundation, December 9, 2025
The most significant aspect of MCP’s Linux Foundation transfer is the neutralization of governance. Previously managed solely by Anthropic, MCP is now evolved through Working Groups, Spec Enhancement Proposals (SEPs), and a formal governance process involving the broader community.
This transfer occurring just one year after MCP’s launch demonstrates how rapidly the industry has embraced it as the de facto standard. For comparison, HTTP/1.1 took years to achieve RFC standardization. MCP reached this milestone in record time.
2. MCP Ecosystem Status as of April 2026
Since AAIF’s formation, the MCP ecosystem has been expanding rapidly. Key developments confirmed by KanseiLink in April 2026:
| Development | Details | Verified |
|---|---|---|
| Pinterest deploys production-scale MCP ecosystem | Built a production-ready MCP ecosystem enabling AI agents to automate complex engineering tasks (April 2026, InfoQ) | ✅ Confirmed |
| Lucidworks launches MCP server | Claims up to 10x reduction in AI integration timelines and $150K+ savings per integration (April 8, 2026) | ✅ Confirmed (self-reported) |
| Google Colab adds MCP support | Released open-source Colab MCP Server enabling AI agents to directly interact with Google Colab | ✅ Confirmed |
| MCPDevSummit + MCPCon events scheduled | North America: Oct 22-23, 2026 (San Jose); Europe: Sept 17-18, 2026 (Amsterdam) | ✅ Confirmed |
| Production pain points to be resolved in 2026 | Auth flows, session management, multi-agent communication — improvements in progress via SEPs | ⚠️ Roadmap-based (not finalized) |
3. Three Shifts for Japanese SaaS Companies
MCP becoming an open standard represents a strategic inflection point for Japanese SaaS companies. Drawing on KanseiLink’s data across 225 tracked services, we identify three key changes.
MCP Support Shifts from Competitive Advantage to Baseline Requirement
Currently, only approximately 23% of the 225 services tracked by KanseiLink offer an official MCP server. However, as MCP cements its status as the industry standard, lack of MCP support will come to be viewed as a “missing feature” equivalent to not having an API at all.
Japanese services that have completed official MCP integration early — freee, kintone, Money Forward — will consolidate their first-mover advantage through this standardization. Meanwhile, major domestic players without MCP support (LINE WORKS, Yayoi, Rakuten, etc.) are losing their window for differentiation.
AEO Score Methodology Will Evolve — Official MCP Compliance Gains Weight
As MCP specifications evolve under AAIF governance, an additional evaluation dimension will emerge: degree of spec compliance. KanseiLink’s current AEO scores are primarily based on official MCP presence, success rate, and latency. Going forward, adherence to SEPs (OAuth 2.1 compliance, Tool Schema quality, etc.) will be incorporated into the evaluation.
In other words, simply “building an MCP server” will no longer be sufficient. What will matter is the ability to maintain spec compliance and continuously update implementations as the standard evolves.
Third-Party MCP Ecosystems Become a Lifeline for Japanese SaaS Without Official Support
The AAIF transfer increases incentives for third parties to build and publish standard-compliant MCP servers — a double-edged sword for Japanese SaaS lacking official MCP.
On one hand, community or partner-built MCP servers may fill the gap. On the other, if uncontrolled third-party MCP servers proliferate with inconsistent quality, agent experiences will degrade and AEO scores will fall. KanseiLink will continue differentiating official MCP from certified third-party MCP in our scoring to surface this risk.
4. KanseiLink’s Outlook — Forecast for H2 2026
On the timeline for MCP’s AAIF transfer to ripple through the Japanese SaaS market, KanseiLink projects the following:
- Q3 2026 (Jul–Sep): Catalyzed by MCPCon events, major domestic SaaS vendors in HR, CRM, and marketing — sectors currently behind on MCP — are most likely to announce official MCP support.
- Q4 2026 (Oct–Dec): As SEPs (spec improvement proposals) begin materializing, questions of full OAuth 2.1 compliance and Tool Schema standardization will become evaluation criteria. We anticipate announcing revisions to the AEO scoring methodology during this period.
- 2027 and beyond: MCP will become as expected as RESTful APIs are today. The question will no longer be whether a service supports MCP, but how well it does so.
KanseiLink’s AEO evaluation criteria will be updated incrementally to reflect AAIF governance evolution. The current Q2 2026 rankings were evaluated under pre-AAIF transfer criteria. Beginning with the Q3 2026 ratings, we plan to transition to an evaluation framework that places greater weight on specification compliance.
Conclusion
MCP’s donation to AAIF is a historic milestone in the standardization of AI agent era infrastructure. Having Anthropic, OpenAI, Google, and Microsoft at the same governance table under the neutral Linux Foundation dramatically reduces vendor lock-in risk.
For Japanese SaaS companies, this standardization ends the debate over “whether to support MCP” and shifts the conversation to “when and at what level to implement it.” KanseiLink will continue providing AEO evaluations grounded in real data from 225 services and agent telemetry, tracking the progress of this industry standardization.
Check Your Service’s AEO Score
Understand your MCP readiness, success rates, and latency with KanseiLink’s real-world data.
Request an AEO Rating Report