mcpkeel

Security

mcpkeel sits in your CI and starts the servers in your MCP config. Here is how its releases are built, what it does with that trust, and how to tell us when it gets something wrong.

Report a vulnerability

Email hello@mcpkeel.app with what you found and how to reproduce it. Please do not open a public issue for a vulnerability. You will get a reply within a few days; a confirmed issue is fixed as soon as the fix is ready, with credit in the release notes unless you prefer otherwise.

These count as vulnerabilities:

Verify what you install

Every release is built and published by GitHub Actions from a tagged commit, through npm trusted publishing: no token is stored anywhere, and each version carries a signed provenance statement that names the workflow and the commit it came from.

npm view mcpkeel@0.6.1 dist.attestations.provenance.predicateType
# https://slsa.dev/provenance/v1

npm audit signatures   # in a project that depends on mcpkeel

The GitHub Action runs the same package, pinned to an exact version. Pin the action itself to a commit in workflows that can write: mcpkeel/mcpkeel@<commit> # v0.6.1.

Every claim on this site comes from a recorded run in docs/EVIDENCE.md, and the measurements and how they were made are in the README.

What mcpkeel touches

Dependencies

Two direct dependencies: the official MCP TypeScript SDK, on its 1.x line, and smol-toml, pinned to an exact version, to read Codex configs. Updates to either are proposed only after a release has been public for two weeks. See also the privacy page.