You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients can now subscribe to specific resources and receive targeted
notifications when those resources change. Previously, calling
`notifyResourceUpdated` on the server would broadcast the notification
to every connected client regardless of interest — now only sessions
that have explicitly subscribed to a given resource URI receive the
update, making resource change propagation both correct and efficient.
The subscription lifecycle is fully handled: clients can subscribe and
unsubscribe at any time, and the server cleans up subscription state
when a session closes.
Supersedes #838.
Resolves#837, #776.
---------
Signed-off-by: Dariusz Jędrzejczyk <dariusz.jedrzejczyk@broadcom.com>
-**Security (2/2):** Localhost validation passes, DNS rebinding protection
20
20
21
-
### Failing (3/40)
22
-
23
-
1.**resources-subscribe** - Not implemented in SDK
24
-
2.**resources-unsubscribe** - Not implemented in SDK
25
-
26
21
## Client Test Results
27
22
28
23
### Passing (3/4 scenarios, 9/10 checks)
@@ -68,10 +63,9 @@ Uses the `client-spring-http-client` module with Spring Security OAuth2 and the
68
63
69
64
## Known Limitations
70
65
71
-
1.**Resource Subscriptions:** SDK doesn't implement `resources/subscribe` and `resources/unsubscribe` handlers
72
-
2.**Client SSE Retry:** Client doesn't parse or respect the `retry:` field, reconnects immediately, and doesn't send Last-Event-ID header
73
-
3.**Auth Scope Step-Up:** Client does not fully handle scope step-up challenges where the server requests additional scopes after initial authorization
74
-
4.**Auth Basic CIMD:** Minor conformance warning in the basic Client-Initiated Metadata Discovery flow
66
+
1.**Client SSE Retry:** Client doesn't parse or respect the `retry:` field, reconnects immediately, and doesn't send Last-Event-ID header
67
+
2.**Auth Scope Step-Up:** Client does not fully handle scope step-up challenges where the server requests additional scopes after initial authorization
68
+
3.**Auth Basic CIMD:** Minor conformance warning in the basic Client-Initiated Metadata Discovery flow
Copy file name to clipboardExpand all lines: conformance-tests/server-servlet/README.md
+4-10Lines changed: 4 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This module contains a comprehensive MCP (Model Context Protocol) server impleme
4
4
5
5
## Conformance Test Results
6
6
7
-
**Status: 37 out of 40 tests passing (92.5%)**
7
+
**Status: 40 out of 40 tests passing (100%)**
8
8
9
9
The server has been validated against the official [MCP conformance test suite](https://github.com/modelcontextprotocol/conformance). See [VALIDATION_RESULTS.md](../VALIDATION_RESULTS.md) for detailed results.
10
10
@@ -22,9 +22,8 @@ The server has been validated against the official [MCP conformance test suite](
22
22
- SEP-1034: Default values for all primitive types
Copy file name to clipboardExpand all lines: mcp-core/src/main/java/io/modelcontextprotocol/server/transport/HttpServletSseServerTransportProvider.java
Copy file name to clipboardExpand all lines: mcp-core/src/main/java/io/modelcontextprotocol/server/transport/HttpServletStreamableServerTransportProvider.java
0 commit comments