github modelcontextprotocol/servers v2.5.0

36 minutes ago

Security fixes

v2.5.0 fixes eight vulnerabilities in three servers. Upgrade mcp-server-git to 2026.11.18,
@modelcontextprotocol/server-filesystem to 2.4.0 and @modelcontextprotocol/server-everything to 2.3.1.

Package Affected Fixed in
mcp-server-git through 2026.11.11 2026.11.18
@modelcontextprotocol/server-filesystem all versions before 2.4.0, and date versions 2025.1.14 through 2026.8.31 2.4.0
@modelcontextprotocol/server-everything through 2.3.0 2.3.1

mcp-server-git 2026.11.18

  • A merge no longer starts Git's automatic maintenance. A successful git_merge, a fast-forward included, ended in git maintenance run --auto, whose garbage collection runs the commands a repository's own gc.recentObjectsHook names, with the server's privileges. maintenance.auto is now false and gc.auto is 0 for every Git command the server runs (GHSA-h2g3-rwxm-xfm3)
  • Git never fetches a missing object by itself. A repository's configuration could declare a promisor remote and name the program Git runs to fetch from it (remote.<name>.uploadpack, core.sshCommand), which a read-only tool then started when it needed an object that was not on disk. Lazy fetching is turned off (GIT_NO_LAZY_FETCH=1), and a Git too old to honor that refuses a repository that declares a promisor remote (GHSA-87qg-cmw8-jc5m)
  • Drivers are read again after a tool writes the working tree. A repository's configuration can include a file that a merge or checkout creates, so a filter or merge driver could appear after the server had emptied the ones it found, and run during the git merge --abort that follows a conflict. git_checkout, git_merge and that abort now read the drivers again before any other Git command runs. The --repository confinement check is not yet repeated after such a write; that is tracked as a follow-up (GHSA-9vjp-x34c-xg6v)
  • A filter or merge driver with an empty name is emptied too. Git accepts [filter ""], selected by filter= in .gitattributes, and the server's list of a repository's drivers missed it, so its command ran (GHSA-pm7p-vphh-2cg7)
  • Index entries that point outside the working tree are refused. With --repository, a crafted .git/index naming a path such as ../outside/secret made git_diff_unstaged and git_diff return that file's content, and git_status report whether it exists. The index is now checked from its top before any tool reads it, and the untracked cache, which can name a directory outside the working tree, is turned off (GHSA-r2q8-f657-4r56)
  • A submodule's own configuration no longer runs programs. With diff.submodule=diff in the repository's configuration, git_diff ran a nested diff inside each changed submodule under the submodule's own diff.external and textconv drivers, and git_checkout and git_add ran Git inside a submodule under its own configuration too. diff.submodule is now short, the drivers a checked-out submodule defines are overridden, and a Git older than 2.33, which would not pass the overrides into a submodule, is refused for a repository that has one checked out (GHSA-8wv7-r664-7594)

@modelcontextprotocol/server-filesystem 2.4.0

  • Directory listings stay with the directory that was checked (Linux and macOS). list_directory, list_directory_with_sizes, directory_tree and search_files now list a directory in place after checking it, so a directory swapped for a symlink between the check and the listing can no longer return the names of entries outside the allowed directories. On Windows a listing is not yet anchored; that is tracked as a follow-up (GHSA-rq2p-q7c4-6g27)

@modelcontextprotocol/server-everything 2.3.1

  • gzip-file-as-resource treats a NAT64 address as the IPv4 address it carries. The tool's private-address guard read addresses in 64:ff9b::/96 as public, so on a network with a NAT64 gateway a URL could reach a private IPv4 address through one. The embedded IPv4 address is now checked (GHSA-38j4-j742-j7r3)

Upgrading from a date-versioned npm release

The TypeScript servers moved from date versions (2025.x, 2026.x) to semantic versions in 1.0.0. Package managers rank 2.4.0 below every 2025.x and 2026.x version, so they won't offer it as an upgrade. If you are on a date version of @modelcontextprotocol/server-filesystem, install 2.4.0 explicitly: npm install @modelcontextprotocol/server-filesystem@2.4.0.

