fix(deps): bump MCP SDK 1.27.1 → 1.29.0 to clear pre-existing npm audit failure

[Nathan Schram (nathanschram)]

Summary

Unblocks the Security Audit CI check, which has been failing on main for a while with 6 vulnerabilities — 5 moderate + 1 HIGH — all transitive through @modelcontextprotocol/sdk@1.27.1. This was caught when running CI on the community contribution batch (#173/#174/#175): all three PRs inherited the pre-existing failure because they branched off main.

Vulns cleared

Package	From	To	Severity
fast-uri	3.1.0	3.1.2	HIGH (path traversal, host confusion)
hono	4.12.7	4.12.23	moderate (10 advisories)
@hono/node-server	1.19.11	1.19.14	moderate
express-rate-limit	8.3.0	8.5.2	(transitive ip-address bump)
ip-address	10.1.0	10.2.0	moderate (XSS)
qs	6.15.0	6.15.2	moderate (DoS)

Approach

Single direct change: bump @modelcontextprotocol/sdk from ^1.27.1 to ^1.29.0. SDK 1.29.0's release notes specifically include "v1.x npm audit fix" (#1780) — exactly the cleanup we need. The other 5 transitive bumps follow automatically via npm's audit fix.

Risk assessment

SDK 1.28.0 introduced one behaviour change worth flagging: fix: reject plain JSON Schema objects passed as inputSchema (#1596). All 708 jest tests pass against the new SDK, so none of our 22 tool registrations are affected — we already use proper inputSchema shapes per the MCP spec.

Verification

• ✅ npm audit --omit=dev --audit-level=high → 0 vulnerabilities
• ✅ npm test → 708/708 passing
• ✅ npm run lint → 0 errors (24 pre-existing warnings unchanged)

Test plan

• CI runs green (especially Security Audit)
• After merge, re-trigger CI on PRs feat(calendar): add update action to manage-event #173/feat(auth): configurable OAuth audience via OUTLOOK_AUTH_AUDIENCE #174/feat(config): make DEFAULT_TIMEZONE overridable via env var #175 (rebase against this main) — they should now pass

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@nathanschram, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 52 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b8e49a77-bf97-4802-af75-df972d997f01

📥 Commits

Reviewing files that changed from the base of the PR and between d7cf229 and 861f1d8.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/dep-audit-cleanup

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}