@viberaven/mcp 1.5.1 → 1.5.2

package/README.md

@@ -1,69 +1,65 @@
-# @viberaven/mcp
-
-[![npm version](https://img.shields.io/npm/v/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
-[![npm downloads](https://img.shields.io/npm/dw/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
-[![license](https://img.shields.io/npm/l/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
-
-Thin MCP wrapper for VibeRaven.
-
-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
-
-```bash
-npx -y @viberaven/mcp
-```
-
-You can also start the MCP server from the main CLI package:
-
-```bash
-npx -y viberaven mcp
-```
-
-## Tools
-
-- `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 --strict --json`
-- `viberaven_gate_result` -> `npx -y viberaven --json`
-- `viberaven_context_map` -> `npx -y viberaven --condense`
-- `viberaven_actions` -> `npx -y viberaven actions`
-- `viberaven_verify_action` -> `npx -y viberaven verify --action <id>`
-- `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
-- `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
-- `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
-- `viberaven_validate_npm_package` -> `npx -y viberaven validate-npm-package --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 a batch of fixes, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
-
-```bash
-npx -y viberaven --strict
-```
-
-## Machine Artifact Contract
-
-```text
-docs/contracts/artifacts.md
-https://viberaven.dev/schemas/gate-result.schema.json
-https://viberaven.dev/schemas/context-map.schema.json
-https://viberaven.dev/schemas/gap.schema.json
-https://viberaven.dev/schemas/heal-result.schema.json
-```
-
-## Login
-
-If VibeRaven prints `LOGIN_URL_READY`, open that exact URL for the user, keep the MCP call alive, and do not ask for passwords, tokens, cookies, or other secrets.
-
-## Security
-
-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.
-
+# @viberaven/mcp
+
+[![npm version](https://img.shields.io/npm/v/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
+[![npm downloads](https://img.shields.io/npm/dw/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
+[![license](https://img.shields.io/npm/l/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
+
+Thin MCP wrapper for VibeRaven.
+
+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
+
+```bash
+npx -y @viberaven/mcp
+```
+
+This package is the only MCP entrypoint in 1.5.2. The main `viberaven` CLI package does not start an MCP server.
+
+## Tools
+
+- `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`: writes and returns a context cleanup review plan; deletes nothing (fixed in 1.5.2)
+- `viberaven_strict_gate` -> `npx -y viberaven --strict --json`
+- `viberaven_gate_result` -> `npx -y viberaven --json`
+- `viberaven_context_map` -> `npx -y viberaven --condense`
+- `viberaven_actions` -> `npx -y viberaven actions`
+- `viberaven_verify_action` -> `npx -y viberaven verify --action <id>`
+- `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
+- `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
+- `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
+- `viberaven_validate_npm_package` -> `npx -y viberaven validate-npm-package --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 a batch of fixes, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
+
+```bash
+npx -y viberaven --strict
+```
+
+## Machine Artifact Contract
+
+```text
+docs/contracts/artifacts.md
+https://viberaven.dev/schemas/gate-result.schema.json
+https://viberaven.dev/schemas/context-map.schema.json
+https://viberaven.dev/schemas/gap.schema.json
+https://viberaven.dev/schemas/heal-result.schema.json
+```
+
+## Login
+
+If VibeRaven prints `LOGIN_URL_READY`, open that exact URL for the user, keep the MCP call alive, and do not ask for passwords, tokens, cookies, or other secrets.
+
+## Security
+
+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.
+

package/dist/lib/cli-runner.js

@@ -52,7 +52,7 @@ function mcpVersion() {
     } catch {
     }
   }
-  found ??= true ? "1.5.1" : void 0;
+  found ??= true ? "1.5.2" : void 0;
   if (!found || !PLAIN_VERSION.test(found)) {
     throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
   }

package/dist/server.js

@@ -191,7 +191,7 @@ function mcpVersion() {
     } catch {
     }
   }
-  found ??= true ? "1.5.1" : void 0;
+  found ??= true ? "1.5.2" : void 0;
   if (!found || !PLAIN_VERSION.test(found)) {
     throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
   }
@@ -361,7 +361,7 @@ async function handleRequest(method, params) {
 }
 
 // src/server.ts
-var SERVER_INFO = { name: "viberaven-mcp", version: "1.5.1" };
+var SERVER_INFO = { name: "viberaven-mcp", version: "1.5.2" };
 var server = new import_server.Server(SERVER_INFO, { capabilities: { tools: {} } });
 server.setRequestHandler(
   import_types.ListToolsRequestSchema,

package/dist/tools/index.js

@@ -192,7 +192,7 @@ function mcpVersion() {
     } catch {
     }
   }
-  found ??= true ? "1.5.1" : void 0;
+  found ??= true ? "1.5.2" : void 0;
   if (!found || !PLAIN_VERSION.test(found)) {
     throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viberaven/mcp",
-  "version": "1.5.1",
+  "version": "1.5.2",
   "description": "MCP server for VibeRaven production-readiness: check_readiness, verify, heal, audit, and strict gate tools for Cursor, Claude Code, and Codex.",
   "license": "MIT",
   "author": "VibeRaven",