Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
A new release is waiting v2.1.309 npm has it, but its platform binary is not downloadable yet
HomeDocsModel Context Protocol 20 Aug 2026
One change · mcp

Subscriptions changedspecification/2026-07-28/basic/patterns/subscriptions

Nearest release: v2.1.238, published 5 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+7added
Lines−6removed
From line 117 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits4to this page, all time

The whole hunk

from line 117, old and new numbered
/
lines
from line 117
117117 
118118* The **client** cancels it — close the SSE stream (HTTP) or send
119119 `notifications/cancelled` referencing the `subscriptions/listen` request ID (stdio).
120* The **server** tears it down (e.g., during shutdown) — it **SHOULD** send the
121 empty `subscriptions/listen` response to signal a graceful end (see
120* The **server** tears it down (e.g., during shutdown) — it **SHOULD** send a
121 successful `subscriptions/listen` response to signal a graceful end (see
122122 [Graceful Closure](#graceful-closure)), then close the stream.
123123* The underlying transport closes (HTTP timeout, TCP disconnect, stdio process
124124 exit).
from line 127
127127 
128128When the server ends a subscription on its own initiative (for example, during
129129shutdown), it **SHOULD** respond to the original `subscriptions/listen` request
130with an empty result before closing the stream. This is the JSON-RPC response to
131the long-lived request, correlated by its `id`, and signals that the subscription
132ended gracefully — as opposed to an abrupt transport drop, which carries no
133response.
130with a completion result before closing the stream. The result carries no
131method-specific data beyond the standard result fields and subscription
132metadata. This is the JSON-RPC response to the long-lived request, correlated by
133its `id`, and signals that the subscription ended gracefully — as opposed to an
134abrupt transport drop, which carries no response.
134135 
135136```json theme={null}
136137{
Feedback