Gate

Name: Gate
Author: nugehs

by nugehsversion 0.3.0i★ –iRuns on your computer

Registry nameio.github.nugehs/gate

Install

Overview

Description from the maker (original English)

One ship/no-ship verdict from aiglare, bouncer, tieline & repoctx — the unified merge gate.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "gate": {
      "command": "npx",
      "args": [
        "-y",
        "@nugehs/gate",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add gate -- npx -y @nugehs/gate mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gate": {
      "command": "npx",
      "args": [
        "-y",
        "@nugehs/gate",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gate": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nugehs/gate",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account nugehs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32568 servers in this category
Published to the registry more recently than 13% of the other 32568 servers in this category
Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Gate safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 ✓ PASS

What 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 skipped

Each tool's native result is normalized onto one status vocabulary:

Status	Meaning
`pass`	the check ran and is clean
`warn`	ran, found something worth a look — not blocking
`fail`	ran, found a blocking problem
`unknown`	ran, but couldn't determine — explicitly not a pass
`skipped`	not applicable / not configured for this repo
`error`	the tool couldn't be run, or returned garbage

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

Tool	Native signal	→ gate
aiglare	a red surface on a side-effectful sink	`fail`; any red/amber → `warn`
bouncer	a `fail` finding (missing required control)	`fail`; any `unknown` control → `unknown`
tieline	`drift` > 0 (FE call with no BE route)	`fail`; `unverifiable` > 0 → `warn`
repoctx	`FAIL`/`BLOCK` merge verdict	`fail`; `WARN` → `warn`

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.

On repoctx + local mode. repoctx's merge-readiness gate can only verify review state (approvals, CODEOWNERS, required checks) against a host like GitHub. Run locally it reports those as a WARN, so on a clean local repo gate will often show merge readiness: warn. That's repoctx being honest about what it can't see locally — not a problem with your change.

CLI

gate [path] [options]

--json Emit the unified verdict as JSON --ci Exit non-zero when the gate fails (blocking by default) --strict Treat WARN/UNKNOWN as blocking too --only Run only these tools (aiglare,bouncer,tieline,repoctx) --skip Skip these tools -h, --help Show this help

gate mcp Start the MCP server (stdio)

By default only a fail verdict blocks under --ci — safe to adopt without drowning a team in warnings. Add --strict when you want warnings to gate too.

Tool resolution

gate doesn't bundle the four tools; it finds each one at runtime. Per tool, first hit wins:

GATE_ _BIN environment variable (explicit override)
the installed @nugehs/ package (from node_modules)
a sibling checkout at ../ (local development)

A tool that can't be resolved is reported as skipped, never a hard failure — so gate is safe to run in a repo that only uses some of the toolchain.

In CI

- run: npx @nugehs/gate . --ci

For a machine-readable record, --json emits the full verdict (schema version, per-domain results, counts, and the blocking reasons) for dashboards or audit evidence.

MCP

gate is also an MCP server, so an agent can ask "can this ship?" in one call — the unified verdict, not four separate tools.

gate mcp                 # stdio JSON-RPC server

npx @nugehs/gate mcp

Tools:

Tool	Returns
`gate_check`	the unified verdict for a repo (`path`, optional `only`/`skip`/`ci`/`strict`)
`list_checks`	the four checks gate runs, each with its domain and what it answers

Registry manifest: server.json (io.github.nugehs/gate).

Editor extension

The same normalized verdict drives a VS Code / Cursor extension (clients/vscode) — the gates, shifted left from CI into the editor:

a verdict cockpit and a checks tree in gate's own Activity Bar container;
inline diagnostics, hovers, Quick Fixes (mute / open docs) and CodeLens on located findings;
AI-native gating — an @gate chat participant, a gate_check tool agent mode can call before it says "done", and an MCP server provider — so the assistant writing the code is checked by the same gate as CI;
debounced run-on-save with in-flight cancellation, and multi-root support.

Roadmap

gate is the shared spine. The same JSON already drives the CLI, the --ci gate, the MCP server, and the editor extension above. Next client on the same JSON:

Web cockpit — a repo/PR verdict board over the JSON, unifying the four *-web sites.

Gate

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FlyDocs

README from the maker

gate

What it reports

How each dialect maps

CLI

Tool resolution

In CI

MCP

Editor extension

Roadmap

License