Viralspin MCP Server
@viralspin/mcp
npm
v0.2.0
Published by @viralspin — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
ViralSpin MCP server — publish local videos and carousels to TikTok, Instagram, and YouTube from Claude Code
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 8 = 86. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 12
high Shell/command execution in server code (dist/tools/assembly-adjust.js)MTC-SRC-002
In the server's implementation (`dist/tools/assembly-adjust.js:7`): 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: ipsTool = void 0; const child_process_1 = require("child_process"); const path_1 = __importDefault(require("path")); //
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/tools/assembly-adjust.js
high Shell/command execution in server code (dist/tools/carousel-video.js)MTC-SRC-002
In the server's implementation (`dist/tools/carousel-video.js:22`): 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: t(require("os")); const child_process_1 = require("child_process"); const client_js_1 = require("../client.js"); const I
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/tools/carousel-video.js
high Shell/command execution in server code (dist/tools/explainer-index.js)MTC-SRC-002
In the server's implementation (`dist/tools/explainer-index.js:284`): 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: > __importStar(require("child_process"))); await new Promise((resolve, reject) => { const ff = spawn
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/tools/explainer-index.js
high Shell/command execution in server code (dist/tools/kinetic-text.js)MTC-SRC-002
In the server's implementation (`dist/tools/kinetic-text.js:7`): 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: extTool = void 0; const child_process_1 = require("child_process"); const path_1 = __importDefault(require("path")); con
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/tools/kinetic-text.js
high Shell/command execution in server code (dist/tools/video-assembly.js)MTC-SRC-002
In the server's implementation (`dist/tools/video-assembly.js:7`): 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: blyTool = void 0; const child_process_1 = require("child_process"); const path_1 = __importDefault(require("path")); con
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/tools/video-assembly.js
high Shell/command execution in server code (engine/assemble.mjs)MTC-SRC-002
In the server's implementation (`engine/assemble.mjs: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: spawnSync } from "node:child_process"; import { fileURLToPath } from "node:url"; import fs from "node:fs"; import path
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 engine/assemble.mjs
high Shell/command execution in server code (engine/kinetic.mjs)MTC-SRC-002
In the server's implementation (`engine/kinetic.mjs:14`): 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: spawnSync } from "node:child_process"; const ENGINE = path.dirname(fileURLToPath(import.meta.url)); const PUBLIC = pat
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 engine/kinetic.mjs
high Shell/command execution in server code (src/tools/assembly-adjust.ts)MTC-SRC-002
In the server's implementation (`src/tools/assembly-adjust.ts: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: import { spawn } from "child_process"; import path from "path"; // Adjustment tools operate on the most recent crea
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 src/tools/assembly-adjust.ts
high Shell/command execution in server code (src/tools/carousel-video.ts)MTC-SRC-002
In the server's implementation (`src/tools/carousel-video.ts:16`): 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: ort { spawnSync } from "child_process"; import { post, uploadFiles, deleteFiles } from "../client.js"; const IMAGE_E
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 src/tools/carousel-video.ts
high Shell/command execution in server code (src/tools/explainer-index.ts)MTC-SRC-002
In the server's implementation (`src/tools/explainer-index.ts:280`): 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: spawn } = await import("child_process"); await new Promise<void>((resolve, reject) => { const ff = spawn("ffm
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 src/tools/explainer-index.ts
medium Untrusted input concatenated into a command sink (engine/assemble.mjs)MTC-SRC-009
In the server's implementation (`engine/assemble.mjs:99`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ts resolve. const r = spawnSync(`npx remotion render "${entry}" Assembly "${out}" "--props=${path.join(PUBLIC, "editDa
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 engine/assemble.mjs
medium Dynamic module load from a non-literal (dist/tools/explainer-index.js)MTC-SRC-005
In the server's implementation (`dist/tools/explainer-index.js:102`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: .then(s => __importStar(require(s))); const form = new FormData(); form.append("index_id", indexId); form.ap
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/tools/explainer-index.js
Tools 1
Each tool and what it can reach — statically extracted from the published source.
getting_startedno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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 |
|---|---|---|---|---|
v0.2.0 latest |
B 86/100 | 12 | 1.13.0 | 2026-09-07 |
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 @viralspin/mcp --onlineMore in Design & Media
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Aleph's official SiliconFlow media-generation MCP server (image / video / TTS)
MCP server for image generation using Google Gemini AI
Ambience AI MCP Server - Generate images, videos, and audio through Model Context Protocol
MCP server exposing every endpoint of the AstroWay Calculation API as tools — natal, synastry, transits, Vedic dashas, Tarot, Numerology, Human Design, AI horoscopes — for Claude Desktop, Cursor and any MCP-compatible AI agent.
Audio-guide and trip-planning tools for 1,100+ cities from Audiala. Free, no API key.