fix: use InvalidTokenError instead of generic Error in MockTokenVerifier #138
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.
Summary
MockTokenVerifier.verifyAccessToken()throwsnew Error('Invalid token')for unrecognized tokens, but the SDK'srequireBearerAuthmiddleware only convertsInvalidTokenErrorinstances to HTTP 401 responses. GenericErrorfalls through as HTTP 500.InvalidTokenErrorfrom@modelcontextprotocol/sdk/server/auth/errors.jsand throw it instead.How it was found
While building token refresh conformance scenarios (access token expires → client gets 401 → uses refresh_token grant), the mock server was returning 500 instead of the expected 401 for expired tokens. Traced to this generic
Errorthrow in the verifier.Test plan
Made with Cursor