AgentGate
Open source · Apache-2.0

Scan, lock, and gate your MCP servers

The npm audit + lockfile + CI drift gate for the MCP era. One command against tool poisoning, rug-pulls, credential leaks, and known advisories.

git clone https://github.com/wookat/agentgate
agentgate scan
$ agentgate ci --fail-on high

✔ filesystem-server      12 tools · matches lock
✔ github-server          8 tools · matches lock
⚠ web-fetch-server       SSRF vector: unrestricted URL fetch
✖ postmark-mcp@1.0.16    MCPA-2025-0002 · hidden BCC backdoor
✖ notes-server           tool description drift from lock

2 critical · 1 warning · exit code 1
Gate closed. Review drift with `agentgate diff`.

One loop, four gates

Everything fragmented across five point tools today, in a single coherent workflow.

scan

Static + live analysis: tool poisoning, hidden Unicode, credential leaks, SSRF/RCE vectors, over-privileged combos.

lock

Pin the exact tool surface — names, descriptions, schemas — into agentgate.lock. Rug-pulls can’t hide.

gate

CI fails on any drift from the approved baseline. Human-readable diffs, not binary allow/deny.

advise

Cross-check every server against a public, structured MCP advisory database — free API, CLI-integrated.

Gate your agent in three steps

  1. 1

    Install

    One global install; auto-discovers Claude, Cursor, VS Code, and Codex MCP configs.

  2. 2

    Scan & lock

    Audit every configured server, then pin the approved tool surface to agentgate.lock.

  3. 3

    Gate in CI

    Add one CI step (or the GitHub Action). Any upstream drift turns the build red.

terminal
# 1. install
$ git clone https://github.com/wookat/agentgate
$ cd agentgate && pnpm install && pnpm build

# 2. scan and lock
$ agentgate scan
$ agentgate lock

# 3. gate in CI
$ agentgate ci --fail-on high