Summary

createServer() passes a hard-coded version: '0.1.0' to the MCP Server (packages/mcp/src/server.ts#L39), so every client receives serverInfo.version: "0.1.0" in the initialize response. The value dates from the first MCP release (#273) and has never changed: @deepnote/mcp is at 0.4.1, and the published 0.4.1 build still reports 0.1.0. Clients and logs that record the server version cannot tell releases apart, which makes version-specific bug reports harder to triage.

Reproduction

pnpm --filter @deepnote/mcp... build
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' \
  | node packages/mcp/dist/bin.js | head -1

The response contains "serverInfo":{"name":"deepnote","version":"0.1.0"}, while packages/mcp/package.json says 0.4.1.

Expected

serverInfo.version equals the version in packages/mcp/package.json, read the way the CLI already does it in packages/cli/src/version.ts (import packageJson from '../package.json'). A test asserts that serverInfo.version matches package.json, so the next version bump cannot drift again.