serverInfo.version hardcoded as "0.6.3" in @modelcontextprotocol/server-memory@2026.1.26
Describe the bug
The serverInfo.version field returned during MCP initialization is hardcoded as "0.6.3" in the compiled dist/index.js of the 2026.1.26 release. It does not reflect the actual npm package version.
To Reproduce
- Install
@modelcontextprotocol/server-memory@2026.1.26
- Start the server and send an
initialize request
- Observe the response:
{
"serverInfo": {
"name": "memory-server",
"version": "0.6.3"
}
}Expected Behavior
serverInfo.version should reflect the published package version (2026.1.26).
Root Cause
The version string in dist/index.js is hardcoded rather than read dynamically from package.json at runtime. It was not updated when the package transitioned from 0.x semver to calendar versioning. First introduced in 2025.4.25 — the first calendar versioning release — and present in every release through 2026.1.26.
Impact
Causes confusion when diagnosing MCP startup issues — the reported version does not match the installed package version, making it appear the server has regressed to an older release.
serverInfo.versionhardcoded as"0.6.3"in@modelcontextprotocol/server-memory@2026.1.26Describe the bug
The
serverInfo.versionfield returned during MCP initialization is hardcoded as"0.6.3"in the compileddist/index.jsof the2026.1.26release. It does not reflect the actual npm package version.To Reproduce
@modelcontextprotocol/server-memory@2026.1.26initializerequest{ "serverInfo": { "name": "memory-server", "version": "0.6.3" } }Expected Behavior
serverInfo.versionshould reflect the published package version (2026.1.26).Root Cause
The version string in
dist/index.jsis hardcoded rather than read dynamically frompackage.jsonat runtime. It was not updated when the package transitioned from0.xsemver to calendar versioning. First introduced in2025.4.25— the first calendar versioning release — and present in every release through2026.1.26.Impact
Causes confusion when diagnosing MCP startup issues — the reported version does not match the installed package version, making it appear the server has regressed to an older release.