screenpipe-mcp@0.20.0
MCP server for screenpipe - search your screen recordings and audio transcriptions
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe unrestricted destination combined with automatic credential forwarding meets the conditional credential-exposure warning boundary. There is no install-time hook or fixed covert recipient, so blocking as malware is not supported.
Decision evidence
public snapshot- The package has no npm install hook; its only lifecycle-like script is prepublishOnly.
- The active stdio entry accepts SCREENPIPE_API_URL or SCREENPIPE_LOCAL_API_URL without an endpoint allowlist.
- It obtains an existing Screenpipe API key from environment variables and sends it as a Bearer token to the selected API base.
- When no key is present, it can execute an unpinned screenpipe@latest command through npx to obtain one.
- A test-file header directly instructs AI agents to make changes outside the repository.
- The default API base is localhost and the package metadata contains no dependencies or install-time script.
- The credential forwarding requires a runtime API request and an operator-supplied endpoint override; no hidden fixed recipient was identified.
Source & flagged code
15 flagged · loading sourcePackage source references child process execution.
dist/http-server.jsView on unpkg · L35293Findings
Affected versions and remediation
This report applies to screenpipe-mcp@0.20.0.
See all versions of screenpipe-mcp for other recorded verdicts.
- Review the evidence and your use of screenpipe-mcp@0.20.0 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.