@extenshi/mcp@0.21.0
Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe source enables runtime telemetry by default, while the package README does not disclose it. The inspected telemetry is limited and has opt-outs, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the MCP server and generating telemetry events; users can opt out through supported settings.
Impact
Usage and server-start events are reported to analytics without clear user-facing disclosure in the README.
Mechanism
Telemetry sends an anonymous install ID and limited event properties to the PostHog endpoint. The install-time ping has a separate positive-consent gate.
AI rationale
The source enables runtime telemetry by default, while the package README does not disclose it. The inspected telemetry is limited and has opt-outs, so this warrants a warning rather than a block.
Evidence
dist/index.jsdist/telemetry.jsdist/mcp-analytics.jsscripts/postinstall.cjs~/.extenshi/config.json
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runtime telemetry is enabled by default and relies on users to opt out.
- The MCP entry point initializes telemetry and reports when the server starts.
- Telemetry uses an anonymous install ID and sends event properties to PostHog.
- The README does not disclose runtime telemetry.
Evidence against
- The telemetry fields shown are limited to package and runtime details, platform, architecture, and a CI flag.
- MCP analytics drops tool arguments, results, intent, and error messages.
- The postinstall ping requires telemetry consent already recorded in the shared config.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
5 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
32import { checkForUpdate } from './update-check.js';
L33: const require = createRequire(import.meta.url);
L34: const pkg = require('../package.json');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/index.jsView on unpkg · L32Findings
3 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/development-guide.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/build-map-store.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @extenshi/mcp@0.21.0.
See all versions of @extenshi/mcp for other recorded verdicts.
- Review the evidence and your use of @extenshi/mcp@0.21.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.