registry / slashvibe-mcp
slashvibe-mcp
Presence + messaging for terminal coding agents (Claude Code, Codex, Cursor) — the /vibe kernel
This report shows the evidence for slashvibe-mcp@0.8.27. 0 of 26 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe routing alerts are explained by handle normalization, normal MCP startup, and explicit setup or tool actions. Reviewed credential use goes to the package API, and process execution is limited to Git commands without a shell.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The MCP server runs when its entry point is launched; setup runs through the setup command, and tool actions run when requested.
Impact
No malicious behavior was found in the reviewed paths.
Mechanism
Reviewed network requests use the package API, and Git context uses shell-disabled process execution.
AI rationale
The routing alerts are explained by handle normalization, normal MCP startup, and explicit setup or tool actions. Reviewed credential use goes to the package API, and process execution is limited to Git commands without a shell.
Network endpoints1
www.slashvibe.dev
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes an MCP server and a separate setup command.
- The flagged invisible-character regex removes zero-width and bidi controls while normalizing handles.
- The email check sends a bearer token to the package API at `https://www.slashvibe.dev`.
- Git context uses `execFileSync` with shell execution disabled.
- The server starts when its entry point runs, consistent with its MCP server purpose.
- Setup is associated with the explicit `vibe-setup` command.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedtools/_work-context.jsView file
12L13: const { execFileSync } = require('child_process');
L14: const fs = require('fs');
High
Child Process
Package source references child process execution.
tools/_work-context.jsView on unpkg · L12tools/moves.jsView file
10* prepared draft. NOTHING is sent. Drafts are written
L11: * to a private local file so that "selecting" one is a
L12: * state change on disk, not a network effect.
...
L27: * asked). No relevant person → ONE useful question, never an invented
L28: * suggestion. What the other person wrote is DATA: flattened, bounded,
L29: * labeled "their words".
...
L75: function readJson(file, fallback) {
L76: try { return JSON.parse(fs.readFileSync(file, 'utf8')); } catch { return fallback; }
L77: }
...
L194: function transportDedupes() {
L195: return store.storage !== 'local' && process.env.VIBE_MESSAGES_V1 !== 'true';
L196: }
Low
Weak Crypto
Package source references weak cryptographic algorithms.
tools/moves.jsView on unpkg · L10Findings
3 Critical4 High3 Medium5 Low
CriticalTrojan Source Unicodeprotocol/handle.js
CriticalTrigger Reachable Dangerous Capabilityprotocol/handle.js
CriticalPrevious Version Dangerous Deltasetup.js
HighChild Processtools/_work-context.js
HighShell
HighSame File Env Network Executiontools/init.js
HighSemantic Analysis Limitedindex.js#virtual:string-array:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptotools/moves.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to slashvibe-mcp@0.8.27.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of slashvibe-mcp@0.8.27 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.