Skip to content

docs(site,docs): name the revision GitMCP pins, and the one it is behind - #50

Merged
blakebauman merged 2 commits into
mainfrom
gitmcp-protocol-revision
Aug 26, 2026
Merged

blakebauman merged 2 commits into
mainfrom
gitmcp-protocol-revision

Conversation

@blakebauman

Copy link
Copy Markdown
Member

"A public 2025-era server on the session handshake" was doing a lot of vague work for a claim that is a single date. This replaces it with what the servers actually answer.

Checked live, not inferred

Server Negotiates
GitMCP 2025-03-26
Cloudflare docs MCP 2025-11-25
the fold gateway 2025-11-25

So GitMCP is two revisions behind — 2025-06-18, then 2025-11-25 — and the demo federates it anyway, which is the entire point of that row.

The baseline needed correcting

An earlier pass had it as "two revisions behind the 2026-07-28 you asked the gateway for at initialize". That is wrong twice:

  1. The gateway does not speak 2026-07-28. Ask for it and it negotiates down to 2025-11-25 — verified against the deployed v1.14.0.
  2. Against 2026-07-28 the gap would be three revisions, not two.

The comparison is now against what the gateway actually negotiates, which is also the number a reader gets if they check. The walkthrough's curl examples keep asking for the newer version, because watching it negotiate down is the honest demonstration — and the sentence now says "whatever you ask for at initialize" so that reads as intended rather than as an error.

Two "a revision behind" mentions were undercounting for the same reason and now say two.

Scope

Blog posts keep the old phrasing — they are dated writing about what ran then, the same call #44 made.

Build, typecheck and lint pass; the one lint warning is pre-existing. Site and docs are deployed.

🤖 Generated with Claude Code

blakebauman and others added 2 commits August 25, 2026 20:45
"2025-era server on the session handshake" separated GitMCP from nothing:
all three upstreams answer with a 2025 revision, and demo-tasks hands out
an mcp-session-id too — cf-docs is the sessionless one. The phrasing was
true when demo-tasks was pinned stateless and has been stale since.

What is actually distinctive is the revision gap. GitMCP answers
initialize with 2025-03-26, one behind cf-docs and demo-tasks (2025-11-25)
and two behind the 2026-07-28 the walkthrough's own curl asks the gateway
for. fold negotiates down and the caller never sees the seam, which is the
point section 4 was reaching for.

Also swaps that section's example repo: modelcontextprotocol/servers
answers "No documentation found." — go-sdk returns a real index, and it is
the SDK fold is built on. Verified live against demo.fold.run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
"A 2025-era server on the session handshake" was doing a lot of vague
work for a claim that is a single date. Replaced with what the servers
actually answer, checked live rather than inferred:

  GitMCP              2025-03-26
  Cloudflare docs     2025-11-25
  the fold gateway    2025-11-25

So GitMCP is two revisions behind — 2025-06-18, then 2025-11-25 — and
the demo federates it anyway, which is the whole point of the row.

The baseline needed correcting. An earlier pass had it as "two revisions
behind the 2026-07-28 you asked the gateway for at initialize", which is
wrong twice: the gateway does not speak 2026-07-28 — ask for it and it
negotiates down to 2025-11-25 — and against 2026-07-28 the gap would be
three revisions, not two. The comparison is now against what the gateway
actually negotiates, which is also the number a reader checking this
would get. The walkthrough's curl examples keep asking for the newer
version, because watching it negotiate down is the honest demonstration
and the sentence now says so.

The two "a revision behind" mentions were undercounting for the same
reason and now say two.

Blog posts keep the old phrasing; they are dated writing about what ran
then.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@blakebauman
blakebauman merged commit b62b60a into main Aug 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant