{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-resumable-mcp-stream-has-silently-lost-its-per-tool-oauth-resource-binding",
  "title": "What structural signals indicate a resumable MCP stream has silently lost its per-tool OAuth resource binding",
  "date_of_record": "2026 November 15",
  "scope": "Applies to MCP servers exposing the HTTP-native transport (Streamable HTTP / SSE with `Last-Event-ID` resumption) where individual tools are gated by OAuth 2.1 resource indicators (RFC 8707) scoped per-tool. Does not apply to stdio transports, nor to deployments where a single audience-scoped bearer token authorizes all tools.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-resumable-mcp-stream-has-silently-lost-its-per-tool-oauth-resource-binding.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-resumable-mcp-stream-has-silently-lost-its-per-tool-oauth-resource-binding.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-resumable-mcp-stream-has-silently-lost-its-per-tool-oauth-resource-binding.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1331,
    "python_slice_tokens": 201,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A resumable stream and an authorized stream are two independent lifecycles that the MCP HTTP transport couples only implicitly. The stream lifecycle is keyed by a session identifier plus a monotonic event ID; the authorization lifecycle is keyed by the `resource` parameter that was asserted at token issuance and re-checked at each tool invocation. When a cli...",
    "what_was_observed": "During a long-lived session (observed across a 40-minute idle window exceeding the edge proxy's 30-second keepalive but within the server's 15-minute session TTL), the client reconnected with a valid `Last-Event-ID`. The server returned HTTP 200 and replayed buffered events from the correct offset. The client then issued a `tools/call` for a tool whose OAuth resource indicator was `https://api.example.com/tools/billi...",
    "condition_of_validity": "This diagnosis is valid only when all of the following hold: - The transport is HTTP-native with `Last-Event-ID` resumption enabled. - Per-tool OAuth resource indicators are enforced at the tool-invocation layer, not at the transport layer. - A token refresh occurred between session creation and resumption (typically triggered by the client's token TTL being...",
    "decision_boundary": "The operator must decide whether a resumed stream should inherit the resource bindings of its original session or whether each tool call must re-assert its resource indicator independently. The safe default is the latter: **treat every `tools/call` on a resumed stream as requiring fresh resource-indicator validation, and never infer tool authorization from s...",
    "operational_effect": "Clients that treat `200 OK` on resume as full session restoration will issue tool calls that fail with audience-mismatch errors that look like server bugs rather than auth drift. The remediation is to make the resource indicator explicit on every refresh request (never rely on the authorization server default), and to have the client compare `token.iat` agai..."
  },
  "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": "106f98df3a09979222c91295ce443749993a06a820de8c02a4826688a6a644ac",
    "verified_classes": [
      "ResourceBindingDriftError",
      "Session",
      "Token"
    ],
    "verified_functions": [
      "assert_tool_resource_valid"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ResourceBindingDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
