[dependabot]

Bumps @modelcontextprotocol/sdk from 1.31.0 to 1.32.0.

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

1.32.0

Upgrade notes

• Redirects: the HTTP client transports now follow a redirect only when it stays on the same origin (same scheme, host and port; http to https on the same host is allowed). A deployment whose endpoint redirects to another host or port either configures the final URL or sets redirectPolicy: 'follow' on StreamableHTTPClientTransport or SSEClientTransport. In browsers, a redirected request fails unless that option is set.
• New options, both off unless you set them: maxToolInputElements on McpServer limits the number of array elements and object members in a tool call's arguments. expectedResource on requireBearerAuth accepts only tokens issued for this server (the token's audience).

What's Changed

• [v1.x] fix(client): follow redirects only within the endpoint's origin by @​claude[bot] in modelcontextprotocol/typescript-sdk#2902
• docs: point SECURITY.md at GitHub Security Advisories (v1.x) by @​claude[bot] in modelcontextprotocol/typescript-sdk#2910
• [v1.x] examples: close idle sessions and cap the session map by @​maxisbey in modelcontextprotocol/typescript-sdk#2914
• [v1.x] fix(tasks): keep tasks of the in-memory task store within the session that created them by @​claude[bot] in modelcontextprotocol/typescript-sdk#2925
• [v1.x] feat(server): add maxToolInputElements option to limit the number of elements in tool-call arguments by @​claude[bot] in modelcontextprotocol/typescript-sdk#2927
• [v1.x] fix(server): accept tools/call and prompts/get requests that omit arguments by @​raashish1601 in modelcontextprotocol/typescript-sdk#2045
• [v1.x] feat(auth): add expectedResource to requireBearerAuth by @​claude[bot] in modelcontextprotocol/typescript-sdk#2930
• [v1.x] test(e2e): cover tools/call and prompts/get without arguments by @​claude[bot] in modelcontextprotocol/typescript-sdk#2931
• chore: bump version to 1.32.0 by @​claude[bot] in modelcontextprotocol/typescript-sdk#2935

New Contributors

• @​raashish1601 made their first contribution in modelcontextprotocol/typescript-sdk#2045

Full Changelog: modelcontextprotocol/typescript-sdk@1.31.0...1.32.0

Commits

• 32549b0 chore: bump version to 1.32.0 (#2935)
• 588d51d [v1.x] test(e2e): cover tools/call and prompts/get without arguments (#2931)
• 5a0724d [v1.x] feat(auth): add expectedResource to requireBearerAuth (#2930)
• 0ca0b62 [v1.x] fix(server): accept tools/call and prompts/get requests that omit argu...
• fd26801 [v1.x] feat(server): add maxToolInputElements option to limit the number of e...
• 727075b [v1.x] fix(tasks): keep tasks of the in-memory task store within the session ...
• 0ff6377 [v1.x] examples: close idle sessions and cap the session map (#2914)
• c2ce003 docs: point SECURITY.md at GitHub Security Advisories (v1.x) (#2910)
• 30bfe51 [v1.x] fix(client): follow redirects only within the endpoint's origin (#2902)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[maxigimenez]

Security triage — Tier B, ready for a human, does not auto-merge

What and why

@modelcontextprotocol/sdk 1.31.0 → 1.32.0 (high; direct dependencies entry of @currents/mcp, not transitive).

Vanta tracks this as alert 173, CVE-2026-111767 / GHSA-22jm-h49p-29qw, CVSS 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), remediateByDate 2026-11-21 — 30 days out.

The advisory's own summary:

Clients sharing one InMemoryTaskStore could list, read and cancel each other's tasks.

One bump closes four advisories, not one. npm audit on this branch confirms all four are gone:

advisory	severity	CVSS	affected
GHSA-22jm-h49p-29qw	high	8.6	>= 1.24.0 < 1.32.0
GHSA-46jr-4wx8-v453	high	7.5	>= 1.3.0 < 1.32.0
GHSA-rvq5-wwqv-78pq	moderate	6.8	>= 1.6.0 < 1.32.0
GHSA-6prh-2h8m-c8cw	moderate	6.5	< 1.32.0

Only the first has a Vanta record and therefore an SLA clock; the other three ride along.

Exposure

Runtime, and it ships. @currents/mcp is published to npm (files: [dist, assets, README.md], bin: mcp and currents-mcp-http), and the SDK resolves outside devDependencies:

$ npm ls @modelcontextprotocol/sdk --omit=dev
@currents/mcp@2.7.0 /home/user/currents-mcp/mcp-server
`-- @modelcontextprotocol/sdk@1.32.0

Two of the four advisories are worth reading in that light rather than as generic dependency noise: GHSA-rvq5-wwqv-78pq is server bearer auth accepting tokens issued for another service, and GHSA-22jm-h49p-29qw is cross-session task access. Both land on the HTTP server path (currents-mcp-http), not the stdio binary.

The fix

lockfile-upgrade. package.json already declares "@modelcontextprotocol/sdk": "^1.29.0", which semver-satisfies 1.32.0, so no manifest edit is needed and none was made. The diff is three lines in one lockfile stanza — version, resolved, integrity — and nothing else.

Breaking-change check

1.32.0 is a minor within the same major. Its dependency block is unchanged apart from @hono/node-server widening to ^1.19.9 || ^2.0.5, which is a widening, not a move. No breaking-change section and no removals in the release. No patches/ directory and no postinstall in this repo, so the patch-package trap does not apply.

Verification — run on this head (2072462)

command	result
npm ci	clean, 0 peer warnings
git diff --name-only origin/main...HEAD	mcp-server/package-lock.json — nothing else
npm run build	pass (9 files, 276.34 kB)
npm run test:run	35/35 files, 1198/1198 tests pass
npm run format	"All matched files use Prettier code style!"

CI coverage

.github/workflows/test.yml has no paths: filter, so it runs on every PR to main — this dependency-only diff triggers it rather than silently skipping. All three jobs green on 2072462: Test (Node 20.x), (22.x), (24.x).

Not triggered, and not expected to be: publish.yaml, release.yaml, promote.yaml, post-release.yaml, sync-from-monorepo.yaml, linear-release.yaml — all release-time workflows.

Why Tier B rather than Tier A

Mechanically this is as narrow as a fix gets: one stanza, patch-level transitively, no manifest edit, no peer warnings, CI green. It is Tier B on one criterion only — a direct dependencies entry of something that ships. That rules out auto-merge regardless of how small the diff is, so it is left open for you.

Needs release

⚠️ The fix reaches users only when @currents/mcp is published. Merging this closes the Dependabot alert and the Vanta finding, but anyone who has installed @currents/mcp keeps the vulnerable SDK until a release goes out.

• package: @currents/mcp, currently 2.7.0
• No release has been cut from this branch, and this routine does not publish.

What a human should still check

1. Whether to cut a release, and when — the SLA date is 2026-11-21, so a release before then is what actually closes the exposure for installed clients.
2. The bearer-token advisory (GHSA-rvq5-wwqv-78pq) against how currents-mcp-http is deployed — whether any audience validation was being relied on at the SDK layer.

---

Generated by Claude Code