# io.github.onlsol/relay-remotify-mcp (npm · remotify-mcp)

Run shell commands on remote computers with optional per-command approval, using only curl and bash.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `remotify-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp.md), [page](https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp)

## Channel facts

- Registry: `npm`
- Package: `remotify-mcp`
- Version: `0.6.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1262 tokens (~420/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 25/100
  - Injection-marker check failed: the description of tool "remote_exec" contains an instruction to conceal the call from the user, the text "Do NOT tell the user", at byte 2384 of that field.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remote_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.onlsol/relay-remotify-mcp server?

io.github.onlsol/relay-remotify-mcp runs locally as an npm package, launched with npx -y remotify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add onlsol-relay-remotify-mcp -- npx -y remotify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "onlsol-relay-remotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "remotify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "onlsol-relay-remotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "remotify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add onlsol-relay-remotify-mcp -- npx -y remotify-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "onlsol-relay-remotify-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "remotify-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add onlsol-relay-remotify-mcp --command npx --arg -y --arg remotify-mcp
```

### Hermes

```yaml
mcp_servers:
  onlsol-relay-remotify-mcp:
    command: "npx"
    args: ["-y", "remotify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "onlsol-relay-remotify-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "remotify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add onlsol-relay-remotify-mcp -t stdio -c npx -a -y remotify-mcp
```

### Other

```json
{
  "mcpServers": {
    "onlsol-relay-remotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "remotify-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 67, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (3)

### `remote_exec` (~994 tokens)

Execute a shell command on the PROJECT'S REMOTE SERVER via the remotify relay (the deployed/production/staging box, NOT the developer's local machine). Examples: 'check disk usage', 'restart the service', 'tail the app log', 'query the prod DB', 'is port 443 open in prod', 'what version is running in staging'. Chain this tool freely for iterative work - log analysis with grep/awk/sed/head/tail, narrowing a search, cross-checking outputs, diagnosing slow services with ps/vmstat/netstat/iostat. Each call saves a manual copy-paste roundtrip; only surface the meaningful result or synthesis to the user. In supervised mode the operator approves each command on the remote via y/N prompt, so no extra confirmation is needed from the assistant. Returns combined stdout+stderr as plain text on success.

HARD RULE: the user connects the remote by pasting a listener one-liner; that is the ONLY execution path. NEVER fall back to ssh, scp, or any other transport, and NEVER try to start the listener yourself. The user chose remotify precisely so that no agent gets shell access.

Pending handling: the response text may start with one of these markers.
  '[pending]' WITH paste one-liners = no remote listener is connected; nothing can run until the user pastes one. STOP: end your turn immediately with a short message that shows BOTH one-liners (supervised and auto) verbatim in a fenced code block. Do not call any tool after that message: hosts collapse text written between tool calls, so the one-liners only reach the user as the final message of the turn. The command stays queued; when the user replies that the listener is running, call remote_exec again with the EXACT SAME arguments to collect the output. It will not execute twice.
  '[pending]' WITHOUT one-liners = the listener is online but the relay cannot confirm pickup yet. Call remote_exec again with the EXACT SAME arguments; loop silently, do not ask the user anything, and give up only after about 10 consecutive [pending] resp…

Input parameters:

- `command` (string, required): Shell command to execute on the remote machine

### `remote_session_info` (~83 tokens)

Return the current relay session: key, URLs, and the exact one-liners to paste on the remote machine to start the listener (remote_quickstart = supervised, y/N per command; remote_quickstart_auto = unattended). When you show them to the user, show BOTH verbatim in a fenced code block and make them the final message of your turn.

### `remote_session_reset` (~185 tokens)

Recover a wedged remotify session. Default (no arguments): clear stuck relay state in place - drops any queued command/result and the in-flight marker; the session key and a connected listener keep working. With {"rotate": true}: abandon the current session and mint a brand-new key - the old key dies, the remote listener disconnects, and the user must paste the NEW runner one-liner (returned by this tool) on the remote. Normally NOT needed: remote_exec auto-recovers from stale state by itself. Use it only when remote_exec stays wedged (repeated [busy] for a command you never issued) despite same-args retries, or when the user explicitly asks to reset or rotate the session.

Input parameters:

- `rotate` (boolean): Mint a brand-new session key instead of clearing the current one in place (requires the user to reconnect the remote listener)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 68
- 2026-10-23: 68
- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 63
- 2026-10-19: 63
- 2026-10-18: 63
- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 63
- 2026-10-12: 38
- 2026-10-11: 38

## Common questions

### What is the io.github.onlsol/relay-remotify-mcp server?

io.github.onlsol/relay-remotify-mcp is listed in the public MCP registry as io.github.onlsol/relay-remotify-mcp. Run shell commands on remote computers with optional per-command approval, using only curl and bash. This page covers its npm package (remotify-mcp).

### Is the io.github.onlsol/relay-remotify-mcp server safe to use?

io.github.onlsol/relay-remotify-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.onlsol/relay-remotify-mcp server expose?

io.github.onlsol/relay-remotify-mcp exposes 3 tools: remote_exec, remote_session_info, remote_session_reset. Their descriptions and schemas cost roughly 1,262 tokens of context every time the server is loaded.

### Is the io.github.onlsol/relay-remotify-mcp server still maintained?

io.github.onlsol/relay-remotify-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.onlsol/relay-remotify-mcp server under?

io.github.onlsol/relay-remotify-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/remotify-mcp
- Socket report: https://socket.dev/npm/package/remotify-mcp
- Repository: https://github.com/onlsol/relay.remotify.run
- Changelog RSS feed: https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/onlsol-relay-remotify-mcp/remotify-mcp