A procurement team wants to confirm that the MCP specification is not controlled by a single vendor before standardizing on it. Which description of MCP's stewardship is accurate?
Select an answer to reveal the explanation.
Short Explanation
You want to know who holds the pen. For MCP, it's an open project under the Linux Foundation umbrella, with individuals — not companies — holding governance seats. The IETF and W3C options sound official, but MCP isn't published there.
Full Explanation
The MCP governance page states that the project has been established as Model Context Protocol a Series of LF Projects, LLC, and that policies from LF Projects apply to it, including trademark guidelines. Technical governance follows a published structure of contributors, maintainers, core maintainers and lead maintainers, and membership is held by individuals rather than companies, with no seats reserved for specific employers. Specification changes go through public Specification Enhancement Proposals, and contributions use the Apache License 2.0. That combination is what makes MCP vendor-neutral and openly governed. Describing MCP as one model vendor's proprietary interface ignores this governance and the open licence. The IETF option is wrong because MCP revisions are published on modelcontextprotocol.io and identified by date, not issued as RFCs, even though MCP references several RFCs such as those for OAuth. The W3C option is also wrong; MCP is not a W3C recommendation, although it cites W3C formats such as Trace Context. Exam caveat: the MCPA credential itself is offered by Linux Foundation training, which is a separate fact from how the specification is governed. Operational check: point procurement to the governance page and the public SEP process as evidence that no single vendor controls the specification.