@viberaven/mcp 1.6.12 → 1.7.1

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/LICENSE CHANGED
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 VibeRaven
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 VibeRaven
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -41,13 +41,14 @@ Reconnect, confirm tools appear, then pass the app root:
41
41
  }
42
42
  ```
43
43
 
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.12` through npx. Scans need no VibeRaven login/API key; downloads and npm validation need network.
44
+ Use `C:/projects/your-app` on Windows. Omitted `cwd` means the server startup directory; npm validation accepts no `cwd`. This server prefers a matching CLI installed alongside the MCP and otherwise invokes the exact matching version through npx. Scans need no VibeRaven login/API key; downloads and npm validation need network.
45
45
 
46
- ## The 14 Tools
46
+ ## Repository tools
47
47
 
48
48
  | Tool | CLI operation |
49
49
  | --- | --- |
50
50
  | `viberaven_check_readiness` | `check --json`: fresh check, summary and artifact paths |
51
+ | `viberaven_rls_test` | Experimental `rls-test --json --matrix <path>`; optional `migrations` directory |
51
52
  | `viberaven_verify` | `check --json`: recheck after a batch of fixes |
52
53
  | `viberaven_audit` | `audit --vercel-supabase`; optional `json: true` |
53
54
  | `viberaven_init_rules` | `init`: native instructions; preview with `dryRun: true` |
@@ -64,6 +65,22 @@ Use `C:/projects/your-app` on Windows. Omitted `cwd` means the server startup di
64
65
 
65
66
  Responses contain `exit N`, CLI output and parseable JSON objects as structured content. Blocker exit 1 can be normal tool content.
66
67
 
68
+ ### Optional local behavioral RLS test (local candidate)
69
+
70
+ After reviewing the intended access in a permissions matrix, a local candidate host that lists `viberaven_rls_test` can run:
71
+
72
+ ```json
73
+ {"name":"viberaven_rls_test","arguments":{"cwd":"/absolute/path/to/app","matrix":"reviewed.permissions.json"}}
74
+ ```
75
+
76
+ This reuses the CLI's experimental PGlite imitation for owner, other_user and anon. Prefer `defaultGrants: none` with actual GRANT SQL for new schemas; disclose legacy defaults otherwise. Review expected access before running, and keep it unchanged while fixing a failure. Read Pass/Fail/Unknown and coverage: valid findings (exit 1) and inconclusive results (exit 2) retain their structured evidence. Unknown is inconclusive. Invalid/missing matrices, missing engine, failed migrations/role checks and malformed or inconsistent receipts are tool errors. Local observations do not prove live Supabase behavior or security.
77
+
78
+ Completed RLS results keep the complete receipt in both compact JSON text and `structuredContent`; only JSON formatting whitespace is removed. All evidence fields and stderr diagnostics remain available. Error diagnostics keep their original text.
79
+
80
+ RLS calls stop after 300 seconds or 8 MiB of combined child output. A stopped run terminates the CLI and returns a tool error without a partial passing receipt.
81
+
82
+ Use an already installed matching candidate CLI with optional `@electric-sql/pglite@0.5.8` next to it, configured for this local MCP host as described below. Installing PGlite only in the target project may not make it visible to the host CLI. The RLS route requires this installed CLI and never falls back to npx. Missing host setup returns setup guidance without spawning; missing PGlite returns the existing CLI guidance. The tool does not install dependencies, accept SQL/credentials or access a provider. Obtain normal user authorization before installing dependencies. The installed CLI fallback is `viberaven rls-test --matrix PATH --json`; this candidate tool is not assumed to exist in the published MCP version shown above.
83
+
67
84
  ## Work The Result
68
85
 
69
86
  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.
@@ -81,7 +98,7 @@ From the app root: `npx -y viberaven@1.6.12` opens Studio; `npx -y viberaven@1.6
81
98
  Artifact compatibility command:
82
99
 
83
100
  ```bash
84
- npx -y viberaven --agent-mode
101
+ npx -y viberaven check
85
102
  ```
86
103
 
87
104
  ## Scope And Evidence
@@ -89,3 +106,9 @@ npx -y viberaven --agent-mode
89
106
  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.
90
107
 
91
108
  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.
109
+
110
+ ### Standalone MCP installation boundary
111
+
112
+ For `viberaven_work_report`, standalone MCP resolves an already installed `@viberaven/cli/package.json` from the MCP installation, and requires its name and exact version to match the MCP candidate. Alternatively, set the host process environment `VIBERAVEN_CLI_PATH` to an absolute matching `dist/cli.js` path. This is an operator-controlled local-candidate setting, not a tool argument. Keep the CLI installation outside the task repository. A regular canonical CLI entry and adjacent manifest are validated before execution.
113
+
114
+ Report runs Node directly with `shell: false`, strips Node/npm environment steering and never invokes npm, npx, package installation or registry fallback. Install/configure the matching candidate separately; reporting fails until it is available. Missing/mismatched installations, process failures, malformed results, output over the bounded transport budget and the 30-second read timeout return a generic error without raw child diagnostics or local paths. Standalone MCP tools other than RLS tests and reports use the same installation validation and direct Node execution when a matching host CLI is available; otherwise they retain exact-version pinned npx fallback. An explicitly invalid `VIBERAVEN_CLI_PATH` fails without fallback. Task-local packages and symlinked entries are not trusted. Transport failures and missing/malformed JSON on JSON routes set MCP `isError`; completed checks with findings remain normal structured content. The source-level embedded MCP compatibility handler uses its own CLI entry with the same shared bounded report runner. It has parity/regression tests but is not exposed as a second installed CLI server entrypoint; the executable MCP route is `@viberaven/mcp`.