@extenshi/mcp@0.18.1
Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source shows default-on runtime analytics, while the package README does not disclose telemetry or its opt-out. The collected data appears limited and tool content is filtered, so this is suspicious undisclosed telemetry rather than malicious exfiltration.
Decision evidence
public snapshot- The MCP entry point initializes telemetry at startup, and the telemetry module says it is active by default unless opted out.
- Telemetry sends package and runtime details with an anonymous per-install ID; MCP analytics drops tool arguments, results, and error messages.
- The postinstall telemetry ping requires telemetry:true in the existing config, so it does not run without prior recorded consent.
- The runtime telemetry payload is limited to usage, error classification, duration, and coarse runtime details; the MCP analytics instrumentation excludes tool content.
- The publish-access request sends the Extenshi API key to the configured Extenshi BFF as part of the publishing tool’s explicit operation.
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.18.1.
See all versions of @extenshi/mcp for other recorded verdicts.
- Review the evidence and your use of @extenshi/mcp@0.18.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.