@viberaven/mcp 1.2.0 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +66 -67
  2. package/dist/server.js +6 -6
  3. package/dist/tools/index.js +5 -5
  4. package/package.json +56 -56
package/README.md CHANGED
@@ -1,67 +1,66 @@
1
- # @viberaven/mcp
2
-
3
- [![npm version](https://img.shields.io/npm/v/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
4
- [![npm downloads](https://img.shields.io/npm/dw/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
5
- [![license](https://img.shields.io/npm/l/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
6
-
7
- Thin MCP wrapper for VibeRaven.
8
-
9
- 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.
10
-
11
- The MCP server wraps the stable CLI package: `npx -y viberaven`.
12
-
13
- ## Run
14
-
15
- ```bash
16
- npx -y @viberaven/mcp
17
- ```
18
-
19
- You can also start the MCP server from the main CLI package:
20
-
21
- ```bash
22
- npx -y viberaven mcp
23
- ```
24
-
25
- ## Tools
26
-
27
- - `viberaven_check_readiness` -> `npx -y viberaven --agent-mode`
28
- - `viberaven_verify` -> `npx -y viberaven --verify`
29
- - `viberaven_audit` -> `npx -y viberaven audit --vercel-supabase`
30
- - `viberaven_init_rules` -> `npx -y viberaven init`
31
- - `viberaven_clean_plan` -> `npx -y viberaven clean --plan`
32
- - `viberaven_strict_gate` -> `npx -y viberaven --agent-mode --strict --json`
33
- - `viberaven_gate_result` -> `npx -y viberaven --agent-mode --json`
34
- - `viberaven_context_map` -> `npx -y viberaven --condense`
35
- - `viberaven_actions` -> `npx -y viberaven actions`
36
- - `viberaven_verify_action` -> `npx -y viberaven verify --action <id>`
37
- - `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
38
- - `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
39
- - `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
40
- - `viberaven_validate_npm_package` -> `npx -y viberaven validate-npm-package --json`
41
-
42
- `viberaven_check_readiness` is the canonical entrypoint. It runs VibeRaven as the Agent Context + Production Gate and writes `.viberaven/agent-tasklist.md`, `.viberaven/gate-result.json`, and `.viberaven/context-map.json`.
43
-
44
- After one fix, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
45
-
46
- ```bash
47
- npx -y viberaven --strict
48
- ```
49
-
50
- ## Machine Artifact Contract
51
-
52
- ```text
53
- docs/contracts/artifacts.md
54
- https://viberaven.dev/schemas/gate-result.schema.json
55
- https://viberaven.dev/schemas/context-map.schema.json
56
- https://viberaven.dev/schemas/gap.schema.json
57
- https://viberaven.dev/schemas/heal-result.schema.json
58
- ```
59
-
60
- ## Login
61
-
62
- 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.
63
-
64
- ## Security
65
-
66
- 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.
67
-
1
+ # @viberaven/mcp
2
+
3
+ [![npm version](https://img.shields.io/npm/v/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
4
+ [![npm downloads](https://img.shields.io/npm/dw/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
5
+ [![license](https://img.shields.io/npm/l/@viberaven/mcp)](https://www.npmjs.com/package/@viberaven/mcp)
6
+
7
+ Thin MCP wrapper for VibeRaven.
8
+
9
+ 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.
10
+
11
+ The MCP server wraps the stable CLI package: `npx -y viberaven`.
12
+
13
+ ## Run
14
+
15
+ ```bash
16
+ npx -y @viberaven/mcp
17
+ ```
18
+
19
+ You can also start the MCP server from the main CLI package:
20
+
21
+ ```bash
22
+ npx -y viberaven mcp
23
+ ```
24
+
25
+ ## Tools
26
+
27
+ - `viberaven_check_readiness` -> `npx -y viberaven --agent-mode`
28
+ - `viberaven_verify` -> `npx -y viberaven --verify`
29
+ - `viberaven_audit` -> `npx -y viberaven audit --vercel-supabase`
30
+ - `viberaven_init_rules` -> `npx -y viberaven init`
31
+ - `viberaven_clean_plan` -> `npx -y viberaven clean --plan`
32
+ - `viberaven_strict_gate` -> `npx -y viberaven --agent-mode --strict --json`
33
+ - `viberaven_gate_result` -> `npx -y viberaven --agent-mode --json`
34
+ - `viberaven_context_map` -> `npx -y viberaven --condense`
35
+ - `viberaven_actions` -> `npx -y viberaven actions`
36
+ - `viberaven_verify_action` -> `npx -y viberaven verify --action <id>`
37
+ - `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
38
+ - `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
39
+ - `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
40
+ - `viberaven_validate_npm_package` -> `npx -y viberaven validate-npm-package --json`
41
+
42
+ `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`.
43
+
44
+ After one fix, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
45
+
46
+ ```bash
47
+ npx -y viberaven --strict
48
+ ```
49
+
50
+ ## Machine Artifact Contract
51
+
52
+ ```text
53
+ docs/contracts/artifacts.md
54
+ https://viberaven.dev/schemas/gate-result.schema.json
55
+ https://viberaven.dev/schemas/context-map.schema.json
56
+ https://viberaven.dev/schemas/gap.schema.json
57
+ https://viberaven.dev/schemas/heal-result.schema.json
58
+ ```
59
+
60
+ ## Login
61
+
62
+ 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.
63
+
64
+ ## Security
65
+
66
+ 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/server.js CHANGED
@@ -38,27 +38,27 @@ var cwdSchema = {
38
38
  var readinessTools = [
39
39
  {
40
40
  name: "viberaven_check_readiness",
41
- description: "Run BEFORE deploying, shipping to real users, or touching auth, database/RLS, billing, webhooks, or environment variables. Scans the repo 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. Returns the gate status and the single next fix. Calling this first avoids wasted code-generation re-runs by surfacing production risks before you write code.",
41
+ 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.",
42
42
  inputSchema: cwdSchema
43
43
  },
44
44
  {
45
45
  name: "viberaven_verify",
46
- description: "Re-scan and refresh VibeRaven readiness artifacts after you apply one fix. 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.",
46
+ 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.",
47
47
  inputSchema: cwdSchema
48
48
  },
49
49
  {
50
50
  name: "viberaven_strict_gate",
51
- 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.',
51
+ 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.',
52
52
  inputSchema: cwdSchema
53
53
  },
54
54
  {
55
55
  name: "viberaven_gate_result",
56
- 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.",
56
+ 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.",
57
57
  inputSchema: cwdSchema
58
58
  },
59
59
  {
60
60
  name: "viberaven_context_map",
61
- 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.",
61
+ 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.",
62
62
  inputSchema: cwdSchema
63
63
  }
64
64
  ];
@@ -315,7 +315,7 @@ async function handleRequest(method, params) {
315
315
  }
316
316
 
317
317
  // src/server.ts
318
- var SERVER_INFO = { name: "viberaven-mcp", version: "1.2.0" };
318
+ var SERVER_INFO = { name: "viberaven-mcp", version: "1.3.0" };
319
319
  var server = new import_server.Server(SERVER_INFO, { capabilities: { tools: {} } });
320
320
  server.setRequestHandler(
321
321
  import_types.ListToolsRequestSchema,
package/dist/tools/index.js CHANGED
@@ -39,27 +39,27 @@ var cwdSchema = {
39
39
  var readinessTools = [
40
40
  {
41
41
  name: "viberaven_check_readiness",
42
- description: "Run BEFORE deploying, shipping to real users, or touching auth, database/RLS, billing, webhooks, or environment variables. Scans the repo 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. Returns the gate status and the single next fix. Calling this first avoids wasted code-generation re-runs by surfacing production risks before you write code.",
42
+ 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.",
43
43
  inputSchema: cwdSchema
44
44
  },
45
45
  {
46
46
  name: "viberaven_verify",
47
- description: "Re-scan and refresh VibeRaven readiness artifacts after you apply one fix. 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.",
47
+ 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.",
48
48
  inputSchema: cwdSchema
49
49
  },
50
50
  {
51
51
  name: "viberaven_strict_gate",
52
- 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.',
52
+ 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.',
53
53
  inputSchema: cwdSchema
54
54
  },
55
55
  {
56
56
  name: "viberaven_gate_result",
57
- 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.",
57
+ 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.",
58
58
  inputSchema: cwdSchema
59
59
  },
60
60
  {
61
61
  name: "viberaven_context_map",
62
- 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.",
62
+ 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.",
63
63
  inputSchema: cwdSchema
64
64
  }
65
65
  ];
package/package.json CHANGED
@@ -1,56 +1,56 @@
1
- {
2
- "name": "@viberaven/mcp",
3
- "version": "1.2.0",
4
- "description": "MCP server for VibeRaven production-readiness: check_readiness, verify, heal, audit, and strict gate tools for Cursor, Claude Code, and Codex.",
5
- "license": "MIT",
6
- "author": "VibeRaven",
7
- "mcpName": "io.github.ohad6k/viberaven",
8
- "homepage": "https://viberaven.dev/mcp.md",
9
- "repository": {
10
- "type": "git",
11
- "url": "git+https://github.com/ohad6k/VibeRaven.git",
12
- "directory": "packages/mcp"
13
- },
14
- "bugs": {
15
- "url": "https://github.com/ohad6k/VibeRaven/issues"
16
- },
17
- "keywords": [
18
- "viberaven",
19
- "mcp",
20
- "claude-code",
21
- "codex",
22
- "cursor",
23
- "launch-readiness",
24
- "production"
25
- ],
26
- "publishConfig": {
27
- "access": "public",
28
- "tag": "latest"
29
- },
30
- "bin": {
31
- "viberaven-mcp": "dist/server.js"
32
- },
33
- "files": [
34
- "dist",
35
- "README.md"
36
- ],
37
- "engines": {
38
- "node": ">=20"
39
- },
40
- "scripts": {
41
- "build": "node scripts/build.mjs",
42
- "typecheck": "tsc -p tsconfig.json --noEmit",
43
- "presmoke": "npm run build",
44
- "smoke": "node scripts/smoke.mjs",
45
- "pretest": "npm run build",
46
- "test": "vitest run"
47
- },
48
- "dependencies": {
49
- "@modelcontextprotocol/sdk": "^1.0.0"
50
- },
51
- "devDependencies": {
52
- "esbuild": "^0.25.0",
53
- "typescript": "^5.8.0",
54
- "vitest": "^3.2.0"
55
- }
56
- }
1
+ {
2
+ "name": "@viberaven/mcp",
3
+ "version": "1.3.0",
4
+ "description": "MCP server for VibeRaven release context, provider context, and what-changed evidence before agents patch real apps.",
5
+ "license": "MIT",
6
+ "author": "VibeRaven",
7
+ "mcpName": "io.github.ohad6k/viberaven",
8
+ "homepage": "https://viberaven.dev/mcp.md",
9
+ "repository": {
10
+ "type": "git",
11
+ "url": "git+https://github.com/ohad6k/VibeRaven.git",
12
+ "directory": "packages/mcp"
13
+ },
14
+ "bugs": {
15
+ "url": "https://github.com/ohad6k/VibeRaven/issues"
16
+ },
17
+ "keywords": [
18
+ "viberaven",
19
+ "mcp",
20
+ "claude-code",
21
+ "codex",
22
+ "cursor",
23
+ "launch-readiness",
24
+ "production"
25
+ ],
26
+ "publishConfig": {
27
+ "access": "public",
28
+ "tag": "latest"
29
+ },
30
+ "bin": {
31
+ "viberaven-mcp": "dist/server.js"
32
+ },
33
+ "files": [
34
+ "dist",
35
+ "README.md"
36
+ ],
37
+ "engines": {
38
+ "node": ">=20"
39
+ },
40
+ "scripts": {
41
+ "build": "node scripts/build.mjs",
42
+ "typecheck": "tsc -p tsconfig.json --noEmit",
43
+ "presmoke": "npm run build",
44
+ "smoke": "node scripts/smoke.mjs",
45
+ "pretest": "npm run build",
46
+ "test": "vitest run"
47
+ },
48
+ "dependencies": {
49
+ "@modelcontextprotocol/sdk": "^1.0.0"
50
+ },
51
+ "devDependencies": {
52
+ "esbuild": "^0.25.0",
53
+ "typescript": "^5.8.0",
54
+ "vitest": "^3.2.0"
55
+ }
56
+ }