pincushion-mcp@1.11.11
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-aiThe scanner's credential/network and shell findings map to documented Pincushion synchronization, opted-out telemetry, and an explicit user-supplied deployment command. Direct inspection found no lifecycle hook or concrete stealthy/exfiltration chain.
Decision evidence
public snapshot- Runtime cloud sync sends the configured license key to Pincushion's Supabase endpoint.
- The explicit mobile-wall publish command can run a user-supplied deploy command through a shell.
- Optional telemetry uses a stable hash derived from the license key.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The entrypoint enables cloud sync only when a key, flag, or configured key file is present.
- Telemetry documents opt-out controls and hashes rather than sends the raw license key.
- Editor MCP configuration writes occur only through explicit setup/claim workflows and are project-gated.
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.11.
See all versions of pincushion-mcp for other recorded verdicts.
- Review the evidence and your use of pincushion-mcp@1.11.11 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.