Security

A narrow relay between the model and your machine.

ReMCP treats remote computer control as privileged access. Authentication, device isolation and explicit tool behavior are part of the core design.

Identity and tenancy

User authentication is handled with Firebase Authentication. MCP sessions and paired device records are scoped to the same authenticated user identity.

Device credentials

Pairing codes are short-lived and one-time. Each paired computer receives an independent random credential. Server storage keeps a one-way hash of that credential.

Network model

The local agent opens an outbound secure WebSocket connection to the relay. No inbound port needs to be opened on the laptop or workstation.

Tool risk

Tool descriptors explicitly declare read-only, destructive and open-world hints. Terminal execution can change local or external state depending on the command supplied.

Revocation

Revoke a device from the signed-in workspace if a computer is lost, retired, or no longer trusted. Revoked credentials cannot reconnect.

Transport

Production traffic uses HTTPS/WSS. OAuth uses PKCE S256. Tokens and device credentials are not placed in public source or page markup.