From b84b039ac7f5f8a5d63dced77ad3d30a17120779 Mon Sep 17 00:00:00 2001
From: Joost de Valk <joost@altha.nl>
Date: Tue, 18 Aug 2026 08:09:12 +0200
Subject: [PATCH] fix(mcp page): the endpoint serves 2026-07-28, not 2025-03-26

/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>
---
 src/pages/mcp.astro | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/src/pages/mcp.astro b/src/pages/mcp.astro
index 5a5d22b0..be2a8d06 100644
--- a/src/pages/mcp.astro
+++ b/src/pages/mcp.astro
@@ -39,8 +39,10 @@ const claudeJson = JSON.stringify(desktopConfig, null, 2);
     <article class="prose-spec mt-8">
       <h2 id="endpoint">Endpoint</h2>
       <p>
-        Streamable HTTP MCP, 2025-03-26 protocol revision. Stateless. Wide-open
-        CORS. No authentication.
+        Streamable HTTP MCP, 2026-07-28 protocol revision. Stateless. Wide-open
+        CORS. No authentication. The handshake-based revisions 2025-11-25,
+        2025-06-18 and 2025-03-26 are still answered via <code>initialize</code
+        >, under a published <code>Deprecation</code> and <code>Sunset</code>.
       </p>
       <pre><code>{site.mcp.endpoint}</code></pre>
       <p>
@@ -118,9 +120,9 @@ const claudeJson = JSON.stringify(desktopConfig, null, 2);
 
       <h2 id="connect-other">Other MCP clients</h2>
       <p>
-        Any client that speaks Streamable HTTP MCP (2025-03-26 revision)
-        connects with one URL. There is no client SDK to install and no token to
-        manage. <a
+        Any client that speaks Streamable HTTP MCP (2026-07-28 revision, or one
+        of the older handshake-based revisions above) connects with one URL.
+        There is no client SDK to install and no token to manage. <a
           href="https://github.com/modelcontextprotocol/inspector"
           rel="external">MCP Inspector</a
         > is the fastest way to poke at the schema.