Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsModel Context Protocol 28 Sep 2026
One change · mcp

SEP Guidelines changedcommunity/sep-guidelines

Nearest release: v2.1.284, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 28 Sep 2026 21:57 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.

Upstream edited
Recorded here
Lines+11added
Lines−11removed
From line 96 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits5to this page, all time

The whole hunk

from line 96, old and new numbered
/
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. 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.
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. Merged SEPs are published in the [SEP index](/seps/index), and each one is reachable by number at `modelcontextprotocol.io/seps/<number>` (for example, [/seps/1850](/seps/1850)).
100100 
101101### SEP Statuses
102102 
103| Status | Meaning |
104| ------------ | ------------------------------------------------ |
105| `draft` | Has a sponsor, undergoing informal review |
106| `in-review` | Ready for formal Core Maintainer review |
107| `accepted` | Approved, awaiting implementation + conformance |
108| `rejected` | Declined by Core Maintainers |
109| `withdrawn` | Author withdrew the proposal |
110| `final` | Complete with implementation and conformance |
111| `superseded` | Replaced by a newer SEP |
112| `dormant` | No sponsor found within 6 months; can be revived |
103| Status | Meaning |
104| - | - |
105| `draft` | Has a sponsor, undergoing informal review |
106| `in-review` | Ready for formal Core Maintainer review |
107| `accepted` | Approved, awaiting implementation + conformance |
108| `rejected` | Declined by Core Maintainers |
109| `withdrawn` | Author withdrew the proposal |
110| `final` | Complete with implementation and conformance |
111| `superseded` | Replaced by a newer SEP |
112| `dormant` | No sponsor found within 6 months; can be revived |
113113 
114114**Important distinction**: `dormant` is not the same as `rejected`. A dormant SEP simply didn't find a sponsor - the idea may still be valid. If circumstances change (new community interest, new use cases), a dormant SEP can be revived by finding a sponsor and reopening the PR.
115115 
Feedback