Gate MCP server
One ship/no-ship verdict from aiglare, bouncer, tieline & repoctx — the unified merge gate.
0 stars
Reviews
Write oneNobody has reviewed Gate yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gate tools (2, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
gate_checkwrite actionRun aiglare, bouncer, tieline & repoctx against a repo and return one normalized verdict (pass|warn|fail), with each tool reduced to a status and the blocking reasons. The single "can this ship?" call for the nugehs toolchain.
list_checksList the four checks gate runs, each with the domain it covers and what it answers.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan15 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 105 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Gate compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 1 read · 1 change
Install Gate in Claude Code, Cursor or VS Code
Runs npx -y @nugehs/gate on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add gate -- npx -y @nugehs/gate
What the publisher says
From the Gate repository's README, as published. We do not edit it. Read it on GitHub
gate
One ship/no-ship verdict from your whole nugehs toolchain.
gate runs aiglare, bouncer, tieline and repoctx against a repo and merges their four dialects into one normalized verdict. Each tool already answers a different "can this ship?" question — gate is the place they finally agree on the answer.
npx @nugehs/gate # audit the current repo
npx @nugehs/gate ./service --ci # fail the build on a blocking verdict
npx @nugehs/gate --json # the unified verdict, machine-readable┌──────────────────────────────────────────────┐
│ gate │
│ one config · one verdict · one report │
└──────────────────────────────────────────────┘
│ │ │ │
aiglare bouncer tieline repoctx
red/amber/ pass/fail/ matched/ PASS/WARN/
green unknown drift FAIL
│ │ │ │
└──── normalize to pass · warn · fail ─────┘
│
✗ FAIL ⚠ WARN ✓ PASSWhat it reports
gate · /path/to/repo
✗ AI governance fail 2 red · 1 amber · 13 green · 1 blocking side-effect
· Compliance skipped not configured (run `bouncer init`)
· Contract drift skipped not configured (run `tieline init`)
⚠ Merge readiness warn 1 of 8 checks need attention
verdict: FAIL — 1 blocking · 1 warn · 2 skippedEach tool's native result is normalized onto one status vocabulary:
The top-level verdict is the worst across the domains that actually ran (skipped never counts). unknown and error roll up to warn so nothing slips through as a silent pass.
How each dialect maps
gate runs aiglare without --ci and derives the blocking verdict itself,
so a tool that process.exit()s before flushing its pipe can't truncate the
report it feeds us.
A run that checked nothing is not a pass. If every domain is skipped or deselected (e.g. --skip them all, or a typo'd --only), gate reports NO CHECKS RAN (ok:false) and fails under --ci — a misconfiguration can't silently turn the gate green.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gate: common questions
- Is Gate MCP server safe?
- Mostly: it is graded B (82/100). Read the Gate safety report
- How do I install Gate?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Gate need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Gate maintained?
- The last commit was 143 days ago (2026-06-14). The latest release is v0.3.0.
- How does Gate compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.