Unverified50% confidenceFactExact time
MCP, OpenAI Function Calling, and Google Extension have not yet formed a unified industry standard
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
8/9/2026
First Seen
Valid until: 11/7/2026
Sources
AI落地团队的隐性成本：碎片化、审查税与集成之痛
Related Claims
UnverifiedBefore MCP, the interaction between large models and external tools mainly relied on vendor-defined Function Calling mechanisms, with OpenAI and Google Gemini each having different function calling formats that were mutually incompatible.72% similarUnverifiedOpen standards such as Model Context Protocol (MCP) are attempting to alleviate platform lock-in issues in the AI Agent space, but the industry has yet to form a unified Agent interoperability standard.71% similarVerifiedGoogle, OpenAI, and other mainstream vendors have successively announced support for the MCP protocol.71% similarUnverifiedBefore MCP appeared, there were multiple mutually incompatible integration specifications such as LangChain Tools and OpenAI Function Calling, causing ecosystem fragmentation.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/714711API
curl https://kongchang.com/api/v1/knowledge/claims/714711MCP
get_claim(id=714711)