@remcp/runtime@0.2.164
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged screenshot and network features serve local runtime capabilities, while telemetry is bounded and routed through the paired agent.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its scripts are start, check, and test.
- The screenshot portal requests a screenshot through the local desktop portal and accepts only a local file URI.
- The screenshot tool runs on request and returns the captured image through the runtime tool response.
- The entrypoint starts the MCP server when the runtime process is invoked.
- Telemetry whitelists tool metadata and sends it through the paired ReMCP agent; the user can disable it.
- The browser CDP default endpoint is loopback.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249The screenshot portal requests a screenshot through the local desktop portal and accepts only a local file URI.
src/screenshot-portal.mjsView on unpkg · L281Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.164.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.164 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.