OAuth 2.0 Protected Resource Metadata support

According to MCP atuhorization specification 2025-06-18, supporting OAuth 2.0 Protected Resource Metadata becomes MUST.
https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization

Do you have a plan to add /.well-known/oauth-protected-resource endpoint to response resource metadata and to add the resource server endpoint info to WWW-Authenticate header of MCP API endpoints?

[example [RFC9728](https://datatracker.ietf.org/doc/html/rfc9728)]
HTTP/1.1 200 OK
Content-Type: application/json

{
"resource":
"https://resource.example.com",
"authorization_servers":
["https://as1.example.com",
"https://as2.example.net"],
"bearer_methods_supported":
["header", "body"],
"scopes_supported":
["profile", "email", "phone"],
"resource_documentation":
"https://resource.example.com/resource_documentation.html"
}

Start by reading the MCP authorization specification dated 2025-06-18 and RFC9728. Inspect the MCP API endpoints and response resource metadata handling; done means serving /.well-known/oauth-protected-resource and including the resource server endpoint information in their WWW-Authenticate headers.

Vom Indexierungsmodell aus dem Issue-Text verfasst.