@viberaven/mcp 1.6.4 → 1.6.6

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.
package/README.md CHANGED
@@ -1,65 +1,91 @@
1
1
  # @viberaven/mcp
2
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)
3
+ A deployed app can still lack Supabase row level security (RLS). This MCP server lets an agent inspect repository evidence, read tasks and recheck after fixes.
6
4
 
7
- Thin MCP wrapper for VibeRaven.
5
+ Check AI-built Vercel + Supabase apps before launch/handoff, after migration/policy changes, or for production RLS, environment, database connection, service-role or Stripe webhook failures. Findings include permissive policies, browser-exposed service-role keys, environment-template drift and unsigned Stripe handlers.
8
6
 
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.
7
+ ## Connect Your Host
10
8
 
11
- The MCP server wraps the stable CLI package: `npx -y viberaven`.
9
+ Requires Node.js 20 or newer. Transport is **stdio**. Adapt this example to your host's configuration format:
12
10
 
13
- For agent-mode artifacts, use `npx -y viberaven --agent-mode`.
11
+ ```json
12
+ {
13
+ "mcpServers": {
14
+ "viberaven": {
15
+ "command": "npx",
16
+ "args": ["-y", "@viberaven/mcp@1.6.6"]
17
+ }
18
+ }
19
+ }
20
+ ```
14
21
 
15
- ## Run
22
+ On Windows, hosts launching executables directly can use:
23
+
24
+ ```json
25
+ {
26
+ "mcpServers": {
27
+ "viberaven": {
28
+ "command": "cmd.exe",
29
+ "args": ["/d", "/s", "/c", "npx", "-y", "@viberaven/mcp@1.6.6"]
30
+ }
31
+ }
32
+ }
33
+ ```
16
34
 
17
- ```bash
18
- npx -y @viberaven/mcp
35
+ Reconnect, confirm tools appear, then pass the app root:
36
+
37
+ ```json
38
+ {
39
+ "name": "viberaven_check_readiness",
40
+ "arguments": { "cwd": "/absolute/path/to/your-app" }
41
+ }
19
42
  ```
20
43
 
21
- This package is the only MCP entrypoint in 1.6.4. The main `viberaven` CLI package does not start an MCP server.
44
+ Use `C:/projects/your-app` on Windows. Omitted `cwd` means the server startup directory; npm validation accepts no `cwd`. This server invokes matching `@viberaven/cli@1.6.6` through npx. Scans need no VibeRaven login/API key; downloads and npm validation need network.
22
45
 
23
- ## Tools
46
+ ## The 14 Tools
24
47
 
25
- - `viberaven_check_readiness` -> `npx -y viberaven check --json`
26
- - `viberaven_verify` -> `npx -y viberaven check --json`
27
- - `viberaven_audit` -> `npx -y viberaven audit --vercel-supabase`
28
- - `viberaven_init_rules` -> `npx -y viberaven init`
29
- - `viberaven_clean_plan` -> `npx -y viberaven clean --plan`: writes and returns a context cleanup review plan; deletes nothing (fixed in 1.5.2)
30
- - `viberaven_strict_gate` -> `npx -y viberaven --strict --json`
31
- - `viberaven_gate_result` -> `npx -y viberaven --json`
32
- - `viberaven_context_map` -> `npx -y viberaven --condense`
33
- - `viberaven_actions` -> `npx -y viberaven actions`
34
- - `viberaven_verify_action` -> `npx -y viberaven --verify --action <id>`
35
- - `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
36
- - `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
37
- - `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
38
- - `viberaven_validate_npm_package` -> `npx -y viberaven validate-npm-package --json`
48
+ | Tool | CLI operation |
49
+ | --- | --- |
50
+ | `viberaven_check_readiness` | `check --json`: fresh check, summary and artifact paths |
51
+ | `viberaven_verify` | `check --json`: recheck after a batch of fixes |
52
+ | `viberaven_audit` | `audit --vercel-supabase`; optional `json: true` |
53
+ | `viberaven_init_rules` | `init`: native instructions; preview with `dryRun: true` |
54
+ | `viberaven_clean_plan` | `clean --plan`: write a cleanup plan, deletes nothing |
55
+ | `viberaven_strict_gate` | `--strict --json`: fresh scan with full gate JSON |
56
+ | `viberaven_gate_result` | `--json`: fresh scan, not an older result |
57
+ | `viberaven_context_map` | `--condense`: refresh context from the last scan |
58
+ | `viberaven_actions` | `actions`: current actions and follow-ups |
59
+ | `viberaven_verify_action` | `--verify --action <actionId>` |
60
+ | `viberaven_heal_plan` | `--heal --plan`: review a supported fix |
61
+ | `viberaven_heal_prompt` | `--heal --prompt`: guidance for the coding agent |
62
+ | `viberaven_heal_apply` | `--heal --apply`: supported repository recipe |
63
+ | `viberaven_validate_npm_package` | `validate-npm-package --json`: `packageName` or `packageNames`; not a package security review |
39
64
 
