subjectId
attribute
connectionLifecycle
value
Two-endpoint design (legacy):
1. Client opens GET on the SSE endpoint; server responds with an
`endpoint` SSE event whose `data:` is the URL the client must
POST JSON-RPC requests to (typically a per-session URL).
2. Client POSTs `initialize` to the announced endpoint; response
is delivered asynchronously as an SSE `message` event on the
open GET stream.
3. Client POSTs `notifications/initialized`. Session is ready.
4. Shutdown is by closing the SSE GET; no explicit DELETE.
subjectKind
MCPTransport
statement
mcp-transport:http-sse connectionLifecycle is Two-endpoint design (legacy):
1. Client opens GET on the SSE endpoint; server responds with an
`endpoint` SSE event whose `data:` is the URL the client must
POST JSON-RPC requests to (typically a per-session URL).
2. Client POSTs `initialize` to the announced endpoint; response
is delivered asynchronously as an SSE `message` event on the
open GET stream.
3. Client POSTs `notifications/initialized`. Session is ready.
4. Shutdown is by closing the SSE GET; no explicit DELETE.
.
confidence
medium
provenanceKind
observation
evidenceStrength
moderate
status
accepted
evidenceSourceIds
claimedAt
2026-05-04T00:00:00Z
claimedBy
a5c-ai-catalog
claimKind
assertion
note
Evidence binding for MCPTransport attributes.