René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"2026-07-28 spec support — tracking","articleBody":"Umbrella for the 2026-07-28 release work. Bar: the conformance suite passes with no expected-failures waivers attributable to this release (the [SEP-990](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/990) enterprise-auth waiver is unrelated and remains). Each sub-issue lists the scenarios it's responsible for; design is owned by whoever takes the issue.\n\nThis sits alongside the broader v2.0 SDK rework tracked in #1253 — that umbrella covers SDK-ergonomics breaking changes; this one covers spec compliance for the 2026-07-28 protocol revision.\n\n## What's in it\n\n- Sub-issues:\n  - #2892\n  - #2893\n  - #2894\n  - #2895\n  - #2896\n  - #2897\n  - #2898\n  - #2899\n  - #2900\n  - #2901\n  - #2902\n  - #2903\n  - #2904\n  - #2905\n- **Architecture (direction, not law):** lowlevel `Server` = protocol interface, minimal state, no magic. The 2026 features ship as **public helpers/classes** usable directly against lowlevel `Server`. `MCPServer` is a **thin composition** of those same public helpers — a pre-built convenience, not a monolith with private machinery.\n- **Capability checkpoints** (shared targets, not tickets):\n  - **M1** — a modern client makes a stateless `tools/call` against a modern server over HTTP, no initialize (minimum slice of _Backwards compatibility \u0026 version negotiation_ + _New HTTP serving path (modern + dual-era)_ + _New Client (all-versions, low-level + high-level)_)\n  - **M2** — the `server-stateless` conformance scenario passes end-to-end (_Backwards compatibility \u0026 version negotiation_ + _New HTTP serving path (modern + dual-era)_ + _Context object (layered, per-request)_ + _Capabilities API + server/discover handler_ + _subscriptions/listen_ all in)\n  - **M3** — all release-attributable waivers gone\n- **Landing model:** PRs land to `main`. 2026-07-28 stays modeled-but-not-negotiable until the version-negotiation work flips it on, so partial work doesn't change behaviour for existing users.\n- Standing maintenance (not a sub-issue): when bumping the conformance pin, reconcile `expected-failures.yml` in the same PR; when in-flight spec PRs merge, re-vendor `schema/2026-07-28.json` + regenerate.\n- Stretch (optional): contribute missing scenarios upstream — discover caching-hints check, dedicated `subscriptions/listen` server scenario, client-direction sessionless scenario.\n\n## Conformance\n\n- (all release-attributable waivers removed across the sub-issues)\n\n## Dependencies\n\n- Depends on: none\n\n## References\n\n- [Draft changelog](https://modelcontextprotocol.io/specification/draft/changelog)\n- [Draft schema](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/schema/draft/schema.ts)\n- [Conformance suite](https://github.com/modelcontextprotocol/conformance)\n- [python-sdk expected-failures](https://github.com/modelcontextprotocol/python-sdk/blob/main/.github/actions/conformance/expected-failures.yml)\n","author":{"url":"https://github.com/maxisbey","@type":"Person","name":"maxisbey"},"datePublished":"2026-06-17T11:11:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2891/python-sdk/issues/2891"}