40
- `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`.
65
+ Responses contain `exit N`, CLI output and parseable JSON objects as structured content. Blocker exit 1 can be normal tool content.
41
66
 
42
- After a batch of fixes, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
67
+ ## Work The Result
43
68
 
44
- ```bash
45
- npx -y viberaven --strict
46
- ```
69
+ Readiness refreshes `.viberaven/agent-tasklist.md`, `gate-result.json` and `context-map.json` without patching source. Read tasks/source, review `viberaven_heal_plan` before apply, and recheck each batch with `viberaven_verify`. Provider steps require provider evidence.
47
70
 
48
- ## Machine Artifact Contract
71
+ The `rls_disabled` migration enables RLS without policies; browser roles lose row access until policies exist. Obtain agreement before apply and `yes: true`. Apply/test through your database workflow.
49
72
 
50
- ```text
51
- docs/contracts/artifacts.md
52
- https://viberaven.dev/schemas/gate-result.schema.json
53
- https://viberaven.dev/schemas/context-map.schema.json
54
- https://viberaven.dev/schemas/gap.schema.json
55
- https://viberaven.dev/schemas/heal-result.schema.json
56
- ```
73
+ Readiness prints a summary. Read `gate-result.json` or call `viberaven_gate_result`/`viberaven_strict_gate` for full `gate.status`.
74
+
75
+ Default check allows warnings: 0 without critical blockers, 1 with blockers, 2 on scan error. Strict gate returns 0 for `clear`/`warning`, 1 for `not_clear`, 2 for `error`, 3 for `unknown` or unavailable results. For warning failures, run `npx -y viberaven@1.6.6 --strict=warning --json` from the app root. Unrestricted SELECT can be intentional public content and is a default warning; focused audit returns 1 for any status other than `pass`.
76
+
77
+ ## Studio And Optional Artifact Mode
57
78
 
58
- ## Login
79
+ From the app root: `npx -y viberaven@1.6.6` opens Studio; `npx -y viberaven@1.6.6 check` checks. Chat needs an installed/authenticated coding CLI and **Test connection**.
59
80
 
60
- 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.
81
+ Artifact compatibility command:
82
+
83
+ ```bash
84
+ npx -y viberaven --agent-mode
85
+ ```
61
86
 
62
- ## Security
87
+ ## Scope And Evidence
63
88
 
64
- 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.
89
+ Checks do not query live policies, prove complete permissions, build or deploy. With RLS off, grants determine actual access. Verify live user access, provider environment, DNS, billing and webhooks separately. A clear result is not a security audit.
65
90
 
91
+ The [RLS comparison](https://ohad6k.github.io/VibeRaven/examples/proof/rls-comparison/) retains maintainer-authored **1.6.3** runs in local databases, not new scans, hosted Supabase verification or independent endorsement. [Public repository](https://github.com/ohad6k/VibeRaven) | [Agent reference](https://ohad6k.github.io/VibeRaven/llms.txt). License: MIT.
@@ -52,7 +52,7 @@ function mcpVersion() {
52
52
  } catch {
53
53
  }
54
54
  }
55
- found ??= true ? "1.6.4" : void 0;
55
+ found ??= true ? "1.6.6" : void 0;
56
56
  if (!found || !PLAIN_VERSION.test(found)) {
57
57
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
58
58
  }
package/dist/server.js CHANGED
@@ -192,7 +192,7 @@ function mcpVersion() {
192
192
  } catch {
193
193
  }
194
194
  }
195
- found ??= true ? "1.6.4" : void 0;
195
+ found ??= true ? "1.6.6" : void 0;
196
196
  if (!found || !PLAIN_VERSION.test(found)) {
197
197
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
198
198
  }
@@ -362,7 +362,7 @@ async function handleRequest(method, params) {
362
362
  }
363
363
 
364
364
  // src/server.ts
365
- var SERVER_INFO = { name: "viberaven-mcp", version: "1.6.4" };
365
+ var SERVER_INFO = { name: "viberaven-mcp", version: "1.6.6" };
366
366
  var INSTRUCTIONS = [
367
367
  "VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase.",
368
368
  "Suggest one viberaven_check_readiness run before such an app launches or is handed off, after a Supabase migration or policy change,",
@@ -192,7 +192,7 @@ function mcpVersion() {
192
192
  } catch {
193
193
  }
194
194
  }
195
- found ??= true ? "1.6.4" : void 0;
195
+ found ??= true ? "1.6.6" : void 0;
196
196
  if (!found || !PLAIN_VERSION.test(found)) {
197
197
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
198
198
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@viberaven/mcp",
3
- "version": "1.6.4",
3
+ "version": "1.6.6",
4
4
  "description": "MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.",
5
5
  "license": "MIT",
6
6
  "author": "VibeRaven",