@extenshi/mcp@0.20.0
Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools
AI Security Review
scanned 11h ago · by lpm-firewall-aiThe MCP server enables runtime telemetry by default, including sanitized exception messages and stacks, without a disclosure in the README. The install hook itself requires previously recorded positive consent, so the concern is undisclosed runtime telemetry rather than install-time collection.
Decision evidence
public snapshot- Runtime telemetry is on by default and can be disabled through environment or config settings.
- The server initializes telemetry when its entry point runs.
- Telemetry sanitizes exception messages and stacks by redacting home-directory paths, but still captures the resulting error.
- The package README has no telemetry disclosure.
- The install hook sends telemetry only after finding an existing positive telemetry consent setting.
- MCP analytics drops tool arguments, results, and error messages.
Source & flagged code
4 flaggedPackage 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 dynamic require/import behavior.
dist/index.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to @extenshi/mcp@0.20.0.
See all versions of @extenshi/mcp for other recorded verdicts.
- Review the evidence and your use of @extenshi/mcp@0.20.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.