The automatic update path can overwrite host MCP settings and change the agent’s server registrations, so this is a configuration integrity risk. The source indicates the registrations are intended for Devboard’s harness, and does not show an unrelated payload or credential theft; classify as suspicious rather than malicious.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The dashboard starts an update check immediately and repeats it at the default 60-second interval; the write occurs when a newer release is installed.
Impact
This can remove host-specific MCP registrations and change which servers the agent starts. The included entries appear related to Devboard’s intended harness integration.
Mechanism
The updater syncs package files into the host, including copying the package’s MCP manifest to `.omp/mcp.json` without preserving the prior file’s contents.
Evidence
server/index.tsserver/updates.tslib/host-sync.mjsomp/mcp.json.omp/mcp.json.omp/commands/.omp/extensions/