One read of Model Context Protocolmcp-20260821T113712Z
1 pages moved out of 144 read.
Pages moved
1
significant first
Pages read
144
in this capture
Captured
11:37 UTC
Corpus hash
2994f61d14f2
corpus-hash
What this read moved
1-1 of 1community/sep-guidelines Changed · +2 / -2 lines
from line 96
9696
97978. **Resolution**: The SEP may be `accepted`, `rejected`, or returned for revision. The sponsor updates the status.
9898
999. **Finalization**: Once accepted, the reference implementation must be completed. For Standards Track SEPs with observable protocol behavior, a [conformance test](#conformance-test-requirement) must also be merged. When complete and incorporated into the specification, the sponsor updates the status to `final`.
999. **Finalization**: Once accepted, the reference implementation must be completed. For Standards Track SEPs with observable protocol behavior, a [conformance test](#conformance-test-requirement) must also be merged. The author adds the specification changes (schema changes, specification text, and a changelog entry) to the SEP's pull request. SDK implementations are not required for a SEP to become `final`. When this work is complete, the sponsor updates the status to `final` and the SEP's PR can be merged.
100100
101101### SEP Statuses
102102
from line 211
211211* Clear benefit to the MCP ecosystem
212212* Community support and consensus
213213
214Once a SEP has been accepted, the reference implementation must be completed. When complete and incorporated into the main repository, the status changes to "Final".
214Once a SEP has been accepted, the author adds the specification changes (schema changes, specification text, and a changelog entry) to the SEP's pull request. The reference implementation must be completed, along with any required [conformance test](#conformance-test-requirement). SDK implementations are not required. When this work is complete, the status changes to "Final" and the PR can be merged.
215215
216216## Conformance Test Requirement
217217