@theronap/agnoclast-mcp@0.9.286
Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected credential flow sends account proof to the configured Agnoclast API for a requested confidential-brain session. Configuration migration is scoped to an existing package entry, and the persistence hint requires explicit wiring and activation; the source does not show an attack.
Decision evidence
public snapshot- The package declares no install, preinstall, or postinstall lifecycle scripts; its executable is bin/cortex-mcp.mjs.
- The confidential-session code sends account proof to the configured Agnoclast API endpoint as part of a request to open a named confidential brain.
- The automatic key migration is limited to configurations that still have the package’s old `cortex` entry and migrates it to `agnoclast`.
- The Antigravity adapter writes its sync script and launchd plist only when its `wire()` function runs, and says it does not load the agent automatically.
- Starting the MCP server can run a migration that updates Claude configuration and adds allow rules for the renamed tool namespace.
- Antigravity’s generated watcher can run a sync script after a user activates its launchd agent.
Source & flagged code
16 flaggedSource file is highly similar to a previously finalized malicious package; 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/agnoclast-mcp@0.9.286.
See all versions of @theronap/agnoclast-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/agnoclast-mcp@0.9.286 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.