Important fix for resource validation in MCP - #259089
Merged
Merged
Conversation
In this example: MCP url: https://foo.com/mcp WWW-Auth resource_metadata: https://foo.com/laugh/in/the/face/of/conventions.json PRM: https://foo.com/laugh/in/the/face/of/conventions.json PRM resource property: https://foo.com/mcp I use to do: a URL derived from "WWW-Auth resource_metadata" (which is actually just PRM) is compared to "PRM resource property" but instead it should be: "MCP url" compared to "PRM resource property" Which is what this PR addresses
Rob Lourens (roblourens)
approved these changes
Jul 31, 2025
Tyler James Leonhardt (TylerLeonhardt)
merged commit Jul 31, 2025
8aa5d2f
into
main
18 checks passed
ghost
pushed a commit
to borisdan/mcp-audit-extension
that referenced
this pull request
Aug 13, 2025
…, proxy MCP Server's PRM endpoint through our gateway temp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In this example:
MCP url: https://foo.com/mcp
WWW-Auth resource_metadata: https://foo.com/laugh/in/the/face/of/conventions.json
PRM: https://foo.com/laugh/in/the/face/of/conventions.json
PRM resource property: https://foo.com/mcp
I use to do:
a URL derived from "WWW-Auth resource_metadata" (which is actually just PRM) is compared to "PRM resource property"
but instead it should be:
"MCP url" compared to "PRM resource property"
Which is what this PR addresses
ref https://datatracker.ietf.org/doc/html/rfc9728#section-3.3