@kryptosai/mcp-observatory@1.46.0
MCP security scanner and CI gate. Test, secure, and monitor MCP servers with attack simulation, schema drift detection, health scoring, and SARIF before agents depend on them.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package has an explicit CLI capability to alter MCP client configuration, including discovered user-level configs, which warrants a warning under the agent configuration policy. The inspected postinstall helper does not invoke that capability, and its separate CI setup requires opt-in.
Decision evidence
public snapshot- The explicit `protect` command can target a supplied MCP config or discover multiple client configs.
- The protect operation rewrites configured server commands to run through the package wrapper and saves a backup.
- Discovered configuration locations include user-level agent configuration files.
- The wrapper checks for a passing local receipt before starting the configured server.
- The postinstall hook is gated and only continues for an MCP project; its automatic CI setup requires an opt-in.
- The configuration mutation is exposed through an explicit CLI command, with an undo option; the inspected code does not invoke it during installation.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/src/ci-issue.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @kryptosai/mcp-observatory@1.46.0.
See all versions of @kryptosai/mcp-observatory for other recorded verdicts.
- Review the evidence and your use of @kryptosai/mcp-observatory@1.46.0 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.