MCP server advertises wrong version (0.1.0) to clients

[eliottreich]

Problem

The server reports version 0.1.0 to MCP clients during the initialize handshake, but the package is at 0.3.0.

Evidence

src/index.ts line 596-599:

const server = new Server(
  { name: "taskbounty-mcp-server", version: "0.1.0" },
  { capabilities: { tools: {} } },
);

Meanwhile PKG_VERSION = "0.3.0" (line 8) and package.json is "version": "0.3.0". The --version flag correctly prints 0.3.0, but the value sent over the MCP protocol is the stale literal 0.1.0.

Why it matters

MCP clients (Claude Desktop, Cursor, Cline) read the server's advertised version for diagnostics and compatibility. Reporting 0.1.0 while shipping 0.3.0 creates confusing bug reports and makes it impossible to tell from a client which version is actually running.

Acceptance criteria

• The version passed to new Server(...) matches the package version (single source of truth, e.g. reuse PKG_VERSION or import from package.json).
• A regression test asserts the server's advertised version equals the package.json version, so the two cannot drift again.

[cybercraftsolutionsllc]

Submitted PR #21 to make the MCP advertised server version match package.json with a regression test. Payout route if needed: 0xB34D185318b34ec2F9E060F662Cc7feA3180049c