@atlisp/mcp@1.9.5
MCP Server for @lisp on CAD,support AutoCAD/GstarCAD/ZWCAD/BricsCAD or CAD platform compatible with AutoLISP
AI Security Review
scanned 23h ago · by lpm-firewall-aiSource inspection confirms automatic recurring disclosure of host-identifying health data, so this warrants a warning for data exfiltration. The package-aligned endpoint and operational payload do not establish a publish-block attack.
Decision evidence
public snapshot- The package entrypoint starts a health reporter after the server starts.
- The report includes the machine hostname and CAD and runtime status.
- The running process sends the report to a fixed package-service endpoint on a repeating interval.
- Autostart changes are behind explicit CLI flags.
- The reported fields are operational health metrics; the inspected code does not show credentials or user document contents being sent.
- The collector is the package’s own service, and the autostart mutation requires an explicit command-line flag.
Source & flagged code
9 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/atlisp-mcp.jsView on unpkgPackage source references child process execution.
dist/atlisp-mcp.jsView on unpkg · L1132Findings
Affected versions and remediation
This report applies to @atlisp/mcp@1.9.5.
See all versions of @atlisp/mcp for other recorded verdicts.
- Review the evidence and your use of @atlisp/mcp@1.9.5 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.