Page history · mcp

SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documentsseps/991-enable-url-based-client-registration-using-oauth-c

Every read this site has made of the page, newest first. A date is when upstream edited the page, where upstream publishes that, and otherwise when the poller caught the edit; each row says which of the two it is.

Recorded changes3including the first read

Lines now297in the newest capture

Characters16,705in the newest capture

First seen 14 Aug 2026 09:58 UTC

Last changed 20 Oct 2026 20:07 UTC

Every recorded edit

3 edits since this site first read it

WhenTitle it carriedWhatLines

14 Aug 26 SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents ·first recorded +303−0 02 Aug 26 SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents ±changed +11−17 02 Aug 26 SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents ±changed +9−9

As it stands

Lines297
Characters16,705
Categoryseps
Pathseps/991-enable-url-based-client-registration-using-oauth-c

Read it upstream →

Sections it gained

# SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents
## Abstract
## Motivation
### The Target Use Case: No Pre-existing Relationship
### Key Innovation: Server-Controlled Trust Without Pre-Coordination
## Specification Changes
### Client Requirements
### Server Requirements
### Discovery
### Integration with Existing MCP Auth
## Rationale
### Why This Solves the "No Pre-existing Relationship" Problem