{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-mcp-http-native-transport-has-silently-degraded-to-sse-fallback-with-lost-session-resumption-state",
  "title": "What structural signals indicate that MCP HTTP-native transport has silently degraded to SSE fallback with lost session resumption state",
  "date_of_record": "2026 November 14",
  "scope": "Applies to Model Context Protocol servers exposing the HTTP-native transport (POST request/response) with streamable SSE as a fallback, where session resumption is keyed on `Mcp-Session-Id` and `Last-Event-ID`. Does not apply to pure stdio transports or to stateless tool endpoints that carry no session identifier.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-mcp-http-native-transport-has-silently-degraded-to-sse-fallback-with-lost-session-resumption-state.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-mcp-http-native-transport-has-silently-degraded-to-sse-fallback-with-lost-session-resumption-state.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-mcp-http-native-transport-has-silently-degraded-to-sse-fallback-with-lost-session-resumption-state.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1320,
    "python_slice_tokens": 175,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a difference between a server that *supports* SSE fallback and a server that is *currently operating* in SSE fallback because the HTTP-native path failed. The protocol permits both. The client, however, frequently cannot tell which mode it is in, because both modes return HTTP 200 and both eventually produce a valid JSON-RPC result. The boundary fai...",
    "what_was_observed": "Three structural signals appeared in sequence, none of which raised an error: 1. **Response framing shift.** The first N responses to `tools/call` arrived as `Content-Type: application/json` with a complete body. Subsequent responses arrived as `Content-Type: text/event-stream` carrying a single `event: message` frame with no following `data:` heartbeat. The status code remained 200 throughout. The client's transport...",
    "condition_of_validity": "The silent-downgrade diagnosis is valid only when all of the following hold: - The client observed at least one prior HTTP-native (application/json) response under the same `Mcp-Session-Id`. - The content-type transition occurred without an intervening `Mcp-Session-Id` rotation and without a 4xx/5xx. - The SSE stream carried no `id:` fields, or carried IDs t...",
    "decision_boundary": "The operational rule: **treat a mid-session content-type transition to `text/event-stream` without monotonic event IDs as a resumption-state loss, and force session renegotiation rather than attempting `Last-Event-ID` recovery.** Do not retry the native request hoping to \"get back\" to native mode within the same session — the server has already committed its...",
    "operational_effect": "When the boundary is respected, the observable cost is one extra negotiation round-trip per downgrade event, plus a re-fetch of tool listings. When it is violated, the failure is deferred and multiplicative: duplicate notifications inflate the agent's context, stale tool schemas cause calls against removed tools, and the replay-from-start behavior on each re..."
  },
  "matched_failure_symptoms": [
    "HTTP_502_503_504_CASCADE"
  ],
  "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": "f0d19779733d266280f7cd00f4cc8b94d7324c0cc4869b102c523f4be94e9eb1",
    "verified_classes": [
      "SilentFallbackResumptionError"
    ],
    "verified_functions": [
      "classify_transport_transition",
      "resume_or_renegotiate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SilentFallbackResumptionError"
    ],
    "sample_fail_closed_invariants": [
      "fallback stream claims resumable IDs but client holds no cursor; refusing to resume without a defined Last-Event-ID."
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}