Comfyui (artokun) MCP Server

comfyui-mcp npm v0.52.199 Source verified

Published by artokun — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Local-first, agent-native control plane for ComfyUI — MCP server + autonomous sidebar agent that drives your live graph in natural language on ANY LLM: Claude/ChatGPT/Gemini on your subscription (no API key), free local models via Ollama (fully offline),

Trust grade
C
78/100
Last scanned get badge →
Trust
C · 78/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
C Why this grade threat 88 − adoption risk = 78/100

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 − 11.7 = 88. What the published surface and source actually contain:

PointsWhat was foundCategory
−11.7 Untrusted input concatenated into a command sink ×4 MTC-SRC-009 injection

2. Client adoption risk — 88 − 10 = 78. 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:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated

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 18

high Shell/command execution in server code (dist/orchestrator/antigravity-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/antigravity-backend.js:52`): 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"; // SECURITY: agy is Google's LLM-vendor CLI — its subprocess must NOT inherit th

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/orchestrator/antigravity-backend.js

high Shell/command execution in server code (dist/orchestrator/codex-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/codex-backend.js:39`): 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 { createRequire } from "node:module"; import { copyFileSync, existsSync,

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/orchestrator/codex-backend.js

high Shell/command execution in server code (dist/orchestrator/gemini-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/gemini-backend.js:63`): 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 { createRequire } from "node:module"; import readline from "node:readline

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/orchestrator/gemini-backend.js

high Shell/command execution in server code (dist/orchestrator/grok-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/grok-backend.js:60`): 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 readline from "node:readline"; import { randomUUID } from "node:crypto";

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/orchestrator/grok-backend.js

high Shell/command execution in server code (dist/orchestrator/index.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/index.js:13`): 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: ecFileSync } from "node:child_process"; import { tmpdir, homedir, networkInterfaces } from "node:os"; import { dirname,

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/orchestrator/index.js

high Shell/command execution in server code (dist/orchestrator/panel-agent.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/panel-agent.js:2935`): 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: return true; } spawn(tabId, resume, spawnOpts) { const agent = this.makeAgent(tabId); if (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/orchestrator/panel-agent.js

high Shell/command execution in server code (dist/orchestrator/pi-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/pi-backend.js:56`): 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 { existsSync } from "node:fs"; import { homedir } from "node:os"; import

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/orchestrator/pi-backend.js

high Shell/command execution in server code (dist/orchestrator/qwen-backend.js)MTC-SRC-002

In the server's implementation (`dist/orchestrator/qwen-backend.js:57`): 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 readline from "node:readline"; import { logger } from "../utils/logger.js

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/orchestrator/qwen-backend.js

high Shell/command execution in server code (dist/services/ai-toolkit.js)MTC-SRC-002

In the server's implementation (`dist/services/ai-toolkit.js:9`): 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: childProcess from "node:child_process"; import { existsSync, readFileSync } from "node:fs"; import { homedir } from "nod

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/services/ai-toolkit.js

high Shell/command execution in server code (dist/services/bridge-port-reclaim.js)MTC-SRC-002

In the server's implementation (`dist/services/bridge-port-reclaim.js:12`): 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: ecFileSync } from "node:child_process"; import { readFileSync } from "node:fs"; import { tmpdir } from "node:os"; import

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/services/bridge-port-reclaim.js

medium Hardcoded egress to an external endpoint (dist/tools/missing-models.js)MTC-SRC-003

In the server's implementation (`dist/tools/missing-models.js:46`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ; const res = await fetch(`https://huggingface.co/api/models/${path}/tree/main`, { // config.huggingfaceToke

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/missing-models.js

medium Hardcoded egress to an external endpoint (dist/tools/model-explorer.js)MTC-SRC-003

In the server's implementation (`dist/tools/model-explorer.js:56`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const res = await fetch(`https://civitai.com/api/v1/model-versions/${versionId}`, { // CivitAI is a th

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/model-explorer.js

medium Untrusted input concatenated into a command sink (dist/services/ai-toolkit.js)MTC-SRC-009

In the server's implementation (`dist/services/ai-toolkit.js:286`): 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: childProcess.execSync(`taskkill /PID ${child.pid} /T /F`, { timeout: 10_000, windowsHide: true }); }

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/services/ai-toolkit.js

medium Untrusted input concatenated into a command sink (dist/services/port-owner.js)MTC-SRC-009

In the server's implementation (`dist/services/port-owner.js:196`): 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: uery(port) { return execSync(`lsof -V -nP -iTCP:${port} -sTCP:LISTEN -Fpn 2>&1`, { encoding: "utf-8",

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/services/port-owner.js

medium Untrusted input concatenated into a command sink (dist/services/process-control.js)MTC-SRC-009

In the server's implementation (`dist/services/process-control.js:77`): 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: const out = execSync(`tasklist /FI "IMAGENAME eq ${exe}" /FO CSV /NH`, { encoding: "utf-8", timeout: 5000 })

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/services/process-control.js

medium Untrusted input concatenated into a command sink (plugin/hooks/open-latest-image.mjs)MTC-SRC-009

In the server's implementation (`plugin/hooks/open-latest-image.mjs:71`): 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: os === "win32") { execSync(`start "" "${newest.path}"`, { shell: true, stdio: "ignore" }); } else if (os === "

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 plugin/hooks/open-latest-image.mjs

medium Dynamic module load from a non-literal (dist/utils/optional-dep.js)MTC-SRC-005

In the server's implementation (`dist/utils/optional-dep.js:36`): 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: const mod = (await import(spec)); cache.set(spec, mod); return mod; } catch (err) {

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/utils/optional-dep.js

low Hardcoded egress to an external endpoint in packaging/dev tooling (scripts/gen-manager-name-collisions.mjs)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/gen-manager-name-collisions.mjs:155`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { const res = await fetch(`https://api.comfy.org/nodes?page=${page}&limit=100`); if (!res.ok) throw new Error(`r

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 scripts/gen-manager-name-collisions.mjs

Tools 38

Each tool and what it can reach — statically extracted from the published source.

  • download_modelingests untrusted input
  • apply_manifestno sensitive capability
  • appsno sensitive capability
  • batchno sensitive capability
  • bisectno sensitive capability
  • calculateno sensitive capability
  • clear_vramno sensitive capability
  • comfy_clino sensitive capability
  • create_workflowno sensitive capability
  • enqueue_workflowno sensitive capability
Show 28 more tools ↓
  • generate_imageno sensitive capability
  • get_defaultsno sensitive capability
  • get_historyno sensitive capability
  • get_imageno sensitive capability
  • get_system_statsno sensitive capability
  • get_workflowno sensitive capability
  • install_comfyuino sensitive capability
  • install_custom_nodeno sensitive capability
  • kitchenno sensitive capability
  • list_api_nodesno sensitive capability
  • list_local_modelsno sensitive capability
  • list_packsno sensitive capability
  • model_metadatano sensitive capability
  • node_packno sensitive capability
  • node_snapshotno sensitive capability
  • queueno sensitive capability
  • report_issueno sensitive capability
  • restart_comfyuino sensitive capability
  • runpodno sensitive capability
  • runpod_watchno sensitive capability
  • save_workflowno sensitive capability
  • search_custom_nodesno sensitive capability
  • train_doctorno sensitive capability
  • train_prepare_datasetno sensitive capability
  • train_startno sensitive capability
  • upload_imageno sensitive capability
  • visualize_workflowno sensitive capability
  • workspaceno sensitive capability

What this scan could not see

Versions 10

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.

VersionScoreFindingsEngineScanned
v0.52.199 latest C 78/100 18 1.13.0 2026-09-06
v0.52.197 C 78/100 18 1.13.0 2026-09-05
v0.52.186 C 78/100 18 1.13.0 2026-09-04
v0.52.165 C 78/100 19 1.13.0 2026-08-31
v0.52.146 C 78/100 19 1.13.0 2026-08-30
Show 5 more versions ↓
v0.52.145 C 78/100 19 1.13.0 2026-08-28
v0.52.137 C 78/100 19 1.13.0 2026-08-27
v0.52.100 C 78/100 19 1.13.0 2026-08-25
v0.52.86 C 78/100 19 1.12.1 2026-08-24
v0.52.65 C 78/100 19 1.12.1 2026-08-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.

MCP Trust Score: C · 78/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/comfyui-mcp/badge.svg)](https://mcptrustchecker.com/registry/comfyui-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/comfyui-mcp"><img src="https://mcptrustchecker.com/registry/comfyui-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/comfyui-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 comfyui-mcp --online

Use the free API → How scoring works

Other implementations of Comfyui 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Communication & Collaboration