MCP is going stateless: What the new spec means for AI agents
The Model Context Protocol has had a fast eighteen months. The client sends initialize, the server mints an mcp-session-id, and that ID is expected on every subsequent request. For single-instance deployments, this is fine.
- ▪The Model Context Protocol has had a fast eighteen months.
- ▪The client sends initialize, the server mints an mcp-session-id, and that ID is expected on every subsequent request.
- ▪For single-instance deployments, this is fine.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,110 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 | New Relic |
| Canonical URL | https://newrelic.com/blog/ai/mcp-is-going-stateless |
| Publication time | Fri, 31 Jul 2026 19:29:30 +0000 |
| Retrieval time | 2026-07-31T19:49:57.489Z |
| Last seen | 2026-07-31T19:49:57.489Z |
| 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 | pvc0rmoe8FV7 · 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
The Model Context Protocol has had a fast eighteen months. Since Anthropic open-sourced it in late 2024, it has gone from a spec nobody had heard of to the most widely adopted protocol for connecting AI agents to external tools, APIs, and data sources, with over 150 organizations building on it and native support across three major cloud platforms.On July 28, the MCP project releases the most significant revision to the MCP specification since launch, and the headline change is one that teams running MCP in production have been waiting for: MCP is going stateless.If you are building agents that connect through MCP clients, building MCP servers, or both, here is what changes, why the old model was a headache in production, and what MCP replacing its proprietary logging channel with…
Excerpt limited to ~120 words for fair-use compliance. The full article is at New Relic.
Discussion
0 commentsMore from New Relic
