pincushion-mcp@1.11.12
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 3mo ago · by lpm-firewall-aiSource inspection found no install lifecycle hook, stealth persistence, or remote payload execution. The package nonetheless performs explicit-user-command MCP configuration, so it should be warned rather than blocked.
Decision evidence
public snapshot- Explicit `claim` can register a Pincushion MCP entry in project-local editor configuration.
- The generated MCP entry launches `npx pincushion-mcp --project-dir .`.
- Cloud sync sends its configured license key only to the configured Pincushion sync URL.
- No npm preinstall, install, or postinstall hook is declared.
- Shell execution is limited to the explicit mobile-wall publish deploy-command.
- No remote code download-and-execute chain was found; the scanner's download hint is a displayed installation suggestion.
Source & flagged code
9 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.12.
See all versions of pincushion-mcp for other recorded verdicts.
- Review the evidence and your use of pincushion-mcp@1.11.12 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.