build(deps): bump ModelContextProtocol 1.3.0 -> 1.4.0 - #30
Merged
Conversation
Picks up security hardening from the upstream SDK: - Stdio transport no longer enumerates child-process env vars in Trace logs. - Streamable HTTP DELETE on a session now validates the authenticated user matches the session owner (mirrors the existing GET/POST check, returns 403 instead of terminating the session on a leaked Mcp-Session-Id). Directly hardens MaestroTool.Mcp (MapMcp()). Also adds the IdentityAssertionGrantProvider (ID-JAG / SEP-990) for future enterprise SSO scenarios, and an InheritEnvironmentVariables option on StdioClientTransportOptions (not used by this server). No API surface changes; we only consume [McpServerToolType] / [McpServerTool] attributes, WithStdioServerTransport(), and MapMcp() — all source-compatible across 1.3.0 -> 1.4.0. Validation: solution builds with 0 warnings, all 208 tests pass. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
ModelContextProtocolandModelContextProtocol.AspNetCorefrom1.3.0to1.4.0(released 2026-06-04). Picks up two security-hardening fixes that directly apply to this server.Why bump
🔐 Security hardening (auto-benefit)
WithStdioServerTransport()inMaestroTool/Program.csDELETEon a session now validates the authenticated user matches the session owner (#1604) — mirrors the existing GET/POST check; returns403instead of terminating the session on a leakedMcp-Session-IdMaestroTool.Mcp/Program.cscallsMapMcp()🏢 New features (available, not adopted in this PR)
IdentityAssertionGrantProvider(ID-JAG / SEP-990) — RFC 8693 + RFC 7523 token exchange for enterprise SSO. Useful later if we add managed auth.InheritEnvironmentVariablesonStdioClientTransportOptions— client-side, not consumed here.API surface check
We only use:
[McpServerToolType]/[McpServerTool]attributes (tool declarations acrossMaestroMcpTools/*)WithStdioServerTransport()(CLI)MapMcp()(AspNetCore Streamable HTTP)All source-compatible across 1.3.0 → 1.4.0.
Changes
MaestroTool.CoreModelContextProtocol 1.3.01.4.0MaestroTool.McpModelContextProtocol.AspNetCore 1.3.01.4.0MaestroToolModelContextProtocol 1.3.01.4.0Validation