The wrapper’s startup and process controls are documented, and local ComfyUI startup requires an explicit tool request plus opt-in configuration. The credential and download hints point into the separately pinned upstream dependency; the inspected wrapper does not run those paths automatically on installation or import.
Static reason
No blocking static signals were detected.
Trigger
Plugin activation starts the MCP bridge; ComfyUI startup and upstream tool actions require tool requests, and local auto-start is disabled by default.
Impact
Normal ComfyUI operations may access the configured ComfyUI service and manage its own process when requested; no automatic collection or unrelated network destination was identified.
Mechanism
The bridge communicates with a local control server and the pinned comfyui-mcp dependency. Optional local startup is restricted to loopback and user-configured executable and directory paths.
Evidence
User-configured ComfyUI installation directory (process working directory); no package-owned files identified as modified.
Network endpoints1
127.0.0.1 (default ComfyUI endpoint)