MCP Servers v2.2.0 Released: Support for CA Certificate Updates
Following reports that private keys for eMudhra intermediate CA certificates could be recovered, MCP Servers v2.2.0 has been released. It details the responses from Node.js and Python's certifi.
eMudhra disclosed on October 20, 2026, that private keys for eight of its intermediate CA certificates could be recovered from public certificates. In response, Node.js shipped security releases on October 21 to update its bundled CA certificates and fix several unrelated high-severity runtime CVEs. Additionally, Python's certifi 2026.10.23 removed the emSign Root CA - C1 and emSign ECC Root CA - C3 roots.
Regarding MCP Servers v2.2.0, TypeScript servers rely on the Node.js runtime for certificate checks and ship no CA certificates of their own. The servers server-filesystem, server-memory, server-sequential-thinking, mcp-server-git, and mcp-server-time make no network connections. Only server-everything makes outbound HTTPS requests (gzip-file-as-resource).
mcp-server-fetch verifies HTTPS against the certifi bundle through httpx. Installing from PyPI (uvx mcp-server-fetch, pip install mcp-server-fetch) resolves certifi 2026.10.23 or later. The repository's fetch Dockerfile moves to certifi 2026.10.23 via its lockfile. If running a TypeScript server from npm, users must update their own Node.js environment.
This item is a summary. The full, checkable version is at the original source:
Read the original at MCP Servers ↗