@compr/opscontext-mcp@2.2.0
OpsContext for AI Agents — read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident audit log + policy-as-code hooks. The ops + compliance layer Claude Code can't grow natively.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real agent-control and persistence capability, but it is explicitly user-invoked and not lifecycle-reachable at installation. Per policy it warrants a warning rather than a publication block.
Decision evidence
public snapshot- Explicit CLI command installs Claude Code hook entries.
- Installed hook captures prompts and tool-call previews.
- Explicit autostart command creates a per-user LaunchAgent.
- No preinstall, install, or postinstall lifecycle hook.
- Hook traffic targets authenticated localhost only.
- Agent configuration mutation is command-gated, not automatic.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/adapters.jsView on unpkg · L46A manifest entrypoint or package-local install chain reaches persistence behavior.
dist/install-autostart.jsView on unpkg · L13Findings
Affected versions and remediation
This report applies to @compr/opscontext-mcp@2.2.0.
See all versions of @compr/opscontext-mcp for other recorded verdicts.
- Review the evidence and your use of @compr/opscontext-mcp@2.2.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.