Repository navigation
docs: restore SEP-1686 disclosure SHOULD for unbound tasks - #33
Closed
imran-siddique wants to merge 1 commit into
Closed
imran-siddique wants to merge 1 commit into
imran-siddique wants to merge 1 commit into
Conversation
SEP-1686 section 8.1 item 2 told receivers without session or authentication binding to document that limitation. It did not carry into SEP-2663 or tasks.md, which now pairs a MAY for task IDs as bearer tokens with a MUST for auth binding and nothing reconciling the two. Add one Security Considerations bullet to the draft spec. The locked 2026-07-28 page is unchanged. Fixes modelcontextprotocol#20 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
|
Closing this to keep my open queue small for the next few weeks. The branch stays as it is. If you get to it and want it in, say so here and I can reopen it. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #20. This is point 2; point 1 was withdrawn on 2026-09-09.
SEP-1686 §8.1, item 2, said: "Receivers that do not implement session or authentication binding SHOULD document this limitation clearly, as task results may be accessible to any requestor that can guess the task ID." That sentence did not reach SEP-2663 or
tasks.md, so the bearer-token MAY and the Auth binding MUST now sit side by side with nothing between them.This adds one bullet after Auth binding in
specification/draft/tasks.md. Sessions are gone after SEP-2567, so it uses SEP-2663's own term, "authorization context", and says "holds" in place of "guess", since the bullet above already requires unguessable IDs. The locked2026-07-28page is untouched. No schema change.npm run check:schemaandnpm run docs:buildpass.AI disclosure: drafted with Claude Code; I checked the quoted text against both SEPs.
🤖 Generated with Claude Code