Skip to content

Repository navigation

Security: alexchen-sys/mcp-node-zig

Security

Report a vulnerability

SECURITY.md

Security Policy

mcp-node runs commands for whoever holds the token. Treat the token like a root password.

Reporting

Please don't open a public issue. Report privately:

  • GitHub: Security tab → Report a vulnerability
  • Email: l46983284@gmail.com, subject mcp-node security

Include the version or commit, steps to reproduce, and the impact.

You'll get a reply within a few days. Fixes ship as a new patch release.

Supported versions

Only the latest release gets security fixes.

Scope

In scope:

  • Reaching any tool without a valid token
  • Bypassing the Host or Origin allowlist
  • Request smuggling or desync in the HTTP layer
  • Exceeding the configured resource caps (output, connections, sessions, request size)
  • One session reading or killing another without its id
  • Connecting to a hub as a node without that node's secret
  • Audit log records altered, removed or reordered without audit-verify noticing

Out of scope:

  • A token holder running commands or reading and writing any file. That's the product.
  • DoS by an authenticated caller within configured limits
  • Token theft from your own infrastructure
  • Deployments with MCP_NODE_INSECURE=1

Deploying safely

  • Keep the default 127.0.0.1 bind. For remote machines, use reverse connect with MCP_NODE_CONNECT_TLS=1; to expose the HTTP API directly, put a TLS proxy or a VPN in front of it.

  • Keep the token file at 0600 and rotate it if exposed.

  • Leave MCP_NODE_ALLOWED_HOSTS and MCP_NODE_ALLOWED_ORIGINS at their defaults unless you need more.

  • Run as a dedicated, unprivileged user. Root isn't needed.

  • Verify what you install. SHA256SUMS.txt is signed keyless by the release workflow (Sigstore bundle SHA256SUMS.txt.sigstore.json), and every archive carries a GitHub build provenance attestation. With cosign installed, MCP_NODE_VERIFY=require makes install.sh refuse anything unsigned. By hand:

    cosign verify-blob SHA256SUMS.txt --bundle SHA256SUMS.txt.sigstore.json \
  --certificate-identity "https://github.com/alexchen-sys/mcp-node-zig/.github/workflows/release.yml@refs/tags/v<version>" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
gh attestation verify mcp-node-v<version>-<target>.tar.gz --repo alexchen-sys/mcp-node-zig

  • Turn on the audit log (MCP_NODE_AUDIT_FILE) and keep its key off the audited machine where you can.

There aren't any published security advisories