---
title: "Get OAuth 2.0 Protected Resource Metadata (MCP path-suffix)"
method: GET
path: "/.well-known/oauth-protected-resource/mcp"
tags: ["oauth2", "metadata"]
---

# Get OAuth 2.0 Protected Resource Metadata (MCP path-suffix)

`GET /.well-known/oauth-protected-resource/mcp`

RFC 9728 path-aware discovery for the /mcp resource. Returns the same metadata as the root well-known endpoint.

## Response `200`

OAuth 2.0 Protected Resource Metadata

- OAuthMetadataGetProtectedResourceMetadataResponseDTO
  - `authorization_details_types_supported` string[] — Array containing authorization details type values supported by the resource server when the authorization_details request parameter is used
  - `authorization_servers` string[] — Array containing authorization server issuer identification URIs
  - `bearer_methods_supported` string[] — Array containing methods supported for presenting bearer tokens
  - `dpop_bound_access_tokens_required` boolean — Boolean value specifying whether the protected resource always requires the use of DPoP-bound access tokens
  - `dpop_signing_alg_values_supported` string[] — Array containing JWS alg values supported by the resource server for validating DPoP proof JWTs
  - `jwks_uri` string, uri — URL of the protected resource's JSON Web Key (JWK) Set document. This contains public keys belonging to the protected resource
  - `resource` string, uri, required — URL of the resource server
  - `resource_documentation` string, uri — URL for human-readable documentation for the resource server
  - `resource_name` string — Human-readable name of the protected resource intended for display to the end user
  - `resource_policy_uri` string, uri — URL for the resource server's policy document
  - `resource_signing_alg_values_supported` string[] — Array containing JWS signing algorithms supported by the protected resource for signing resource responses
  - `resource_tos_uri` string, uri — URL for the resource server's terms of service
  - `scopes_supported` string[] — Array containing OAuth 2.0 scope strings that the resource server can accept in access tokens
  - `signed_metadata` string — Signed JWT containing metadata parameters about the protected resource as claims
  - `tls_client_certificate_bound_access_tokens` boolean — Boolean value indicating protected resource support for mutual-TLS client certificate-bound access tokens

---

[API](https://skmtc.net/wejam/apis/jam.md) · [All operations](https://skmtc.net/wejam/apis/jam/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wejam/jam/revisions/bd5a5f406bca/schema)