Vibemaster MCP Server
vibemaster-mcp
npm
v8.0.2
Published by snaiilydevelopment — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 28.3 = 72. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −22 | Hardcoded GitHub token in server code MTC-SRC-008 | exfiltration |
| −6.3 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 72 − 7 = 65. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
| ✓ | inspection depth (source) — how much of the target the scan could see |
Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 22
high Hardcoded GitHub token in server code (dist/tests/secret-guard.test.js)MTC-SRC-008
A live-looking GitHub token is hardcoded in `dist/tests/secret-guard.test.js:11`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: GitHub token: ghp_…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server dist/tests/secret-guard.test.js
high Dynamic code execution in server code (dist/__tests__/bug-detector-fixes.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/bug-detector-fixes.test.js:52`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/bug-detector-fixes.test.js
high Dynamic code execution in server code (dist/__tests__/debug-handlers.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/debug-handlers.test.js:27`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/debug-handlers.test.js
high Dynamic code execution in server code (dist/__tests__/debug-session-step-order.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/debug-session-step-order.test.js:91`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/debug-session-step-order.test.js
high Dynamic code execution in server code (dist/__tests__/diff-agentic-handlers.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/diff-agentic-handlers.test.js:22`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/diff-agentic-handlers.test.js
high Dynamic code execution in server code (dist/__tests__/orchestration-handlers.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/orchestration-handlers.test.js:36`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/orchestration-handlers.test.js
high Dynamic code execution in server code (dist/__tests__/pipeline-mode-gating.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/pipeline-mode-gating.test.js:27`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/pipeline-mode-gating.test.js
high Dynamic code execution in server code (dist/__tests__/runtime-events.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/runtime-events.test.js:170`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/runtime-events.test.js
high Dynamic code execution in server code (dist/__tests__/session-reporter.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/session-reporter.test.js:14`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/session-reporter.test.js
high Dynamic code execution in server code (dist/__tests__/timeout-json-format.test.js)MTC-SRC-001
In the server's implementation (`dist/__tests__/timeout-json-format.test.js:25`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/__tests__/timeout-json-format.test.js
high Dynamic code execution in server code (dist/analysis/session-pattern-tracker.js)MTC-SRC-001
In the server's implementation (`dist/analysis/session-pattern-tracker.js:284`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/analysis/session-pattern-tracker.js
high Shell/command execution in server code (dist/detectors/bug-detector.js)MTC-SRC-002
In the server's implementation (`dist/detectors/bug-detector.js:618`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: exec(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/detectors/bug-detector.js
high Shell/command execution in server code (dist/detectors/dataflow-analyzer.js)MTC-SRC-002
In the server's implementation (`dist/detectors/dataflow-analyzer.js:259`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: exec(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/detectors/dataflow-analyzer.js
high Shell/command execution in server code (dist/detectors/stack-detector.js)MTC-SRC-002
In the server's implementation (`dist/detectors/stack-detector.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/detectors/stack-detector.js
high Shell/command execution in server code (dist/diff/diff-detector.js)MTC-SRC-002
In the server's implementation (`dist/diff/diff-detector.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/diff/diff-detector.js
high Shell/command execution in server code (dist/gsd/uat.js)MTC-SRC-002
In the server's implementation (`dist/gsd/uat.js:11`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/gsd/uat.js
high Shell/command execution in server code (dist/handlers/sync-handlers.js)MTC-SRC-002
In the server's implementation (`dist/handlers/sync-handlers.js:159`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/handlers/sync-handlers.js
high Shell/command execution in server code (dist/installer/mcp-installer.js)MTC-SRC-002
In the server's implementation (`dist/installer/mcp-installer.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/installer/mcp-installer.js
high Shell/command execution in server code (dist/observability/mcp-health.js)MTC-SRC-002
In the server's implementation (`dist/observability/mcp-health.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/observability/mcp-health.js
high Shell/command execution in server code (dist/quality/context-builder.js)MTC-SRC-002
In the server's implementation (`dist/quality/context-builder.js:62`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/quality/context-builder.js
high Shell/command execution in server code (dist/setup-wizard.js)MTC-SRC-002
In the server's implementation (`dist/setup-wizard.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/setup-wizard.js
medium Package runs install-time scripts (postinstall)MTC-SUP-010
"vibemaster-mcp" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package vibemaster-mcp
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v8.0.2 latest |
C 72/100 | 22 | 1.5.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan vibemaster-mcp --onlineMore in Developer Tools
Security scan results for the 1c Odata MCP server.
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.