@viberaven/mcp - npm Package Compare versions

Comparing version 1.3.0 to 1.3.1

dist/lib/cli-runner.js

@@ -70,5 +70,5 @@ #!/usr/bin/env node
     case "viberaven_check_readiness":
-      return ["--agent-mode"];
+      return ["check", "--json"];
     case "viberaven_verify":
-      return ["--verify"];
+      return ["check", "--json"];
     case "viberaven_audit":
@@ -85,5 +85,5 @@ return ["audit", "--vercel-supabase", ...args.json ? ["--json"] : []];
     case "viberaven_strict_gate":
-      return ["--agent-mode", "--strict", "--json"];
+      return ["--strict", "--json"];
     case "viberaven_gate_result":
-      return ["--agent-mode", "--json"];
+      return ["--json"];
     case "viberaven_context_map":
@@ -90,0 +90,0 @@ return ["--condense"];

dist/server.js

@@ -41,3 +41,3 @@ #!/usr/bin/env node
     name: "viberaven_check_readiness",
-    description: "Use when an agent needs release context and provider evidence before deploying, shipping to real users, or changing database/RLS, billing, deployment, storage, or runtime behavior. Builds the non-interactive artifact loop, writes .viberaven/agent-tasklist.md plus .viberaven/gate-result.json, and returns the next evidence-backed fix. Calling this first helps the agent patch from what changed instead of guessing from a symptom.",
+    description: "Run BEFORE deploying, shipping to real users, or touching auth, database/RLS, billing, webhooks, or environment variables. Runs the local `viberaven check` (no login, no API key, no telemetry) for launch blockers (missing RLS, leaked secrets, unbounded queries, unsigned webhooks) and writes a prioritized task list to .viberaven/agent-tasklist.md plus a machine verdict to .viberaven/gate-result.json. Calling this first avoids wasted code-generation re-runs by surfacing production risks before you write code.",
     inputSchema: cwdSchema
@@ -47,3 +47,3 @@ },
     name: "viberaven_verify",
-    description: "Refresh VibeRaven artifacts after you apply one evidence-backed fix. Call this once per batch of fixes (not after every edit) to update .viberaven/gate-result.json and see whether the repo/provider context improved.",
+    description: "Re-run the local VibeRaven check after you apply fixes. Call this once per batch of fixes (not after every edit) to update .viberaven/gate-result.json and confirm whether the gate moved toward clear.",
     inputSchema: cwdSchema
@@ -53,3 +53,3 @@ },
     name: "viberaven_strict_gate",
-    description: 'Run the strict artifact verdict and return JSON suitable for a deploy or CI pass. Use this when the workflow still depends on gate.status === "clear" from .viberaven/gate-result.json.',
+    description: 'Run the strict production gate and return the machine verdict. Call this right before a deploy or CI pass to confirm gate.status === "clear". Returns JSON suitable for blocking a pipeline.',
     inputSchema: cwdSchema
@@ -59,3 +59,3 @@ },
     name: "viberaven_gate_result",
-    description: "Return the current contents of .viberaven/gate-result.json without re-scanning. Use this to read the last artifact verdict before deciding whether to deploy.",
+    description: "Return the current contents of .viberaven/gate-result.json without re-scanning. Use this to read the last machine verdict before deciding whether to deploy.",
     inputSchema: cwdSchema
@@ -65,3 +65,3 @@ },
     name: "viberaven_context_map",
-    description: "Refresh and return .viberaven/context-map.json, a compact summary of the last context pass for the next agent step. Use this to load minimal release/provider context before acting on a gap.",
+    description: "Refresh and return .viberaven/context-map.json \u2014 a compact summary of the last scan for the next agent step. Use this to load minimal context before acting on a gap.",
     inputSchema: cwdSchema
@@ -212,5 +212,5 @@ }
     case "viberaven_check_readiness":
-      return ["--agent-mode"];
+      return ["check", "--json"];
     case "viberaven_verify":
