pincushion-mcp@1.12.1
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 18d ago · by lpm-firewall-aiSource review found no install lifecycle hook or confirmed attack behavior. The flagged credential and agent-configuration paths are connected to requested product operations, and the configuration changes require explicit consent.
Decision evidence
public snapshot- package.json exposes server.js but defines no install lifecycle hook.
- Agent setup writes are gated by explicit consent and target project-level editor locations; existing or managed configurations are checked before changes.
- Deployment credential calls pass data through the configured owner lifecycle and are tied to deployment automation or requested management actions.
- Telemetry hashes the license key before using it as an account identifier; license helpers display only its last four characters.
- mobile-wall.mjs sends the license key to its configured cloud sync service for annotation and screenshot operations.
Source & flagged code
11 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.12.1.
See all versions of pincushion-mcp for other recorded verdicts.
- Review the evidence and your use of pincushion-mcp@1.12.1 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.