misp-mcp changelog

v1.3.6

Jul 17, 2026

Restored Node 20 support. The undici 8 dependency requires Node 22.19+, so 1.3.4 and 1.3.5 crashed at startup (webidl.util.markAsUncloneable is not a function) on every Node 20 install despite the package declaring Node 20 support. undici is pinned back to ^7.28.0, which the fetch-dispatcher fix from 1.3.5 works with unchanged. engines.node is now an honest >=20.18.1 (undici 7's floor). This was masked in CI because npm test ran with continue-on-error.

CI no longer carries a duplicate tag-triggered npm publish job; releases publish only through the Publish npm workflow (trusted publishing). The old job had no token and failed with ENEEDAUTH on every tag.
npm test in CI is no longer continue-on-error, so test failures fail the build again.
Repo memory owner switched from claude to codex; harness docs and Brigade config updated to match.

Jul 17, 2026

All MISP requests now go through undici's own fetch instead of the Node.js global fetch. Passing an npm-undici Agent to the runtime-bundled global fetch fails outright when the two undici versions disagree on the dispatcher interface (with undici 8 on Node 22 every request died with fetch failed before reaching the network), which surfaced as the server never contacting the MISP API (#2).
Network errors now include the underlying cause chain and a targeted hint instead of a bare fetch failed: TLS certificate rejections point at MISP_VERIFY_SSL, DNS failures report the unresolvable hostname, and refused or unreachable connections call out the URL, port, and firewall path.

README now opens with a what / why / how-it-differs lead and a copy-paste npx -y misp-mcp MCP client config, surfaces the website link near the top, and adds "Why not the MISP web UI or raw API?" and "What misp-mcp is not" sections. The full tool list is re-verified against the server source (36 tools, 3 resources, 3 prompts).

Maintainer-health files: SECURITY.md (private reporting, scope, and the API-key trust model), CONTRIBUTING.md, CODE_OF_CONDUCT.md, a CHANGELOG.md, GitHub issue forms (bug, feature, plus a config.yml that disables blank issues and routes security and MISP-platform questions off-issue), and a pull request template with a no-PII / content-guard checklist.