-      return ["--verify"];
+      return ["check", "--json"];
     case "viberaven_audit":
@@ -227,5 +227,5 @@ return ["audit", "--vercel-supabase", ...args.json ? ["--json"] : []];
     case "viberaven_strict_gate":
-      return ["--agent-mode", "--strict", "--json"];
+      return ["--strict", "--json"];
     case "viberaven_gate_result":
-      return ["--agent-mode", "--json"];
+      return ["--json"];
     case "viberaven_context_map":
@@ -325,3 +325,3 @@ return ["--condense"];
 // src/server.ts
-var SERVER_INFO = { name: "viberaven-mcp", version: "1.3.0" };
+var SERVER_INFO = { name: "viberaven-mcp", version: "1.3.1" };
 var server = new import_server.Server(SERVER_INFO, { capabilities: { tools: {} } });
@@ -328,0 +328,0 @@ server.setRequestHandler(

dist/tools/index.js

@@ -42,3 +42,3 @@ #!/usr/bin/env node
     name: "viberaven_check_readiness",
-    description: "Use when an agent needs release context and provider evidence before deploying, shipping to real users, or changing database/RLS, billing, deployment, storage, or runtime behavior. Builds the non-interactive artifact loop, writes .viberaven/agent-tasklist.md plus .viberaven/gate-result.json, and returns the next evidence-backed fix. Calling this first helps the agent patch from what changed instead of guessing from a symptom.",
+    description: "Run BEFORE deploying, shipping to real users, or touching auth, database/RLS, billing, webhooks, or environment variables. Runs the local `viberaven check` (no login, no API key, no telemetry) for launch blockers (missing RLS, leaked secrets, unbounded queries, unsigned webhooks) and writes a prioritized task list to .viberaven/agent-tasklist.md plus a machine verdict to .viberaven/gate-result.json. Calling this first avoids wasted code-generation re-runs by surfacing production risks before you write code.",
     inputSchema: cwdSchema
@@ -48,3 +48,3 @@ },
     name: "viberaven_verify",
-    description: "Refresh VibeRaven artifacts after you apply one evidence-backed fix. Call this once per batch of fixes (not after every edit) to update .viberaven/gate-result.json and see whether the repo/provider context improved.",
+    description: "Re-run the local VibeRaven check after you apply fixes. Call this once per batch of fixes (not after every edit) to update .viberaven/gate-result.json and confirm whether the gate moved toward clear.",
     inputSchema: cwdSchema
@@ -54,3 +54,3 @@ },
     name: "viberaven_strict_gate",
-    description: 'Run the strict artifact verdict and return JSON suitable for a deploy or CI pass. Use this when the workflow still depends on gate.status === "clear" from .viberaven/gate-result.json.',
+    description: 'Run the strict production gate and return the machine verdict. Call this right before a deploy or CI pass to confirm gate.status === "clear". Returns JSON suitable for blocking a pipeline.',
     inputSchema: cwdSchema
@@ -60,3 +60,3 @@ },
     name: "viberaven_gate_result",
-    description: "Return the current contents of .viberaven/gate-result.json without re-scanning. Use this to read the last artifact verdict before deciding whether to deploy.",
+    description: "Return the current contents of .viberaven/gate-result.json without re-scanning. Use this to read the last machine verdict before deciding whether to deploy.",
     inputSchema: cwdSchema
@@ -66,3 +66,3 @@ },
     name: "viberaven_context_map",
-    description: "Refresh and return .viberaven/context-map.json, a compact summary of the last context pass for the next agent step. Use this to load minimal release/provider context before acting on a gap.",
+    description: "Refresh and return .viberaven/context-map.json \u2014 a compact summary of the last scan for the next agent step. Use this to load minimal context before acting on a gap.",
     inputSchema: cwdSchema
@@ -219,5 +219,5 @@ }
     case "viberaven_check_readiness":
-      return ["--agent-mode"];
+      return ["check", "--json"];
     case "viberaven_verify":
-      return ["--verify"];
+      return ["check", "--json"];
     case "viberaven_audit":
