trace-mcp@3.37.5
Framework-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 7d ago · by lpm-firewall-aiThe runtime migration can change global Claude instructions without using the separate setup command's consent path. The behavior is package-aligned, but its effect on agent tool choice supports a warning rather than a malicious-package block.
Decision evidence
public snapshot- Starting the server schedules a delayed migration; automatic installation of package updates is enabled unless auto_update is set to false.
- The migration skips first use and same-version starts, but runs after a stored version mismatch and calls the global Claude instruction writer.
- That writer can create or change the user's global Claude instructions and remove sections marked for competing tools.
- The inserted Trace routing block steers agents toward Trace tools and away from standard host file-search tools.
- Other flagged agent locations are user-data path declarations or benchmark reads, not this instruction-writing path.
- The changed instructions are a Trace-owned product-routing block, and the update checker targets this same package.
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.37.5.
See all versions of trace-mcp for other recorded verdicts.
- Review the evidence and your use of trace-mcp@3.37.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.