# zn-gate

Local security layer for coding agents (Claude Code, Codex CLI, Cursor, OpenCode): keeps secrets out of what the agent sends to the model, checks for prompt injection and guards the MCP servers you wrap.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.8.2
- **Author:** usezn
- **License:** MIT
- **npm:** zn-gate
- **Source:** https://github.com/usezn/zn
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-16T10:38:34.539Z
- **Version scanned:** 1.9.0
- **CVEs:** none found by OSV at scan time

## Tools

20 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `auto-run-command`
- `download-and-run`
- `project-mcp-command`
- `mcp-auto-approve`
- `unpinned-package`
- `remote-mcp`
- `endpoint-override`
- `code-loading-env`
- `credential-helper`
- `broad-permissions`
- `secret-in-config`
- `instruction-injection`
- `instruction-download-run`
- `instruction-exfiltration`
- `instruction-weaken-checks`
- `shadowing-executable`
- `project-plugins`
- `agent-extensions`
- `ci-agent-untrusted-input`
- `unchecked-agent-file`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"zn-gate\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"zn-gate\"\n      ],\n      \"env\": {\n        \"ZN_API_KEY\": \"<YOUR_ZN_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `ZN_API_KEY` — Zn API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Critical blast radius — runs commands; holds an api key.
- Floor 64, ceiling 64 (tier: critical)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/zn-gate
- Install plan: https://forgeregistry.com/api/v1/packages/zn-gate/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/zn-gate
- HTML page: https://forgeregistry.com/registry/zn-gate
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.