{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-resumed-mcp-sse-stream-when-oauth-2-1-resource-indicators-change-mid-session",
  "title": "Under what conditions must an instance reject a resumed MCP SSE stream when OAuth 2.1 resource indicators change mid-session",
  "date_of_record": "2026 November 14",
  "scope": "Applies to MCP servers exposing HTTP-native transport (POST + `text/event-stream`) with `Last-Event-ID` resumability and per-tool OAuth 2.1 resource indicators (RFC 8707). Does not apply to stdio transports, to servers that bind a single resource indicator for the whole session, or to streams that have never been interrupted (no `Last-Event-ID` presented).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-resumed-mcp-sse-stream-when-oauth-2-1-resource-indicators-change-mid-session.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-resumed-mcp-sse-stream-when-oauth-2-1-resource-indicators-change-mid-session.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-resumed-mcp-sse-stream-when-oauth-2-1-resource-indicators-change-mid-session.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1493,
    "python_slice_tokens": 210,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A resumed SSE stream is not a continuation of the *request*; it is a continuation of the *authorization context* under which the original event sequence was produced. The `Last-Event-ID` token is an opaque pointer into server-side replay state, and that replay state was materialized under a specific access token, a specific `resource` indicator, and a specif...",
    "what_was_observed": "During a multi-tool session, a client held a stream open against `resource=https://mcp.example.com/tools/search`. A mid-stream tool call to `resource=https://mcp.example.com/tools/fetch` required a step-up authorization (broader scope, distinct resource indicator). The client performed the OAuth 2.1 exchange, obtained a new access token bound to the `fetch` resource, and — because the transport layer reconnects trans...",
    "condition_of_validity": "The resume is only valid when all of the following hold for the `Last-Event-ID` being presented: 1. The `resource` claim in the presented token equals the resource indicator under which the event sequence was originally minted (stored as stream metadata at event creation time). 2. The scope set of the presented token is a superset of the scope set recorded o...",
    "decision_boundary": "The boundary is between two superficially identical HTTP requests: - **Reconnection:** same principal, same `resource`, same-or-broader scope, valid event ID → replay and continue. - **Reauthorization:** same principal, *different* `resource` or *narrower* scope, valid event ID → refuse replay, return `409 Conflict` (or `403` with a `WWW-Authenticate` challe...",
    "operational_effect": "When the boundary is enforced correctly, the client observes a `409` on resume and must re-issue the original MCP request under the new token. This costs a full round-trip and re-execution of the tool call, but it preserves the invariant that every byte delivered on a stream was authorized under the resource indicator stamped on that stream's replay log. Whe..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "b3beecb4a07a167f7e4208eb59f4d21bec722466df3152aaa419086e41b3c745",
    "verified_classes": [
      "StreamResumeAuthorizationError",
      "StreamProvenance",
      "PresentedToken"
    ],
    "verified_functions": [
      "validate_resume"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "StreamResumeAuthorizationError"
    ],
    "sample_fail_closed_invariants": [
      "principal mismatch on resume; treating as new stream",
      "client_id mismatch on resume; treating as new stream"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
