Trailing slash in `.well-known/oauth-protected-resource` response may violate “Canonical Server URI” requirement

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?

まず .well-known/oauth-protected-resource のレスポンスの実装箇所を特定し、その resource と authorization_servers の値を、リンク先の MCP の正規化要件と比較します。末尾のスラッシュに関する想定動作を確認し、その後、レスポンスの値について、完了を検証できるようにテストカバレッジを特定するか追加します。