[Snyk] Fix for 2 vulnerabilities

[sestinj]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• core/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-JS-HANDLEBARS-20574183	858
	Insufficiently Protected Credentials SNYK-JS-MODELCONTEXTPROTOCOLSDK-20579853	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Access of Resource Using Incompatible Type ('Type Confusion')

[sestinj]

This update includes a medium-risk change for @modelcontextprotocol/sdk and a low-risk security update for handlebars.

@modelcontextprotocol/sdk 1.29.0 → 1.31.0 (Medium Risk)

This minor version upgrade introduces a significant behavioral change in how servers handle connections. As of version 1.31.0, a McpServer or Server object is designed to serve only one connection at a time. Similarly, a stateless Streamable HTTP transport (where sessionIdGenerator is undefined) will only handle a single request.

Action required: Applications that reuse a single server object or a stateless transport for multiple HTTP requests will fail after the second request. The code must be updated to create a new server and transport for each incoming request.

handlebars 4.7.9 → 4.7.10 (Low Risk)

This is a patch release that addresses two critical remote code execution (RCE) vulnerabilities (CVE-2026-106445, CVE-2026-106446). There are no documented breaking API changes for standard usage. The fixes target unintended use-cases related to prototype access and are not expected to impact applications following documented practices.

Source: Release notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.