chore(deps)(deps): bump @modelcontextprotocol/server from 2.0.0-alpha.2 to 2.0.0-alpha.3#79
Open
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@modelcontextprotocol/server](https://github.com/modelcontextprotocol/typescript-sdk) from 2.0.0-alpha.2 to 2.0.0-alpha.3. - [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases) - [Commits](https://github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.0.0-alpha.2...@modelcontextprotocol/server-legacy@2.0.0-alpha.3) --- updated-dependencies: - dependency-name: "@modelcontextprotocol/server" dependency-version: 2.0.0-alpha.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
There was a problem hiding this comment.
No concrete security issues found in the changed files.
Reviewed changes:
apps/api/package.json: bumps@modelcontextprotocol/serverfrom2.0.0-alpha.2to2.0.0-alpha.3.pnpm-lock.yaml: updates the resolved MCP server package and removes its previous optional@cfworker/json-schemapeer; the new package resolves only tozod.
Threat surfaces checked:
- MCP endpoint auth: no route/auth code changed; verified existing flow still authenticates bearer token and project before server/tool registration and before resumed session handling, returns JSON-RPC auth errors, and passes token scopes into tool handlers.
- Query execution sandboxing: no query code changed; verified existing
execute_querypath still routes through scoped model checks, AST validation, read-only DuckDB instance/hardening, timeout handling, and 1000-row result limiting. - Admin auth (Better Auth): no admin auth files changed by this dependency bump.
- API input validation: no Hono route handler input schemas changed by this dependency bump.
- Environment secrets: no
.env.local/secret-bearing source changes; the lockfile/package change does not add secret logging or response exposure. - Dependency exposure:
@modelcontextprotocol/server@2.0.0-alpha.3is the currentlatest/alphadist-tag and does not introduce new transitive dependencies beyondzod.pnpm audit --prodreports unrelated existing advisories outside this package path, with no finding introduced through@modelcontextprotocol/server.
Verification run:
pnpm --filter @archmax/api typecheckpassed.npx vitest run apps/api/src/mcp/archmax-route.test.ts apps/api/src/mcp/archmax-server.test.ts packages/core/src/services/mcp-tools.test.ts packages/core/src/services/sql-ast-validation.test.tspassed (191tests).
Sent by Cursor Automation: archmax Security Review
Docker image readydocker pull ghcr.io/archmaxai/archmax:pr-79 |
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
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.


Bumps @modelcontextprotocol/server from 2.0.0-alpha.2 to 2.0.0-alpha.3.
Release notes
Sourced from @modelcontextprotocol/server's releases.
Commits
e4227d1Version Packages (alpha) (#1845)0fb8406v2: codemod iterations, canonical zod schema exports fromsdk-shared(#2354)7ea6fdetest(client): cover refresh retry after invalid token 401 (#2367)ee732d6chore: switch to module ESNext + moduleResolution bundler (#2095)c59dc3afeat(server): expose icons on registerTool/registerPrompt (McpServer) (#2353)6312f2afix(middleware): stop bundling workspace type graphs into .d.ts (avoids dts-g...5e0249ftest(integration): stop the cloudflare workers test from rewriting workspace ...78fbe27feat(core): reserved trace context _meta keys and propagation docs (SEP-414) ...e84c3e9fix(server,client): non-SEP draft spec conformance (eager list handlers, pagi...49c0a71feat: deprecate roots, sampling, and logging runtime APIs (SEP-2577) (#2268)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Low Risk
Dependency-only bump with no app code changes; alpha SDK upgrades can still affect MCP transport or tool registration behavior at runtime.
Overview
Bumps
@modelcontextprotocol/serverinapps/apifrom 2.0.0-alpha.2 to 2.0.0-alpha.3 and refreshespnpm-lock.yaml.@modelcontextprotocol/honostays on 2.0.0-alpha.2; the lockfile now resolves it against the new server version.The lockfile change drops the optional
@cfworker/json-schemapeer wiring for the server package;@modelcontextprotocol/servernow resolves withzodonly. No application source files are modified—MCP still importsMcpServerandWebStandardStreamableHTTPServerTransportfrom the same package paths.Reviewed by Cursor Bugbot for commit bcf9115. Bugbot is set up for automated code reviews on this repo. Configure here.