MCP Server Security

MCP draft spec adopts Client ID Metadata draft 03

The Model Context Protocol draft specification changelog records an update on 9 Nov 2026: the Client ID Metadata Document reference moves from draft-ietf-oauth-client-id-metadata-document-00 to draft 03. The changelog says MCP implementations that support Client ID Metadata Documents must follow that version.

Facts read on .

Client ID Metadata Documents let a client identify itself to an authorization server with an HTTPS URL that hosts its metadata. The 2026-07-28 specification marks Dynamic Client Registration as deprecated and points new implementations to these documents.

The change sits in the draft, not in the 2026-07-28 release, so it applies to the next revision. The commit that made the change is dated 9 Nov 2026 in the specification repository.

The spec's security best practices page warns that an authorization server fetching a client-supplied metadata URL can be pointed at internal addresses, and recommends blocking private IP ranges and using an egress proxy. Teams running their own authorization server should check which draft their library follows before the next revision.

Sources