registry / @extenshi/mcp / 0.13.1
@extenshi/mcp@0.13.1
Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found an install-time telemetry hook, but it exits unless the shared configuration records affirmative consent. Runtime tools use the package's fixed service endpoints, and MCP analytics filters tool content; no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package invokes its postinstall script; that script sends an event only when telemetry consent is recorded.
Impact
The inspected behavior is limited to consent-gated adoption telemetry and client-requested MCP operations.
Mechanism
The install event uses an anonymous install identifier and coarse runtime details. Runtime analytics removes tool content before transmission.
AI rationale
Source inspection found an install-time telemetry hook, but it exits unless the shared configuration records affirmative consent. Runtime tools use the package's fixed service endpoints, and MCP analytics filters tool content; no concrete attack behavior was established.
Evidence
package.jsonscripts/postinstall.cjsdist/index.jsdist/telemetry.jsdist/mcp-analytics.jsdist/config.jsdist/development-guide.js
Network endpoints4
eu.i.posthog.combff.extenshi.ioscan.extenshi.iodocs.extenshi.io
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines a postinstall hook that runs the package's telemetry script.
- The install script exits unless the shared config records an affirmative telemetry choice.
- When enabled, the install event contains an anonymous install identifier and coarse package and runtime details.
- The MCP server registers tools for client requests and uses fixed Extenshi service endpoints.
- MCP analytics removes tool arguments, results, intent, and error messages before sending events.
- The development guide describes extension development and reference tools.
Evidence against
- The postinstall hook can send an install event over the network, but the inspected code requires recorded telemetry consent first.
Behavioral surface
CryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
4 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
30import { checkForUpdate } from './update-check.js';
L31: const require = createRequire(import.meta.url);
L32: const pkg = require('../package.json');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/index.jsView on unpkg · L30Findings
2 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/development-guide.js#virtual:normalized:round1
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.13.1.
See all versions of @extenshi/mcp for other recorded verdicts.
- Review the evidence and your use of @extenshi/mcp@0.13.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.