Join our Newsletter — 33% off our NHI Course
Home› Guides› MCP Specification Version Tracker: Every Revision, Change and…
Guide AI Platforms

MCP Specification Version Tracker: Every Revision, Change and Deprecation Date

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 15 November 2026 13 min read
On this page

The Model Context Protocol has had five dated specification revisions in under two years, and the latest one removed the initialisation handshake that every earlier client and server depends on. This tracker lists each revision of the MCP specification, what changed in it according to the official changelogs, which features are now deprecated and when they become eligible for removal, and how old and new implementations interoperate. It is written for engineers maintaining MCP clients, servers and SDK integrations, for architects planning upgrades and for security teams who need to know which revision a server speaks before they assess it. All facts come from the specification repository and modelcontextprotocol.io. Last checked: 2026-11-15.

This is an independent reference page from NHI Mgmt Group based on public provider documentation; it is not sponsored or endorsed by any provider.

Key takeaways

  • 2026-07-28 is the current revision. The versioning page names it as current; 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05 are the earlier revisions, and a Draft collects changes for the next one.
  • The version string is a date of breaking change, not a release date. Identifiers use YYYY-MM-DD to mark the last date backwards-incompatible changes were made, and compatible updates do not change the identifier.
  • 2026-07-28 split MCP into modern and legacy eras. Sessions, the initialize handshake and SSE resumability were removed, and every request now carries its protocol version and client capabilities in _meta.
  • Deprecation now has a formal clock. SEP-2596 introduced Active, Deprecated and Removed states with a minimum twelve-month window, and Roots, Sampling, Logging and Dynamic Client Registration are deprecated with earliest removal in the first revision on or after 2027-07-28.
  • Authorisation has tightened in every revision. From an OAuth 2.1 framework in 2025-03-26 to resource indicators, Client ID Metadata Documents and issuer validation, each revision changes what a client and authorisation server must do.

How MCP versioning works

According to the versioning page for revision 2026-07-28, MCP uses string version identifiers in the format YYYY-MM-DD to indicate the last date backwards-incompatible changes were made. The protocol version is not incremented for backwards-compatible updates. Revisions carry one of three labels:

  • Draft: in-progress specifications, not yet ready for consumption.
  • Current: the version ready for use, which may still receive backwards-compatible changes.
  • Final: past, complete specifications that will not be changed.

Individual features have their own state under the feature lifecycle policy: Active, Deprecated (still in the specification but scheduled for removal, with a documented migration path) or Removed (deleted from the draft and absent from the next Current revision). A Deprecated feature stays for at least twelve months, or at least ninety days under the expedited-removal exception, before it becomes eligible for removal. Changes are proposed through Specification Enhancement Proposals (SEPs); revision 2026-07-28 formalised a PR-based SEP workflow (SEP-1850).

Every revision at a glance

As of 15 November 2026, from the revision list on modelcontextprotocol.io and each revision's changelog.

RevisionStatusBase protocol modelHeadline changes
2024-11-05FinalStateful connections with capability negotiationInitial specification: resources, prompts and tools on servers; sampling on clients; stdio and HTTP with Server-Sent Events transports
2025-03-26FinalStatefulOAuth 2.1 authorisation framework; Streamable HTTP replaces HTTP+SSE; JSON-RPC batching added; tool annotations
2025-06-18FinalStatefulBatching removed; structured tool output; servers classed as OAuth resource servers; RFC 8707 resource indicators required; elicitation; MCP-Protocol-Version header
2025-11-25FinalStatefulOpenID Connect discovery; Client ID Metadata Documents; URL mode elicitation; tool calling in sampling; experimental tasks; icons; JSON Schema 2020-12 default
2026-07-28CurrentStateless, per-request metadataSessions and initialize removed; server/discover; subscriptions/listen; Multi Round-Trip Requests; tasks moved to an extension; formal deprecation policy
DraftDraftAs 2026-07-28Accumulates changes for the next revision (see below)

The specification was announced as an open standard by Anthropic on 25 November 2024, alongside SDKs and a repository of reference servers. On 9 December 2025 Anthropic announced it was donating MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation co-founded by Anthropic, Block and OpenAI, and stated that MCP's governance model would remain unchanged.

2024-11-05: the initial specification

The first revision defined MCP as JSON-RPC 2.0 messages between hosts (LLM applications), clients (connectors inside the host) and servers (services providing context and capabilities), with stateful connections and capability negotiation. Servers could offer resources, prompts and tools; clients could offer sampling. Utilities covered configuration, progress, cancellation, error reporting and logging. Two transports were defined: stdio, where the client launches the server as a subprocess, and HTTP with Server-Sent Events. The specification states it was inspired by the Language Server Protocol.

