Predict the correct client behavior when an MCP server responds with an unsupported protocol version

Attempt it

A client sends `initialize` proposing `protocolVersion: "2025-11-05"`. The server replies with `protocolVersion: "2024-11-01"`, a version the client does not recognize. The client continues the session and sends `tools/list`.

Quick reference

TL;DR

The client must abort: when the server returns a protocolVersion the client does not support, the spec says close the transport and report incompatibility. Sending tools/list anyway is the bug.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Imagine two people agreeing on a language before a meeting. You say, 'Let's use English-2025.' The other person replies, 'I only speak English-2024,' a dialect you have never learned. The safe move is to stop and say 'we are not compatible,' then hang up. The dangerous move is to keep talking anyway, guessing at words, hoping the meaning carries. You might get lucky on simple sentences and then completely misunderstand an important one. MCP version negotiation works the same way. The client proposes a version, the server answers with the version it will actually use, and if the client does not recognize that answer it should disconnect rather than push forward and risk silent misunderstandings later in the conversation.

Key concepts

Protocol version negotiation Initialize lifecycle Capability negotiation

Quick scan · 2–4 min

Everything important, quickly.

5 min: initialize handshake + server-authoritative version + abort rule on unrecognized version + capability decay failure modes + the security-mismatch variant.

Side-by-side

Behavior	Abort on unrecognized version (correct)	Continue and send tools/list (the bug)
When the mismatch surfaces	Immediately at the initialize handshake	Later, at some runtime call
Failure shape	One loud, clear incompatibility error	Scattered errors or silent semantic drift
Security posture	No assumptions made on an unverified contract	May assume guarantees the old version never gave
Debuggability	Single obvious failure point	Hard to trace, looks like a tool bug

Real-world examples

Real products, models, and research that use this idea.

The official MCP TypeScript and Python SDKs reject an initialize response whose protocolVersion is not in the client's supported set, closing the transport.
Claude Code and Cursor pin the protocol versions their MCP clients accept, so a server advertising an unknown date fails fast at connection rather than mid-session.
The MCP Inspector debugging tool surfaces a version mismatch at the initialize step, making this exact negotiation failure visible during development.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QIf the server returns a version the client DOES support but the client proposed a newer one, what happens?

Sign in or go Pro to see the approach for this follow-up.

QHow does an unrecognized version create a security mismatch, not just a feature gap?

Sign in or go Pro to see the approach for this follow-up.

QWhere should the abort be enforced (in the SDK, the host, or both)?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.