io.github.mustafacagri/vibe-gate-mcp
NPM · VIBE-GATE-MCP
Adversarial Quality Gate MCP for vibe-coding: IDE AI vs Critic AI, human decides on deadlock
Available components
Last scanned (4 hours ago)
Scores higher than 92% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 50 of 141 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mustafacagri/vibe-gate-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 602 tokens (~301/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 21 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/vibe-gate-mcp@0.1.12
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mustafacagri/vibe-gate-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mustafacagri/vibe-gate-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3134426891 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a649c5777ca2b200f2d988cdab0156555124e8e712438b07fa612042ef5774f14617f730d01d2c7cd72280b3e8e2ade276bb605f22c200c7ad893b5f5 |
Background: How many MCP packages publish verified provenance →
Dependencies 141 packages
| Packages resolved | 141 |
|---|---|
| Deprecated | 1 |
| Stale | 49 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
log_human_decision Log Human Decision ~148
Last-resort after true DEADLOCK (max Critic rounds). Prefer Implementer↔Critic resubmit. ACCEPT_IMPLEMENTER is rejected while a review session is still open below max rounds.
| Name | Type | Req | Description |
|---|---|---|---|
| caseId | string | yes | Conflict case identifier (usually phaseId) |
| confirmationToken | string | – | Optional. Only if VIBE_HUMAN_CONFIRMATION_TOKEN is set (opt-in). Default flow does not use this — keep AI↔AI debate. |
| decision | string | yes | Rare deadlock only. Prefer another submit_phase_review round. ACCEPT_IMPLEMENTER is blocked while the Critic loop is still open. |
| rationale | string | – | Optional rationale for the decision |
No output schema declared.
No examples provided.
submit_phase_review Submit Phase Review ~454
IDE AI (Implementer) submits a phase completion report for Critic review. Prefer files[] (workspace-relative paths; MCP reads disk and builds FILE:...CONTENT:). Alternatives: semanticDiffPath or inline semanticDiff — exactly one. If CRITIC_PROVIDER is unset, Vibe-Gate selects the first installed local CLI and includes providerNotice in the first result. Set readOnly:true for checks that must not change the workspace. updateStatus:false only skips phase status.
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | – | New/updated package names |
| files | array | – | PREFERRED. Workspace-relative source paths under VIBE_WORKSPACE_ROOT. MCP reads each file and builds FILE:...CONTENT: payload. Exactly one of: files | semanticDiffPath | semanticDiff. Max 10 files. |
| logToDebt | object | – | When DEBT verdict and Implementer accepts, log to DEBT.md |
| phaseId | string | yes | Phase identifier (e.g., phase-6-§1a or 1.1.1) |
| readOnly | boolean | – | When true, do not write or delete workspace state, sessions, debt logs, conflict counts or case files. Overrides updateStatus. Default: false; no durable review round is saved. |
| report | string | yes | Implementer report. MUST INCLUDE: 1. Specific file paths & line numbers. 2. What changed and why. 3. Confirmation that NO "future solutions" or "TODOs" remain (instant fixes only). |
| round | integer | – | Round number (1-3), default 1 |
| semanticDiff | string | – | Inline FILE:...CONTENT: payload. Prefer files[]. Exactly one of: files | semanticDiffPath | semanticDiff. NOT git diff. |
| semanticDiffPath | string | – | Workspace-relative path to a pre-built FILE:...CONTENT: payload file (raw or JSON {"semanticDiff":"..."}). Exactly one of: files | semanticDiffPath | semanticDiff. |
| updateStatus | boolean | – | When false, ACCEPT does not write .vibe/status.json. Default: true except phaseIds with mcp-smoke- / vibe-gate-probe- prefixes. |
No output schema declared.
No examples provided.
How do I install the io.github.mustafacagri/vibe-gate-mcp server?
io.github.mustafacagri/vibe-gate-mcp runs locally as an npm package, launched with npx -y vibe-gate-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vibe-gate-mcp
claude mcp add mustafacagri-vibe-gate-mcp -- npx -y vibe-gate-mcp
What is the io.github.mustafacagri/vibe-gate-mcp server?
io.github.mustafacagri/vibe-gate-mcp is listed in the public MCP registry as io.github.mustafacagri/vibe-gate-mcp. Adversarial Quality Gate MCP for vibe-coding: IDE AI vs Critic AI, human decides on deadlock. This page covers its npm package (vibe-gate-mcp).
Is the io.github.mustafacagri/vibe-gate-mcp server safe to use?
io.github.mustafacagri/vibe-gate-mcp scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mustafacagri/vibe-gate-mcp server expose?
io.github.mustafacagri/vibe-gate-mcp exposes 2 tools: submit_phase_review, log_human_decision. Their descriptions and schemas cost roughly 602 tokens of context every time the server is loaded.
Is the io.github.mustafacagri/vibe-gate-mcp server still maintained?
io.github.mustafacagri/vibe-gate-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mustafacagri/vibe-gate-mcp server under?
io.github.mustafacagri/vibe-gate-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.