serverInfo.version reports the MCP SDK version, not the server's #6

Open
opened 2026-08-26 06:21:30 +00:00 by jlxq0 · 0 comments
Owner

Observed against the released v0.2.0 image during a smoke test:

"serverInfo":{"name":"Listmonk MCP Server","version":"1.11.0"}

1.11.0 is the mcp SDK version. The server is 0.2.0, which GET /health reports correctly alongside the revision:

{"status":"healthy","version":"0.2.0","revision":"75caec3cd6fdec900b592e812385205eea4421d7"}

Cosmetic today and wrong in a way that gets believed: a client asking the server what version it is gets the version of the library it was built with. Any log line or dashboard keyed on serverInfo.version will be indistinguishable across every release of this server until the SDK bumps, and will appear to change when the SDK does.

FastMCP takes the version from its own package unless one is passed. Fix is to pass the project version at construction, the same value /health already reads.

Not urgent — nothing is deployed yet — but worth doing before anything consumes it.

Observed against the released `v0.2.0` image during a smoke test: ``` "serverInfo":{"name":"Listmonk MCP Server","version":"1.11.0"} ``` `1.11.0` is the `mcp` SDK version. The server is `0.2.0`, which `GET /health` reports correctly alongside the revision: ``` {"status":"healthy","version":"0.2.0","revision":"75caec3cd6fdec900b592e812385205eea4421d7"} ``` Cosmetic today and wrong in a way that gets believed: a client asking the server what version it is gets the version of the library it was built with. Any log line or dashboard keyed on `serverInfo.version` will be indistinguishable across every release of this server until the SDK bumps, and will appear to change when the SDK does. `FastMCP` takes the version from its own package unless one is passed. Fix is to pass the project version at construction, the same value `/health` already reads. Not urgent — nothing is deployed yet — but worth doing before anything consumes it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jlxq0/listmonk-mcp#6
No description provided.