-
Notifications
You must be signed in to change notification settings - Fork 166
[Tests] Pin that protected resource metadata advertises no scope of its own #440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
chr-hertel
merged 1 commit into
modelcontextprotocol:main
from
chr-hertel:pr/prm-scope-regression
Aug 18, 2026
+29
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -83,4 +83,33 @@ public function testEmptyAuthorizationServersThrows(): void | |
|
|
||
| new ProtectedResourceMetadata([]); | ||
| } | ||
|
|
||
| #[TestDox('the SDK advertises exactly the scopes it was given, and never adds offline_access')] | ||
| public function testScopesAreOperatorSuppliedOnly(): void | ||
| { | ||
| // SEP-2207: `offline_access` is a refresh-token scope, not something a | ||
| // resource requires. Nothing in the SDK injects it — this pins that, so | ||
| // a future default cannot quietly start advertising one. | ||
| $metadata = new ProtectedResourceMetadata( | ||
| resource: 'https://api.example.com/mcp', | ||
| authorizationServers: ['https://auth.example.com'], | ||
| scopesSupported: ['mcp:read', 'mcp:write'], | ||
| ); | ||
|
|
||
| $data = $metadata->jsonSerialize(); | ||
|
|
||
| $this->assertSame(['mcp:read', 'mcp:write'], $data['scopes_supported']); | ||
| $this->assertNotContains('offline_access', $data['scopes_supported']); | ||
|
Comment on lines
+99
to
+102
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not adding assertArrayHasKey here — line 101 already dereferences the same key and would fail first with a clear message if it were missing; jsonSerialize() also guarantees the key is set whenever scopesSupported is non-null. |
||
| } | ||
|
|
||
| #[TestDox('no scopes given means no scopes_supported member at all')] | ||
| public function testNoScopesMeansNoMember(): void | ||
| { | ||
| $metadata = new ProtectedResourceMetadata( | ||
| resource: 'https://api.example.com/mcp', | ||
| authorizationServers: ['https://auth.example.com'], | ||
| ); | ||
|
|
||
| $this->assertArrayNotHasKey('scopes_supported', $metadata->jsonSerialize()); | ||
| } | ||
| } | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not changing this — the test's input has no whitespace/empties/duplicates, so normalize() is a no-op here; the TestDox describes this test's specific SEP-2207 guard, not a general preservation guarantee.