-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Trailing slash in .well-known/oauth-protected-resource response may violate “Canonical Server URI” requirement #1265
Copy link
Copy link
Open
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureauthIssues and PRs related to Authentication / OAuthIssues and PRs related to Authentication / OAuthbugSomething isn't workingSomething isn't workingready for workEnough information for someone to start working onEnough information for someone to start working on
Description
Question
As I understand it, https://your-mcp.com/.well-known/oauth-protected-resource should return:
{
"resource": "https://your-mcp.com",
"authorization_servers": [
"https://your-auth.com"
],
"scopes_supported": [],
"bearer_methods_supported": [
"header"
]
}However, it actually returns:
{
"resource": "https://your-mcp.com/",
"authorization_servers": [
"https://your-auth.com/"
],
"scopes_supported": [],
"bearer_methods_supported": [
"header"
]
}Note the trailing / in both the resource and authorization_servers values.
According to the MCP spec’s “resource-parameter-implementation” section, I believe this violates the requirement for canonicalization:
https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#resource-parameter-implementation
Is this a bug, or am I misunderstanding the requirement?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureauthIssues and PRs related to Authentication / OAuthIssues and PRs related to Authentication / OAuthbugSomething isn't workingSomething isn't workingready for workEnough information for someone to start working onEnough information for someone to start working on