Packages

Package Version Registry In this release
@modelcontextprotocol/server-everything 2.3.1 npm published
@modelcontextprotocol/server-filesystem 2.4.0 npm published
@modelcontextprotocol/server-memory 2.2.1 npm published
@modelcontextprotocol/server-sequential-thinking 2.2.0 npm published
mcp-server-fetch 2026.11.18 PyPI published
mcp-server-git 2026.11.18 PyPI published
mcp-server-time 2026.11.18 PyPI published

Release ledger: v2/chore/5572-release-v2.5.0

@modelcontextprotocol/server-everything 2.3.1

What's Changed

  • docs(everything): state the whole-segment rule for get-env masking by @cliffhall in #5532
  • fix(everything): GHSA-38j4-j742-j7r3 by @cliffhall in #5583
  • chore: version packages by @github-actions[bot] in #5537
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

@modelcontextprotocol/server-filesystem 2.4.0

What's Changed

  • Serve Streamable HTTP from every reference server by @cliffhall in #5536
  • docs(filesystem): document the Windows parent-directory swap as a limit of the implementation by @cliffhall in #5568
  • fix(filesystem): GHSA-rq2p-q7c4-6g27 by @cliffhall in #5584
  • chore: version packages by @github-actions[bot] in #5537
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

@modelcontextprotocol/server-memory 2.2.1

What's Changed

  • fix(memory): release held lock files on exit and SIGINT/SIGTERM by @cliffhall in #5530
  • Serve Streamable HTTP from every reference server by @cliffhall in #5536
  • feat(memory): opt-in write limits on graph size by @cliffhall in #5534
  • fix(memory): never delete a successor's live lock when breaking a stale one by @cliffhall in #5563
  • chore: version packages by @github-actions[bot] in #5537
  • fix(memory): release held locks when the Streamable HTTP server stops by @cliffhall in #5596
  • chore: version packages by @github-actions[bot] in #5597
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

@modelcontextprotocol/server-sequential-thinking 2.2.0

What's Changed

  • fix(sequentialthinking): count header rows toward the log box's row cap by @cliffhall in #5535
  • Serve Streamable HTTP from every reference server by @cliffhall in #5536
  • chore: version packages by @github-actions[bot] in #5537
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

mcp-server-fetch 2026.11.18

What's Changed

  • docs(docker): drop the stale --db-path comments in the fetch and git Dockerfiles by @cliffhall in #5531
  • Serve Streamable HTTP from every reference server by @cliffhall in #5536
  • fix(fetch): refuse --allowed-hosts wildcards on IP addresses by @cliffhall in #5562
  • fix(fetch): connect only to the address the private-IP guard checked by @cliffhall in #5564
  • chore(fetch): raise the Python floor to 3.11.5 so the lock drops soupsieve 2.10 by @cliffhall in #5567
  • fix(fetch): clear the Python 3.11 ruff findings in the pinning code by @cliffhall in #5571
  • chore: stamp Python CalVer versions for 2026.11.18 by @github-actions[bot] in #5591
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

mcp-server-git 2026.11.18

What's Changed

mcp-server-time 2026.11.18

What's Changed

  • Serve Streamable HTTP from every reference server by @cliffhall in #5536
  • chore: stamp Python CalVer versions for 2026.11.18 by @github-actions[bot] in #5591
  • Release v2.5.0: merge v2/main into main by @cliffhall in #5592

Repository

What's Changed

  • ci: add mcp-interface-diff.yml as a dispatch-only placeholder (staged rename, Step 1) by @cliffhall in #5528
  • fix(scripts): scope a hoisted npm copy by the ranges it satisfies by @cliffhall in #5529
  • chore(deps): pin hono >=4.13.16 and @hono/node-server >=2.1.6 via overrides by @cliffhall in #5561

Full Changelog: v2.4.0...v2.5.0

Thanks for helping us improve

This release addresses issues and vulnerabilities reported by these community members. Thank you for taking the time to report them:

Don't miss a new servers release

NewReleases is sending notifications on new releases.