trace-mcp@3.30.1
⚠ Under reviewFramework-aware code intelligence MCP server — 88 framework integrations, 81 languages, 72.7% fewer input tokens to review a pull request, comprehension at parity
AI Security Review
scanned 25d ago · by lpm-firewall-aiInspected install hooks and agent path hints show package-owned launcher, launchd, and publisher-repo app update behavior, not a foreign control-surface hijack or hidden payload. Marking the package clean is blocked because sixteen required citation paths exceed the eight-citation limit, so the review stays unresolved.
Decision evidence
public snapshot- package.json postinstall runs local scripts preflight-native.mjs, postinstall-app.mjs, and postinstall-control-plane.mjs.
- The control-plane hook exits when TRACE_MCP_NO_POSTINSTALL is set or the tree is a dev checkout, then writes this package's ~/.trace launcher and its own LaunchAgent, and skips launchd when daemon.disabled exists.
- Desktop update fetches default to the publisher repo nikolai-vysotskyi/trace-mcp.
- The Claude plugin file only declares an mcpServers command and is not installed into a user agent config by the postinstall hook.
- The hinted dist/proxy.js lines define home-directory path constants for agent project folders.
- A clean verdict cannot be published: sixteen required citation paths exceed the eight-citation cap, and no separate malicious chain was found.
- Postinstall can bootstrap com.trace-mcp.server and, on macOS, download a publisher release to refresh a legacy desktop bundle.
- Agent home paths are referenced in the bundle, which is expected for an MCP code-intelligence server and was not shown to be written from the install hook.
Source & flagged code
26 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 unpkgFindings
Affected versions and remediation
This report applies to trace-mcp@3.30.1.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.30.1 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.