@theronap/cortex-mcp@0.9.117
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-aiThis is not malicious by the stated boundary because the control-surface writes require explicit user commands and no npm lifecycle hook performs them. It warrants a warning because it persists hooks and permissions in multiple AI-editor control surfaces and transmits session-derived data.
Decision evidence
public snapshot- The explicit install command wires detected AI editors and records a local capability manifest.
- Claude setup adds a prompt-time hook and pre-authorizes the package's MCP tools.
- Codex setup writes an MCP server entry and a Stop hook.
- The capture hook posts session-derived data to the Cortex API.
- The Antigravity option writes a launchd plist and executable wrapper.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Configuration changes require an explicit setup, install, repair, or login command.
- The capture path redacts credential-shaped transcript content before upload.
- No source evidence shows credential theft, destructive behavior, hidden remote code loading, or an unconsented install-time mutation.
Source & flagged code
6 flaggedPackage source references weak cryptographic algorithms.
lib/capture.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @theronap/cortex-mcp@0.9.117.
See all versions of @theronap/cortex-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/cortex-mcp@0.9.117 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.