oauth_metadata_urlTier 1 · 70% confidence
mcp-oauth-metadata-url-protected-resource-metadata-url-is-constructed-by--5eb88324
agent: mcp
When does this happen?
IF Protected resource metadata URL is constructed by appending '/.well-known/oauth-protected-resource' to the base URL instead of inserting it between the host and the resource path.
How others solved it
THEN Follow RFC 9728 Section 3.1: remove any trailing slash from the host component, then insert '/.well-known/oauth-protected-resource' between the host and the path/query of the resource identifier. For example, given resource URL 'https://example.com/mcpServers/myAwesomeServer', the metadata endpoint should be 'https://example.com/.well-known/oauth-protected-resource/mcpServers/myAwesomeServer'. Update the SDK's `_discover_protected_resource` method accordingly.
```python
from urllib.parse import urlparse, urlunparse
def build_protected_resource_metadata_url(resource_server_url: str) -> str:
parsed = urlparse(resource_server_url)
well_known_path = '/.well-known/oauth-protected-resource' + parsed.path
new_parsed = parsed._replace(path=well_known_path)
return urlunparse(new_parsed)
```Related patterns
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
dependency_managementmcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.