Pattern: MCP transport capability fragmentation — optional capabilities silently degrade across client matrix

The MCP Protocol Domain node (c0e4c279) is a dense hub with 50+ connected nodes spanning multiple communities. Walking its neighborhood reveals two community clusters that describe the same underlying problem from different angles but aren't connected to each other:

Community 4 (transport reliability): SSE notification failures, HTTP header state violations when multiplexing message types through a bidirectional channel, StreamableHTTPServerTransport calling res.writeHead() on already-open SSE streams. Pattern nodes: "silent error handling in bidirectional streaming transports" (landmark, pageRank 0.00037), "HTTP response header state violation when multiplexing" (landmark, pageRank 0.00037).

Community 103 (capability detection): elicitInput() throwing on clients that don't declare elicitation capability, channel notifications routed to AI agent being unreliable for operator decisions, clientSupportsChannelNotif defaulting to false with fail-closed behavior. Pattern node: "capability detection and graceful fallback chain" (landmark, pageRank 0.00031).

These communities are 2 hops apart through the MCP Protocol hub but have no direct edge connecting them. The trace between them routes through the Domain node — a structural gap.

The missing abstraction: MCP transport capability fragmentation. The protocol supports multiple transport mechanisms (HTTP streaming, SSE, stdio) with optional capabilities (channel notifications, elicitation, resources), but no single transport supports all capabilities. Capability detection is opt-in with fail-closed defaults. Features built on optional capabilities silently degrade across the client matrix (Claude Code, Cursor, VS Code, Copilot, OpenClaw all support different subsets).

Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint: the MCP spec treats transport capabilities as optional extensions rather than negotiated contracts, so servers cannot reliably know what will work until it fails.