Skip to content

@wasit-dev/server@0.3.0

Choose a tag to compare

View all tags
@dzakwannajmi dzakwannajmi released this 06 Sep 05:28
· 70 commits to main since this release
@wasit-dev/server@0.3.0
19ee60f

Fixes the version the MCP server reports in its initialize handshake. No tool, resource or result shape changed.

Install

npx -y @wasit-dev/server@0.3.0

What changed in this package

  • The server announced 0.1.0 in the MCP initialize handshake through two releases, because the version string was hardcoded. It now reads its own package manifest at runtime, the same way wasit --version does. Until now a client could file a bug against a version that was never published.
  • Bumped to @wasit-dev/core@^0.3.0, so the MCP server and the CLI always run the same check code rather than the server quietly trailing a version behind.

Compatibility

Node.js >=24, stdio transport. The four tools (wasit_x402_test, wasit_mpp_charge_test, wasit_mpp_channel_test, wasit_mpp_channel_test_with_close) and the wasit://checks resource are unchanged. structuredContent is unchanged since 0.2.0. wasit_mpp_channel_test_with_close is still registered only when the server is started with WASIT_ALLOW_DESTRUCTIVE=1 — an agent cannot call what it cannot see.

Known issues

Same nested Stellar SDK advisories as @wasit-dev/core — upstream peer ranges, no downstream fix. See SECURITY.md.

Links

CHANGELOG · npm · Full diff

Assets 2
Loading