pincushion-mcp@1.11.19
Visual feedback as agent work packets. Stakeholders drop pins on your live app; your AI coding agent reads each pin (selector, screenshot, DOM, thread, acceptance criteria) via MCP and ships the fix.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install lifecycle or automatic attack chain was found, so the source does not support a malicious verdict. The explicit shell and upload capability remains a real risk if project configuration is untrusted, and incomplete static parse coverage makes a clean verdict unsuitable.
Decision evidence
public snapshot- The mobile-wall publish command passes a deploy command from arguments or project configuration to a shell.
- The publish path reads a selected screenshot and sends it with a license key to the configured cloud endpoint.
- The server entrypoint exposes mobile-wall as a user-invoked CLI subcommand.
- Telemetry is configured to contact PostHog unless an opt-out environment variable is set.
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- The shell execution and screenshot upload are reachable only through the mobile-wall command and its publish flow.
- The reviewed license helper only labels key sources and produces local messages; it does not perform network I/O.
- No source evidence showed automatic credential harvesting, remote payload download, or hidden persistence.
Source & flagged code
10 flaggedA single source file combines environment access, network access, and code or shell execution with blocking evidence.
mobile-wall.mjs#virtual:normalized:round1View on unpkg · L121Findings
Affected versions and remediation
This report applies to pincushion-mcp@1.11.19.
See all versions of pincushion-mcp for other recorded verdicts.
- Review the evidence and your use of pincushion-mcp@1.11.19 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.