fix(mcp page): /mcp advertised the 2025-03-26 revision, the endpoint serves 2026-07-28 - #183
Draft
jdevalk wants to merge 1 commit into
Draft
fix(mcp page): /mcp advertised the 2025-03-26 revision, the endpoint serves 2026-07-28#183jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
/mcp advertised the 2025-03-26 protocol revision in two places. That is the oldest revision the Worker still answers via the legacy `initialize` handshake, not the one it serves: `PROTOCOL_VERSION` in mcp/src/index.ts is 2026-07-28, and /.well-known/mcp/server-card.json has said so since that revision landed. Name the current revision, and say plainly that the three handshake-based revisions remain reachable under the published Deprecation/Sunset. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
b84b039
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9f0d403e.specification-website.pages.dev |
| Branch Preview URL: | https://fix-mcp-page-protocol-revisi.specification-website.pages.dev |
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.
What changed
src/pages/mcp.astroclaimed the endpoint speaks the 2025-03-26 protocol revision, in two places (the#endpointparagraph and the "Other MCP clients" paragraph). It does not. Both now name 2026-07-28, and the endpoint paragraph says explicitly that the three handshake-based revisions are still answered viainitializeunder the publishedDeprecation/Sunset.Why now
The daily standards scan checked the MCP specification's own versioning page and confirmed 2026-07-28 is the Current revision. Every other surface in this repo already agrees:
mcp/src/index.ts—const PROTOCOL_VERSION = '2026-07-28';LEGACY_PROTOCOL_VERSIONS = ['2025-11-25', '2025-06-18', '2025-03-26'].public/.well-known/mcp/server-card.json—"protocolVersion": "2026-07-28".public/.well-known/agent-skills/specification-website/SKILL.md— same, andcheck:skillenforces it./spec/agent-readiness/mcp-and-tool-discovery/— already documents the handshake removal in 2026-07-28.So
/mcpwas the one page left advertising the oldest revision the Worker tolerates as the one it serves. An agent reading the human page and the server card got two different answers.Source
Status
No spec-page status is touched. No changelog entry: per
CLAUDE.md, the changelog covers what the spec says, and this is a correction to site plumbing that is invisible on any spec page.npm run build,npm run lint,npm run format:checkandnpm run check:skillall pass.🤖 Generated with Claude Code