prepare MCP 0.1.1 release

[kopachlager]

What changed

• bump the package and lockfile to 0.1.1
• keep test version fixtures aligned with the release

Why

Version 0.1.0 bootstrapped the new npm package. This release validates the protected GitHub OIDC workflow and publishes the promotable package with npm provenance.

Validation

• 7 tests passing
• 98.52% line coverage
• 95% branch coverage
• syntax checks passing
• package contents verified: 9 files, 7,744 bytes
• zero production audit vulnerabilities

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: be873c3031

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep the advertised server version aligned

When clients connect to the published 0.1.1 package, MCP initialization still reports serverInfo.version as 0.1.0 because src/server.js:8 remains hard-coded to the old version. The change in test/server.test.js only updates the test client's identity, so it neither fixes nor detects this mismatch; update the server identity or derive it from the package version.

Useful? React with 👍 / 👎.