Enfusion MCP Server
enfusion-mcp
npm
v0.6.1
Published by articulated7 — 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.
MCP server for Arma Reforger / Enfusion engine modding — create mods from natural language
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 − 11 = 83. 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 |
|---|---|
| −10 | capability blast radius (critical) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 4
high Shell/command execution in server code (dist/tools/mod-build.js)MTC-SRC-002
In the server's implementation (`dist/tools/mod-build.js:4`): 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: rt { spawn } from "node:child_process"; const WORKBENCH_DIAG_EXE = "ArmaReforgerWorkbenchSteamDiag.exe"; const BUILD_TIM
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/mod-build.js
high Shell/command execution in server code (dist/workbench/client.js)MTC-SRC-002
In the server's implementation (`dist/workbench/client.js:15`): 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: , execSync } from "node:child_process"; import { encodeRequest, decodeResponse } from "./protocol.js"; import { logger }
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/workbench/client.js
medium Untrusted input concatenated into a command sink (dist/workbench/client.js)MTC-SRC-009
In the server's implementation (`dist/workbench/client.js:181`): 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: try { execSync(`taskkill /IM ${WORKBENCH_EXE} /F`, { stdio: "ignore" }); logger.info("Kill
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/workbench/client.js
low Unconstrained path parameter "path" on "project_browse"MTC-CAP-008
Tool "project_browse" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool project_browse · inputSchema.properties.path
Tools 44
Each tool and what it can reach — statically extracted from the published source.
project_browseingests untrusted inputreads sensitive datagame_browseingests untrusted inputproject_readingests untrusted inputapi_searchno sensitive capabilityasset_searchno sensitive capabilityconfig_createno sensitive capabilitygame_readno sensitive capabilitylayout_createno sensitive capabilitymod_buildno sensitive capabilitymod_createno sensitive capability
Show 34 more tools ↓
mod_validateno sensitive capabilityprefab_createno sensitive capabilityproject_writeno sensitive capabilityscript_createno sensitive capabilityserver_configno sensitive capabilitywb_cleanupno sensitive capabilitywb_clipboardno sensitive capabilitywb_componentno sensitive capabilitywb_connectno sensitive capabilitywb_entity_createno sensitive capabilitywb_entity_deleteno sensitive capabilitywb_entity_inspectno sensitive capabilitywb_entity_listno sensitive capabilitywb_entity_modifyno sensitive capabilitywb_entity_selectno sensitive capabilitywb_execute_actionno sensitive capabilitywb_launchno sensitive capabilitywb_layersno sensitive capabilitywb_localizationno sensitive capabilitywb_open_resourceno sensitive capabilitywb_playno sensitive capabilitywb_prefabsno sensitive capabilitywb_projectsno sensitive capabilitywb_reloadno sensitive capabilitywb_resourcesno sensitive capabilitywb_saveno sensitive capabilitywb_script_editorno sensitive capabilitywb_stateno sensitive capabilitywb_stopno sensitive capabilitywb_terrainno sensitive capabilitywb_undo_redono sensitive capabilitywb_validateno sensitive capabilitywiki_searchno sensitive capabilityworkshop_infono sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 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.6.1 latest |
B 83/100 | 4 | 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 enfusion-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.