MCP.Market

Vibe Gate MCP server

by mustafacagri·io.github.mustafacagri/vibe-gate-mcp·v0.1.12

Adversarial Quality Gate MCP for vibe-coding: IDE AI vs Critic AI, human decides on deadlock

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars460 downloads/wk

Reviews

Write one

Nobody has reviewed Vibe Gate yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vibe Gate tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vibe Gate compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Downloads a week
460
more than 87% of 12,191 servers with a package

Install Vibe Gate in Claude Code, Cursor or VS Code

Runs npx -y vibe-gate-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vibe-gate-mcp -- npx -y vibe-gate-mcp
Add to Cursor

What the publisher says

From the Vibe Gate repository's README, as published. We do not edit it. Read it on GitHub

Vibe-Gate (MCP)

An Adversarial Quality Gate for AI-assisted IDEs: the IDE agent and a Critic LLM debate code; the human decides only on deadlock.

Quick start (npm / npx)

1. Choose a Critic provider

Use a direct API provider with its key, or use a local CLI that is already installed and signed in. Local CLI providers do not need a separate provider API key. If CRITICPROVIDER is omitted, Vibe-Gate selects the first installed local CLI in this order: Codex, Claude Code, Cursor Agent, then OpenCode CLI. OpenCode CLI moves to the front when CRITICMODEL is in provider/model form. The first review response includes a notice naming the selected CLI. If none is found, OpenAI remains the default and requires OPENAIAPIKEY. Set CRITIC_PROVIDER to choose explicitly.

Copy from the package’s .env.example:

# Direct API example
CRITIC_PROVIDER=openai
OPENAI_API_KEY=YOUR_OPENAI_API_KEY

# Or use the signed-in Codex CLI account (no API key)
# CRITIC_PROVIDER=codex-cli

# Or another signed-in local CLI (no separate API key)
# CRITIC_PROVIDER=claude-code
# CRITIC_PROVIDER=cursor-agent
# CRITIC_PROVIDER=opencode-cli
# CRITIC_MODEL=provider/model  # required for opencode-cli; see `opencode models`

# Or OpenCode (https://opencode.ai/auth)
# CRITIC_PROVIDER=opencode
# OPENCODE_API_KEY=...
# OPENCODE_PLAN=go
# CRITIC_MODEL=minimax-m3

For Cursor Agent, Vibe-Gate runs agent first and falls back to the legacy cursor-agent executable if the primary command is unavailable.

opencode is still the separate Zen/Go HTTP provider and needs OPENCODEAPIKEY. opencode-cli runs the local CLI and requires a provider/model value in CRITIC_MODEL; see the CLI guide for details.

CRITIC_MODEL is passed to the selected provider or CLI without a Vibe-Gate model allowlist; the provider must support that model ID. The OpenAI API provider uses the Responses API. See provider configuration.

See CLI provider setup and alternatives for CLI installation, login, configuration, OpenCode session details, and other candidates we evaluated. Full variable list: docs/project/VARIABLES.md.

2. Configure Cursor MCP (any consumer repo)

Project or user .cursor/mcp.json for Codex CLI (or use the API-key example):

{
  "mcpServers": {
    "vibe-gate": {
      "command": "npx",
      "args": ["-y", "vibe-gate-mcp"],
      "env": {
        "VIBE_WORKSPACE_ROOT": "${workspaceFolder}",
        "CRITIC_PROVIDER": "codex-cli"
      }
    }
  }
}

For direct providers, prefer keys in a local .env next to the package or in the consumer project under VIBEWORKSPACEROOT (never commit secrets). MCP env overrides .env. For a CLI provider, install and sign in to that CLI as the same OS user running the MCP server.

3. Call the tool (agents)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vibe Gate: common questions

Is Vibe Gate MCP server safe?
Mostly: it is graded B (83/100). Read the Vibe Gate safety report
How do I install Vibe Gate?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vibe Gate need an API key?
Yes. The registry entry asks for OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_GENERATIVE_AI_API_KEY, MINIMAX_API_KEY and 1 more.
Is Vibe Gate maintained?
The last commit was 28 days ago (2026-10-07). The latest release is v0.1.12.
How does Vibe Gate compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); downloads a week 460 (more than 87% of 12,191 servers with a package). Full comparison.