Highlights: Literal and prototype-named keys are preserved through proxies, schemas, and CLI selectors, and configuration diagnostics show the selected path.
- Preserve literal keys through proxies, generated schemas, and canonical JSON, including prototype-named and empty fields; keep distinct cached tool names and require own properties for required arguments.
- Preserve prototype-named CLI selectors and argument keys across named, JSON, function-call, and positional syntax instead of dropping values or treating them as flag handlers.
- Show the selected
--configorMCPORTER_CONFIGpath in configuration diagnostics instead of reporting only default locations. - Recover lost Chrome relay connections by retiring the current MCP child before the next explicit call creates a fresh authenticated connection, preserving setup cleanup and never replaying interrupted tool calls.
- Verify Vitest 5 on Node 24 and 26 with strict CI engine checks, omit the unsupported non-LTS Node 25 development line while retaining the Node >=24 runtime floor, and ignore Vitest's generated reports.
- Refresh Zod to 4.6.2 across the runtime and protocol fixtures, plus JOSE and test coverage dependencies, preserving Node 24 support and the 48-hour dependency release-age policy.
- Refresh Zod, Hono, Node types, and Vite; pin GitHub Actions to verified releases and avoid duplicate CI builds while preserving Node 24 and the 48-hour dependency release-age policy.
Packages and verification
- npm mcporter 0.13.13
- npm registry tarball
- npm integrity:
sha512-rgltHjpmdsBzErnWfAlNsW6Sn5B3y3Qli8phNtKkgn7s/Lk3Uf1YWLpqJXrIXjhxzBR67Oi5Z3+wxptn/vxFkA== - Exact release-commit CI
- Signed and notarized arm64 and x86_64 binaries are attached, with SHA-256 checksums and provenance.
- Native arm64 and Intel release-asset verification