2025-03-26: authorisation and Streamable HTTP

  • Authorisation: a comprehensive authorisation framework based on OAuth 2.1 (PR #133).
  • Transport: the HTTP+SSE transport was replaced by Streamable HTTP (PR #206).
  • Batching: JSON-RPC batching support was added (PR #228), and removed again in the next revision.
  • Tool annotations: annotations describing tool behaviour, such as read-only or destructive (PR #185).
  • Schema: a message field on ProgressNotification, audio content alongside text and images, and a completions capability for argument autocompletion.

For the transport change in practice, see MCP SSE to Streamable HTTP Migration.

2025-06-18: resource servers and elicitation

  • Batching removed: support for JSON-RPC batching was removed (PR #416).
  • Structured tool output: tools can return structured content (PR #371).
  • OAuth resource servers: MCP servers are classified as OAuth resource servers, with protected resource metadata used to discover the authorisation server (PR #338).
  • Resource indicators: clients must implement RFC 8707 to prevent malicious servers obtaining access tokens (PR #734).
  • Security guidance: clarified security considerations and a new security best practices page.
  • Elicitation: servers can request additional information from users during interactions (PR #382).
  • Resource links: tool call results can include resource links (PR #603).
  • Protocol version header: the negotiated version must be sent in the MCP-Protocol-Version header on subsequent HTTP requests (PR #548).
  • Schema: _meta on more interface types (PR #710), a context field on CompletionRequest (PR #598) and a title field for display names (PR #663).

2025-11-25: discovery, CIMD and experimental tasks

  • Discovery: authorisation server discovery supports OpenID Connect Discovery 1.0 (PR #797), and protected resource metadata discovery aligns with RFC 9728, making the WWW-Authenticate header optional with a .well-known fallback (SEP-985).
  • Client registration: OAuth Client ID Metadata Documents added as a recommended registration mechanism (SEP-991).
  • Scopes: incremental scope consent via WWW-Authenticate (SEP-835).
  • Elicitation: URL mode elicitation (SEP-1036) and standards-based enum schemas (SEP-1330).
  • Sampling: tool calling via tools and toolChoice parameters (SEP-1577).
  • Tasks: experimental support for durable requests with polling and deferred results (SEP-1686).
  • Other: icons for tools, resources and prompts (SEP-973), tool name guidance (SEP-986), HTTP 403 for invalid Origin headers (PR #1439), input validation errors returned as tool execution errors (SEP-1303) and JSON Schema 2020-12 as the default dialect (SEP-1613).
  • Governance: formal governance structure (SEP-932), working and interest groups (SEP-1302) and an SDK tiering system (SEP-1730).

2026-07-28: stateless MCP

The current revision is the largest change since launch. Its major changes, summarised from the changelog:

ChangeWhat it means for implementersReference
Protocol-level sessions and Mcp-Session-Id removedList endpoints no longer vary per connection; cross-call state uses server-minted handles passed as tool argumentsSEP-2567
initialize handshake removedEach request carries protocol version and client capabilities in _meta; clients should send clientInfo and servers serverInfoSEP-2575
server/discover addedServers must implement it to advertise versions, capabilities and identity; clients may call it firstSEP-2575
subscriptions/listen replaces the HTTP GET endpoint and resource subscribe methodsOne long-lived POST response stream for opted-in change notificationsSEP-2575
ping, logging/setLevel and notifications/roots/list_changed removedLog level set per request via _metaSEP-2575
Tasks moved to the io.modelcontextprotocol/tasks extensionPolling via tasks/get, input via tasks/update; tasks/list removedSEP-2663
Multi Round-Trip RequestsServers return InputRequiredResult instead of sending server-initiated requests; clients retry with inputResponsesSEP-2322
Required resultType on all results"complete" or "input_required"; clients treat a missing field from older servers as completeSEP-2322
SSE resumability removedNo Last-Event-ID; a broken stream means re-issuing the request with a new IDSEP-2575

Minor changes include an extensions capability field, OpenTelemetry trace context keys in _meta (SEP-414), required Mcp-Method and Mcp-Name headers on Streamable HTTP POSTs (SEP-2243), ttlMs and cacheScope on list and read results (SEP-2549), and resource-not-found moving from -32002 to -32602. On authorisation, servers should include iss in authorisation responses per RFC 9207 and clients must validate it (SEP-2468); clients must set application_type in Dynamic Client Registration (SEP-837); and client credentials are bound to the issuing authorisation server (SEP-2352). The JSON-RPC server-error range is now partitioned, with -32020 to -32099 reserved for the specification. For the authorisation flow in depth, see the MCP Authorisation Specification Guide.

Changes in the Draft since 2026-07-28

As of 15 November 2026. Draft content can change before the next revision. The draft changelog updates the referenced OAuth Client ID Metadata Document draft from -00 to draft-ietf-oauth-client-id-metadata-document-03, which implementations supporting CIMD must follow, and restores the optional _meta field on several request and result types that was unintentionally dropped in 2026-07-28. The roadmap, last updated 2026-08-22, lists priority areas including agentic messaging primitives and HTTP-native transport unification, with work on HTTP over stdio and ETag-based caching; it states that it reflects current thinking rather than firm commitments.

Deprecated features and removal dates

As of 15 November 2026, from the deprecated features registry in revision 2026-07-28. Earliest removal marks eligibility; actual removal is a Core Maintainer decision.

FeatureDeprecated inMigration pathEarliest removal
Dynamic Client Registration (RFC 7591)2026-07-28Client ID Metadata DocumentsFirst revision released on or after 2027-07-28
HTTP+SSE transport2025-03-26Streamable HTTPThree months after SEP-2596 reaches Final
includeContext: "thisServer" / "allServers"2025-11-25Omit the field or use "none"Follows Sampling
Logging2026-07-28Log to stderr for stdio; use OpenTelemetryFirst revision released on or after 2027-07-28
Roots2026-07-28Pass directories or files via tool parameters, resource URIs or server configurationFirst revision released on or after 2027-07-28
Sampling2026-07-28Integrate directly with LLM provider APIsFirst revision released on or after 2027-07-28

The registry records no features as Removed under the policy yet. Because Sampling is deprecated, review designs that rely on it; see the MCP Sampling and Elicitation Security Guide for the security side.

How old and new implementations interoperate

The 2026-07-28 versioning page calls revisions that use per-request metadata modern (2026-07-28 and later), those using the initialize handshake legacy (2025-11-25 and earlier), and implementations supporting both dual-era. A server that does not support the requested version must return UnsupportedProtocolVersionError (code -32022) listing the versions it supports.

ClientServerOutcome stated in the specification
ModernModernWorks; version mismatches surface as UnsupportedProtocolVersionError and the client retries
ModernLegacyFails; on stdio clients should send server/discover first to fail deterministically
Dual-eraModernWorks; the client stays modern
Dual-eraLegacyWorks; the client falls back to initialize
LegacyModernFails; legacy clients have no fall-forward mechanism
LegacyDual-eraWorks under the negotiated legacy revision

Clients should cache the detected era per server process (stdio) or origin (HTTP). SDK support follows the SEP-1730 tiers: Tier 1 SDKs need a 100% conformance pass rate and new protocol features before a new specification release, Tier 2 an 80% pass rate and new features within six months.

Upgrading safely: a phased approach

  1. Inventory: record the protocol version each client and server negotiates, using the MCP-Protocol-Version header or _meta values in logs. The MCP Server Inventory Template has fields for this.
  2. Check SDK support: confirm your SDK's tier and which revisions it implements, including legacy support.
  3. Go dual-era first: upgrade clients to dual-era so they keep working with legacy servers, then move servers.
  4. Retest authorisation: verify issuer validation, issuer-keyed credential storage and CIMD support against your authorisation server.
  5. Replace deprecated features: plan away from Sampling, Roots, Logging, HTTP+SSE and Dynamic Client Registration before 2027-07-28.
  6. Roll back by version: keep the previous server build able to answer initialize until all clients are confirmed modern.

Measure progress with the share of servers on 2026-07-28, the number still on HTTP+SSE, the count of UnsupportedProtocolVersionError responses and the number of clients still registering through Dynamic Client Registration.

Where identity and security fit

Most revision changes with security weight concern the identities MCP clients and servers use. The move from anonymous connections in 2024-11-05 to OAuth resource servers, RFC 8707 audience binding, Client ID Metadata Documents and issuer-bound credentials means each MCP client is now a registered OAuth client and each server a protected resource, and both should be governed as non-human identities with owners, scopes and rotation. Removing sessions in 2026-07-28 also removes Mcp-Session-Id as a correlation key, so logging should rely on clientInfo, authorisation context and OpenTelemetry trace context instead. Revision drift is a risk in its own right: a server still on HTTP+SSE or a client registering through Dynamic Client Registration is running deprecated paths that will eventually lose specification support.

Practitioner checklist

  • Record the negotiated MCP revision for every client and server in your inventory.
  • Subscribe to the specification changelog and deprecated features registry, and review the Draft changelog before each upgrade.
  • Upgrade clients to dual-era before moving servers to 2026-07-28.
  • Remove HTTP+SSE endpoints and move remote servers to Streamable HTTP.
  • Plan migrations away from Sampling, Roots, Logging and Dynamic Client Registration before 2027-07-28.
  • Validate iss in authorisation responses and key stored client credentials by issuer.
  • Check that your SDK's tier and supported revisions match your target revision.
  • Re-run security tests after each revision change; see the MCP Security Testing Guide.

Standards and references

Related NHI Mgmt Group resources: What Is MCP? The Model Context Protocol Explained (2026), MCP Security Guide, MCP Authorisation Specification Guide, Streamable HTTP vs stdio MCP Transport, MCP Client Support Tracker.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 15 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.