Skills/npm/plexo-mcp

plexo-mcp@1.1.1

CAUTION

Publisher claims: "Model Context Protocol (MCP) Server for Plexo - Landing page generation, email templates, publishing, and analytics." Observed in sandbox: static analysis only — behavior not yet observed.

Registry npm (MCP server)Publisher charisol · joined 0 days agoInstalls 1,518Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-27 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
File type combined with upload actiondist/appToolDefs.js:92 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File type combined with upload actionsrc/appToolDefs.ts:89 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
LOW
Unpinned dependency.github/workflows/publish-npm.yml:29 · Unpinned dependencyFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

What would make this Verified

14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim charisol: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
  3. Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
  4. Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim charisol