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

Client Registration changedspecification/2026-07-28/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 22 Oct 2026 20:37 UTC.

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

The whole hunk

from line 44, old and new numbered
/
lines
from line 44
4444* **SHOULD** cache metadata respecting HTTP cache headers
4545* **MUST** validate redirect URIs presented in an authorization request against those in the metadata document
4646* **MUST** validate the document structure is valid JSON and contains required fields
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](/specification/2026-07-28/basic/authorization/security-considerations#client-id-metadata-document-security)
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](/specification/2026-07-28/basic/authorization/security-considerations.md#client-id-metadata-document-security)
4848 
4949### Example Metadata Document
5050 
from line 181
181181credentials with the specific authorization server that issued them,
182182keyed by the authorization server's `issuer` identifier. When the
183183authorization server changes (detected via updated
184[protected resource metadata](/specification/2026-07-28/basic/authorization/authorization-server-discovery#authorization-server-location)),
184[protected resource metadata](/specification/2026-07-28/basic/authorization/authorization-server-discovery.md#authorization-server-location)),
185185clients **MUST NOT** reuse client credentials
186186from a different authorization server and **MUST** re-register
187187with the new authorization server.
Feedback