Workflow objective: establish an auditable editorial process for Model Context Protocol (MCP) content so that verifiable statements are tied to sources and clearly separated from interpretation or unconfirmed material.
Source URL: https://modelcontextprotocol.io/specification/2025-06-18
Suggested workflow:
1. Collect official sources: prioritize the official specification page as the basis for protocol concepts and record the source URL.
2. Extract verifiable facts: include only protocol concepts supported by the source, without adding unsupported dates, prices, benchmarks, product capabilities, or release claims.
3. Record evidence: keep the source attached to each factual statement so reviewers can trace it.
4. Separate facts from interpretation: factual sections should state only what the source supports; interpretation should be clearly labeled as editorial understanding and not presented as an official conclusion.
5. Require human review: before publication, a human reviewer should check sources, evidence, wording, and risk areas to ensure the draft does not exceed the source basis.
Editorial note: the source can support MCP protocol concepts, but it should not be used on its own to substantiate claims about specific products, commercial terms, performance benchmarks, or unsupported release information. Any such additions would require additional official sources and another review step.