MCP 2026-07-28 Specification: transport going stateless
Across our Tier 1 SDKs, we’re seeing close to half-a-billion downloads a month, with both TypeScript and Python SDKs crossing the 1 billion total downloads threshold. It was one of the most highly-requested features from developers who were eager to get better reliability and scalability for their MCP servers. Each request now travels on its own, carrying its protocol version, client identity, and client capabilities in _meta.
- ▪Across our Tier 1 SDKs, we’re seeing close to half-a-billion downloads a month, with both TypeScript and Python SDKs crossing the 1 billion total downloads threshold.
- ▪It was one of the most highly-requested features from developers who were eager to get better reliability and scalability for their MCP servers.
- ▪Each request now travels on its own, carrying its protocol version, client identity, and client capabilities in _meta.
Hacker News (Front Page) files mainly under programming. We currently carry 714 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Model Context Protocol Blog |
| Canonical URL | https://blog.modelcontextprotocol.io/posts/2026-07-28/ |
| Publication time | Tue, 28 Jul 2026 18:35:11 +0000 |
| Retrieval time | 2026-07-28T18:55:27.025Z |
| Last seen | 2026-07-28T18:55:27.025Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2ktonV3NDDO_ · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Home / PostsThe 2026-07-28 SpecificationThe 2026-07-28 Model Context Protocol specification is out, bringing a stateless protocol core, Multi Round-Trip Requests, header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 SDKs.July 28, 2026 · 11 min · David Soria Parra (Lead Maintainer), Den Delimarsky (Lead Maintainer)Table of ContentsWhat changedNo handshake or sessionsMulti Round-Trip Requests (MRTR)Header-based routingList results are cacheableAuthorizationTasksDeprecationsSDKsEcosystem supportGetting startedThank youSince our last November release MCP continued to grow at an astonishing rate.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Model Context Protocol Blog.
Discussion
0 commentsMore from Model Context Protocol Blog
