@remcp/runtime@0.2.184
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe reviewed entry point, telemetry flow and screenshot dependency match the package’s stated purpose as a local MCP device runtime. I found no install hook, undisclosed external endpoint or automatic credential transfer.
Decision evidence
public snapshot- The package describes a local MCP runtime and declares no install lifecycle hook; its scripts start the runtime or run checks and tests.
- The runtime starts an MCP server over stdio, and telemetry is delivered as a notification through that server.
- Telemetry event fields are limited to tool names, timings, outcomes and coarse error classes, and the source says they go through the paired ReMCP agent.
- The D-Bus dependency is loaded for a desktop screenshot request; the returned screenshot URI must use the local file protocol.
- Telemetry is enabled by default, though users can opt out; the reviewed code sends it through the paired agent.
- The runtime exposes powerful local file, process, desktop and browser tools, consistent with its stated purpose.
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 · L249Package ships non-JavaScript build or shell helper files.
src/helpers/wayland_eis_sender.pyView on unpkgFindings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.184.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.184 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.