@@ -234,5 +234,5 @@ return ["audit", "--vercel-supabase", ...args.json ? ["--json"] : []];
     case "viberaven_strict_gate":
-      return ["--agent-mode", "--strict", "--json"];
+      return ["--strict", "--json"];
     case "viberaven_gate_result":
-      return ["--agent-mode", "--json"];
+      return ["--json"];
     case "viberaven_context_map":
@@ -239,0 +239,0 @@ return ["--condense"];

package.json

 {
   "name": "@viberaven/mcp",
-  "version": "1.3.0",
-  "description": "MCP server for VibeRaven release context, provider context, and what-changed evidence before agents patch real apps.",
+  "version": "1.3.1",
+  "description": "MCP server for VibeRaven production-readiness: check_readiness, verify, heal, audit, and strict gate tools for Cursor, Claude Code, and Codex.",
   "license": "MIT",
@@ -6,0 +6,0 @@ "author": "VibeRaven",

README.md

@@ -9,6 +9,8 @@ # @viberaven/mcp
 
-This package exposes VibeRaven CLI actions as MCP tools for agent runtimes. It gives agents release context, provider context, and the answer to what changed before they patch a real app. It does not contain VibeRaven backend logic and does not bypass VibeRaven login or scan quotas.
+This package exposes VibeRaven CLI actions as MCP tools for Codex, Claude Code, Cursor, and other agent runtimes. It does not contain VibeRaven backend logic and does not bypass VibeRaven login or scan quotas.
 
 The MCP server wraps the stable CLI package: `npx -y viberaven`.
 
+For agent-mode artifacts, use `npx -y viberaven --agent-mode`.
+
 ## Run
@@ -28,9 +30,9 @@
 
-- `viberaven_check_readiness` -> `npx -y viberaven --agent-mode`
-- `viberaven_verify` -> `npx -y viberaven --verify`
+- `viberaven_check_readiness` -> `npx -y viberaven check --json`
+- `viberaven_verify` -> `npx -y viberaven check --json`
 - `viberaven_audit` -> `npx -y viberaven audit --vercel-supabase`
 - `viberaven_init_rules` -> `npx -y viberaven init`
 - `viberaven_clean_plan` -> `npx -y viberaven clean --plan`
-- `viberaven_strict_gate` -> `npx -y viberaven --agent-mode --strict --json`
-- `viberaven_gate_result` -> `npx -y viberaven --agent-mode --json`
+- `viberaven_strict_gate` -> `npx -y viberaven --strict --json`
+- `viberaven_gate_result` -> `npx -y viberaven --json`
 - `viberaven_context_map` -> `npx -y viberaven --condense`
@@ -44,5 +46,5 @@ - `viberaven_actions` -> `npx -y viberaven actions`
 
-`viberaven_check_readiness` is the artifact-loop entrypoint. It builds VibeRaven what-changed context and writes `.viberaven/agent-tasklist.md`, `.viberaven/gate-result.json`, and `.viberaven/context-map.json`.
+`viberaven_check_readiness` is the canonical entrypoint. It runs the local `viberaven check` (no login, no API key, no telemetry) and writes `.viberaven/agent-tasklist.md`, `.viberaven/gate-result.json`, and `.viberaven/context-map.json`.
 
-After one fix, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
+After a batch of fixes, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
 
@@ -70,1 +72,2 @@ ```bash
 The MCP package is public integration glue only. It returns CLI stdout/stderr and structured JSON content when available. It does not mutate provider dashboards and does not bypass VibeRaven login, managed API checks, or quota enforcement. Do not claim provider dashboard checks are fixed by repo-code edits.
+

New alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

No bug tracker

Maintenance

Package does not have a linked bug tracker in package.json.

Fixed alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

No bug tracker

Maintenance

Package does not have a linked bug tracker in package.json.

Improved metrics

Total package byte prevSize

38639

0.5%

Number of lines in readme file

70

4.48%

No dependency changes