@theronap/cortex-mcp@0.9.234
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 20d ago · by lpm-firewall-aiThe runtime permits a user-configured custom host to receive the service token, which creates a conditional credential exposure risk. The package has no npm install hook, and the flagged agent setup behavior is separately invoked or requires manual activation, so this supports a warning rather than a block.
Static reason
No blocking static signals were detected.
Trigger
The user configures CORTEX_URL to a custom domain and starts the MCP server.
Impact
The selected host can receive the service token. The source shows conditional exposure, not theft or malicious use.
Mechanism
The server uses the configured base URL and places its bearer token in an automatic session ping and other service requests, without restricting custom domains to an approved destination.
AI rationale
The runtime permits a user-configured custom host to receive the service token, which creates a conditional credential exposure risk. The package has no npm install hook, and the flagged agent setup behavior is separately invoked or requires manual activation, so this supports a warning rather than a block.
Evidence
lib/diagnose.mjslib/server.mjs
Network endpoints2
agnoclast.comCORTEX_URL-selected custom domain
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest defines a CLI entrypoint and only release, promote, and rollback scripts; it has no npm install lifecycle hook.
- The token resolver reads the token from the environment. CORTEX_URL defaults to the Agnoclast host, but a custom domain is accepted without an allowlist.
- The MCP server sends its bearer token to BASE in an automatic session ping at startup and every minute; BASE comes from CORTEX_URL.
- The flagged editor and skill code concerns scoped setup or removal behavior. Antigravity writes launcher files, but its source requires a separate manual load command to activate the watcher.
- The package does not silently install these integrations during npm installation; setup, install, and uninstall are separate CLI commands.
Evidence against
- The credential exposure requires configuring CORTEX_URL to a custom domain; the default destination is the package's Agnoclast service. The source does not establish hidden transfer or malicious intent.
Behavioral surface
ChildProcessCryptoEnvironmentVars
Source & flagged code
6 flaggedlib/capture.mjsView file
1import { readFileSync, accessSync, constants, openSync, mkdirSync } from 'fs'
L2: import { spawn, execFileSync } from 'child_process'
L3: import { homedir } from 'os'
...
L21: if (!res.ok) return null
L22: const j = await res.json().catch(() => ({}))
L23: return Array.isArray(j.types) ? j.types : null
...
L35: try {
L36: if (resolve(String(cwd)) === homedir()) return 'general'
L37: } catch { /* unresolvable path — fall through to basename */ }
...
L45: //
L46: // Handles the four remote forms git emits: scp-like ssh (git@github.com:o/n.git), ssh://, https://,
L47: // git://. The HOST CHECK IS LOAD-BEARING, not cosmetic: this string becomes a clearance key, and
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/capture.mjsView on unpkg · L1lib/editors/antigravity.mjsView file
4Trigger-reachable persistence chain: manifest.bin -> bin/cortex-mcp.mjs -> lib/install.mjs -> lib/editors/index.mjs -> lib/editors/antigravity.mjs
L4: // WatchPaths the trajectory store and runs a one-shot sync. wire() generates the two artifacts
L5: // (the sync.sh + the launchd plist) deterministically. It does NOT run `launchctl load` here
L6: // (an unverifiable system mutation) and it flags the PORTABILITY BLOCKER below.
...
L21: /** The launchd plist, home-substituted. Deterministic — golden-testable byte-for-byte. */
L22: export function renderAntigravityPlist({ home = homedir() } = {}) {
L23: const sh = join(home, '.cortex', 'antigravity-sync.sh')
...
L33: <array>
L34: <string>/bin/bash</string>
L35: <string>${sh}</string>
Findings
3 High4 Medium5 Low
HighTrigger Reachable External Ai Agent Control Surface Mutationlib/uninstall.mjs
HighTrigger Reachable Persistencelib/editors/antigravity.mjs
HighSemantic Analysis Limitedbin/cortex-mcp.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencelib/editors/antigravity.mjs
MediumSuspicious Lifecycle Evidencepackage.json
LowScripts Present
LowWeak Cryptolib/capture.mjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @theronap/cortex-mcp@0.9.234.
See all versions of @theronap/cortex-mcp for other recorded verdicts.
- Review the evidence and your use of @theronap/cortex-mcp@0.9.234 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.