Client Registration changedspecification/draft/basic/authorization/client-registration
Nearest release: v2.1.305, published under an hour 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 20 Oct 2026 20:02 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 20 Oct 2026 20:07 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−8removed
From line
1
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Client Registration
22
3<div id="enable-section-numbers" />
4
53MCP supports three client registration mechanisms. Choose based on your scenario:
64
75* **[Client ID Metadata Documents](#client-id-metadata-documents)**: When client and server have no prior relationship (most common)
from line 133
135133
136134## Dynamic Client Registration
137135
138<Warning>
139 Dynamic Client Registration is deprecated. New implementations should use
140 [Client ID Metadata Documents](#client-id-metadata-documents) instead. This
141 option remains available for backwards compatibility with authorization
142 servers that do not support Client ID Metadata Documents.
143</Warning>
136> [!WARNING]
137>
138> Dynamic Client Registration is deprecated. New implementations should use
139> [Client ID Metadata Documents](#client-id-metadata-documents) instead. This
140> option remains available for backwards compatibility with authorization
141> servers that do not support Client ID Metadata Documents.
144142
145143MCP clients and authorization servers **MAY** support the
146144OAuth 2.0 Dynamic Client Registration Protocol [RFC7591](https://datatracker.ietf.org/doc/html/rfc7591)
No line in this hunk matches that.