Update server version to match package semantic version and force npm publish

[olaservo]

Description

Issue #674 has been open a while and the publish process is triggered by an update to a typescript file in the server.

I also noticed that the server version does not match the semantic version in the package, so I thought this would be a good candidate as a small change to trigger this process.

Server Details

• Server: memory
• Changes to: version number

Motivation and Context

Need the latest published to npm.

How Has This Been Tested?

I don't have a way to test the publish process in advance, but users have tested the fix that will be published in the package.

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

[tadasant]

Thank you!