Security review

Is @pidanmoe/e-commerce-master MCP safe to give an agent?

read onlyunknownunknownhealthy

A factual risk summary built from @pidanmoe/e-commerce-master’s real tool surface, execution model, and verification history — not a vibe. Trust score 52/100.

01What it can do

Only read-style tools observed — no write/destructive tools.

11 tools observed

02Execution model

Transport not yet confirmed, so the execution model is unknown. Treat as untrusted until verified.

Installs via npx (`npx -y @pidanmoe/e-commerce-master`) — it pulls and executes third-party code; pin versions and review the source.

03Permissions & auth

No auth scopes captured yet (scope extraction runs during the sandboxed handshake, gated until configured). Treat unconfirmed scopes as unknown, not as “none.”

04Verification

handshakepassed — tool surface is real

runstools_list:passed · handshake:passed · metadata:passed

last_checked2026-06-30 22:15Z

sourcesnpm registry [p4]

Reduce the risk

Wrap @pidanmoe/e-commerce-master in a governed Loadout — scoped permissions, approval rules on write/destructive tools, and audit logging — instead of handing your agent raw access.

Build a governed Loadout

See also: full server page · setup · alternatives