mcp-server-discovery reports version 1.0.0 in package 0.3.6

Start by locating the source or build entry point that produces dist/cli.mjs and calls createMCPServer, then compare it with package.json metadata. Update the version source so the MCP server reports the published package version, and verify the built output exposes 0.3.6 instead of 1.0.0.

The published @transcend-io/mcp-server-discovery@0.3.6 package appears to initialize its MCP server with stale hardcoded server metadata version 1.0.0.

Static evidence from the published npm package:

• package.json declares:

{
  "name": "@transcend-io/mcp-server-discovery",
  "version": "0.3.6"
}

• dist/cli.mjs initializes the MCP server with:

createMCPServer({
  name: "transcend-mcp-discovery",
  version: "1.0.0",
  getTools: getDiscoveryTools,
  createClients: ({ auth, sombraUrl, graphqlUrl, dashboardUrl }) => ({
    rest: new TranscendRestClient(auth, sombraUrl),
    graphql: new DiscoveryMixin(auth, graphqlUrl),
    dashboardUrl
  })
});

Expected behavior: the MCP serverInfo.version exposed during client initialization should match the published package version (0.3.6) or be generated from package metadata during build/release.

Observed behavior: the package version is 0.3.6, but the MCP server metadata version is hardcoded as 1.0.0.

This is separate from CLI --help / --version auth preflight behavior. It affects the server metadata a client receives on normal MCP initialization.

Suggested fix: pass the package version into createMCPServer, or generate the version literal during the package build so it stays in sync with releases.

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