@theronap/cortex-mcp@0.9.150
Renamed to @theronap/agnoclast-mcp — use that. Existing installs switch themselves to the new name on next start.
Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not malicious by the install-hook policy because it has no npm lifecycle trigger and its control-surface changes require explicit CLI setup. Its persistent editor hooks, automatic session capture, and permission changes remain a real first-party agent-extension risk.
Decision evidence
public snapshot- The explicit install command wires detected AI-editor adapters and writes a local capability manifest.
- Claude wiring adds a Stop hook that invokes this package and appends its MCP tool permissions.
- The capture path processes hook input and posts an ingest body to the Agnoclast API.
- The Antigravity adapter writes a launchd watcher artifact that invokes the stable package release.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The configuration changes are reached through explicit CLI subcommands, not package import or registry installation.
- Network traffic is directed to the package-aligned Agnoclast service and uses the configured token.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
lib/capture.mjsView on unpkgPackage source references weak cryptographic algorithms.
lib/capture.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @theronap/cortex-mcp@0.9.150.
See all versions of @theronap/cortex-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/cortex-mcp@0.9.150 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.