WRM PRO is listed as active in the registry but did not answer our last check. Last commit 6 Nov 2026.
Your self-hosted WRM PRO: logs, files, services and commands with approvals and audit.
What the code does
We read the source, 20 h ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
: childProcess.spawn(process.platform === 'darwin' ? 'open' : 'xdg-open', [link], {detached: true, stdio: 'ignore'});
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
" || { rm -rf -- " + shellQuote(dir) + "; exit 1; }; else exit " + strconv.Itoa(mdLockedExit) + "; fi"
runuser, err := exec.LookPath("runuser")
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
mediumInContainer = func() bool { return mediumFileExists("/.dockerenv") || mediumFileExists("/run/.containerenv") }
if op.Delete {
continue
}
f := s.abs(op.Rel)
op.tmp = path.Dir(f) + "/." + path.Base(f) + ".wrm-tmp"
if e := copyIn(filepath.Join(dir, rel), target+"/"+filepath.ToSlash(rel)); e != nil {
vm.runInNewContext(js.slice(start, end).replace('const LANGS', 'var LANGS'), ctx);
const child = spawn(process.execPath, [bridge], {
info.Why = "WRM itself runs in a container. Give it the host's Docker instead: mount /var/run/docker.sock and the docker CLI into WRM's container"
problem = "empty path; leave key out to use the agent or ~/.ssh/config"
self.old_env = dict(os.environ)
for _, n := range []string{"id_rsa", "id_ed25519", "id_ecdsa", "id_dsa"} {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
A tool parameter here reaches a dangerous call
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add wrm-pro --transport http 'https://{wrm_host}/mcp'https://{wrm_host}/mcp[mcp_servers.wrm-pro]
url = "https://{wrm_host}/mcp"{
"mcpServers": {
"wrm-pro": {
"url": "https://{wrm_host}/mcp"
}
}
}{
"servers": {
"wrm-pro": {
"type": "http",
"url": "https://{wrm_host}/mcp"
}
}
}Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://{wrm_host}/mcp | streamable-http | answering | 1 ms | 2 min ago |
Alternatives to WRM PRO
same job, measured the same wayPolicy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.
Human approvals, autonomy limits and a chained audit log for the AI agents of service firms.
Self-hosted IMAP/SMTP email for any MCP client, with per-client permissions and audit log.
Cordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals.
Your agent ships the app. Alerts, logs, project memory and approval-gated deletes come with it.
Reach your own computers from any AI app: files, search, commands, approvals and outage alerts.
Let AI agents use your real Android phones safely, with permissions, approvals and an audit log.
Deploy and manage web apps with Atlas hosting, isolated Postgres, file storage and logs.
WRM PRO — questions
Answers built from our own checks of this server.