The earlier review correctly identified a reachable automatic update path: backend startup checks registry.npmjs.org and may install comfyui-mcp@latest despite the wrapper’s fixed dependency declaration. Under the current rules, an npm self-update with an off-switch is suspicious whether or not it is disclosed, so this behavior warrants a warning rather than a malicious block.
Static reason
No blocking static signals were detected.
Trigger
After a user request reaches the backend through discovery or call_tool, the backend runs the check at server startup; it updates when a newer release is found unless the opt-out is set.
Impact
The dependency version may change from the wrapper’s declared 0.52.206, potentially changing the code used by the plugin. The current rules classify an automatic self-update from npm with an off-switch as suspicious, not a block.
Mechanism
The updater fetches the latest version from registry.npmjs.org and runs npm install for comfyui-mcp@latest.
Evidence
server.mjstool-router.mjs.lpm-dependency-evidence-2bf8eb42-d0e2-4479-87c0-ca46dea09535/1/npm-linux/dist/boot.js.lpm-dependency-evidence-2bf8eb42-d0e2-4479-87c0-ca46dea09535/1/npm-linux/dist/services/self-update.jsnpm-managed comfyui-mcp installation