@theronap/agnoclast-mcp@0.9.283
Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged credential flow requests access to a confidential brain through the configured Cortex API when that brain is explicitly named in a tool call. Setup and editor configuration changes are command-driven, and the Antigravity adapter does not activate its generated launch agent.
Decision evidence
public snapshot- The manifest describes an MCP integration for the publisher’s Cortex service.
- Configuration setup and cross-editor installation are explicit CLI commands.
- Confidential-session proof is sent with a seat-token request to the configured Cortex API after a tool names a confidential brain.
- The Antigravity adapter writes a launch agent file but does not activate it; it tells the user to load it.
- The status command’s automatic guard repair is described as applying the guard for the next session.
- The package reads Codex and Claude account proof, so credential handling warrants scrutiny; the inspected flow sends proof to the configured Cortex API as part of an explicitly requested confidential-brain action.
- No install lifecycle scripts are declared.
- The persistence hint is bounded: the adapter writes artifacts but does not load the launch agent.
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/agnoclast-mcp@0.9.283.
See all versions of @theronap/agnoclast-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/agnoclast-mcp@0.9.283 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.