Skip to content

v3.0.2 — MCP Registry

Choose a tag to compare

View all tags
@NickCirv NickCirv released this 24 Apr 17:05
v3.0.2
2d17084

v3.0.2 — MCP Registry integration (chore)

Patch release. No runtime changes. Adds the mcpName field to package.json required by the Official MCP Registry (registry.modelcontextprotocol.io) for namespace-ownership proof, and tightens the server.json descriptions to the registry's 100-char limit.

What changed

  • package.json → top-level "mcpName": "io.github.NickCirv/engram"
  • server.json → descriptions shortened (top-level 343 → 91 chars; 5 env-var descriptions 102-158 → 53-83 chars each)
  • Both bumped to 3.0.2 to match the required npm publish

Why not in 3.0.1

3.0.1 needed to ship the preuninstall hook-cleanup as fast as possible after @freenow82's report. The MCP Registry integration surfaced only during the submission flow after 3.0.1 was already live — separate concern, separate patch.

For users

Nothing to do. 3.0.1 works correctly; 3.0.2 is an infra-side nicety that makes engramx discoverable at registry.modelcontextprotocol.io. npm install -g engramx picks up 3.0.2 on the next install.

Verification

  • 878/878 tests passing
  • CI green Ubuntu + Windows × Node 20 + 22
  • TypeScript strict, lint clean
Assets 2
Loading