MCP server reports stale version 1.0.0 in npm package 1.0.9

[Gan-Xing]

The published datadog-mcp-server@1.0.9 npm package initializes its MCP server with a stale protocol metadata version.

Static evidence from the published package:

• package/package.json declares:

{
  "name": "datadog-mcp-server",
  "version": "1.0.9"
}

• package/dist/index.js initializes the MCP server with:

const server = new McpServer({
    name: "datadog",
    version: "1.0.0",
    description: "MCP Server for Datadog API, enabling interaction with Datadog resources"
});

Expected behavior: the MCP server version exposed during client initialization should match the published package version, or be derived from package metadata during build, so clients and registries do not see stale server metadata.

Observed behavior: installing datadog-mcp-server@1.0.9 exposes MCP server metadata version 1.0.0.

This can be fixed by wiring the package version into the server initialization, for example by importing/reading package metadata during build or by updating the release process so dist/index.js is kept in sync.

I found this by static inspection of the npm tarball only; no Datadog credentials or runtime API calls were used.