{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-an-mcp-http-native-sse-stream-as-a-non-resumable-per-request-event-channel-rather-than-a-durable-subscription",
  "title": "In what scenarios must an instance treat an MCP HTTP-native SSE stream as a non-resumable, per-request event channel rather than a durable subscription",
  "date_of_record": "2026 November 17",
  "scope": "Applies to MCP servers and clients using the HTTP-native transport with Server-Sent Events (`text/event-stream`) for agent tool invocation, where the stream is opened per request and correlated by a request-scoped identifier. Does not apply to full-duplex transports (e.g., stdio or a WebSocket-based binding), nor to long-lived SSE subscriptions explicitly negotiated as durable, resumable channels.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-an-mcp-http-native-sse-stream-as-a-non-resumable-per-request-event-channel-rather-than-a-durable-subscription.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-an-mcp-http-native-sse-stream-as-a-non-resumable-per-request-event-channel-rather-than-a-durable-subscription.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-an-mcp-http-native-sse-stream-as-a-non-resumable-per-request-event-channel-rather-than-a-durable-subscription.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1374,
    "python_slice_tokens": 222,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary that matters is between *stream identity* and *request identity*. In the HTTP-native MCP transport, an SSE stream is a transport-level framing for the response to one JSON-RPC request (or a batch), not a session-level subscription. The stream carries the reply, progress notifications, and any server-initiated messages correlated to that request,...",
    "what_was_observed": "A tool-invocation client opened an SSE stream for a `tools/call` request. The server emitted a progress notification, then the proxy between client and server terminated the idle connection at 60 seconds (the tool was still executing server-side). The client, using a generic SSE library with `Last-Event-ID` replay enabled, reconnected with the last event ID it had seen. The server, which had already settled the reque...",
    "condition_of_validity": "The \"non-resumable, per-request\" model holds when all of the following are true: 1. The stream was opened by a specific JSON-RPC request and is correlated to that request's `id` (or a request-scoped token). 2. The server does not guarantee event retention across connection lifetimes for that stream. 3. The transport contract (as implemented by the MCP HTTP-n...",
    "decision_boundary": "The decision point is reached on any mid-stream disconnect (connection reset, proxy timeout, client abort, or server-side stream close without a terminal JSON-RPC message). At that point the client must choose between: - **Re-issue the JSON-RPC request** (correct for the per-request model), accepting that the operation may be non-idempotent and must be guard...",
    "operational_effect": "Operationally, this means the client's reconnect logic must be request-aware, not stream-aware. The SSE layer should expose \"stream ended without terminal message\" as an error to the request layer, which then decides: re-issue (with idempotency guard) or fail the tool invocation. The stream layer must not silently reconnect. Servers must close the stream wit..."
  },
  "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": "44e0442ca656bd1da7f95bce29b50451cf46c75820bd6d4107380ca022643c95",
    "verified_classes": [
      "StreamResumptionViolation",
      "RequestScopedStream"
    ],
    "verified_functions": [
      "__init__",
      "on_event",
      "on_disconnect",
      "resume"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "StreamResumptionViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
