WeSearch

Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)

Simon Willison· ·5 min read · 0 reactions · 0 comments · 4 views
#ai#protocols#software#open-source#Anthropic#Model Context Protocol#Ade Oshineye#agentic-mermaid.dev#mcp-explorer
Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)
TL;DR · WeSearch summary

The Model Context Protocol (MCP) released a new stateless specification on July 28, 2026, simplifying client‑server interactions to a single HTTP request. The author built three implementations and created the mcp‑explorer CLI tool to probe MCP servers without installation. The stateless design reduces complexity and improves scalability compared to the earlier stateful version.

Key facts
About this source

Simon Willison files mainly under blogs. We currently carry 52 of its stories.

Original article
Simon Willison's Weblog · Simon Willison
Read full at Simon Willison's Weblog →

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 publisherSimon Willison's Weblog
Canonical URLhttps://simonwillison.net/2026/Jul/31/stateless-mcp/#atom-everything
Publication time2026-07-31T23:13:22+00:00
Retrieval time2026-07-31T23:25:51.417Z
Last seen2026-07-31T23:25:51.417Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterFijO30tE1zkn · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp) 31st July 2026 Tuesday was Stateless MCP day—the rollout of MCP 2.0, or the 2026-07-28 Model Context Protocol specification to use the more formal but less memorable name. This is the most significant change to the MCP spec since it first launched, and has also served to reignite my personal interest in the protocol. For background: MCP is the Model Context Protocol, which describes a standard way to expose new tools to LLM-powered agent frameworks.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Simon Willison's Weblog.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments