# Netrun (npm · netrun-mcp)

Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `api.netrun.io`: 38/100, [markdown](https://verifymcp.io/servers/io-netrun-netrun/v1-mcp.md), [page](https://verifymcp.io/servers/io-netrun-netrun/v1-mcp)
- npm · `netrun-mcp`: 60/100 (this document), [markdown](https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp.md), [page](https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp)

## Channel facts

- Registry: `npm`
- Package: `netrun-mcp`
- Version: `0.4.0`
- 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-06.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 95 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 (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1673 tokens (~185/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Netrun MCP server?

Netrun runs locally as an npm package, launched with npx -y netrun-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 io-netrun-netrun -- npx -y netrun-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-netrun-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-netrun-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-netrun-netrun -- npx -y netrun-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-netrun-netrun --command npx --arg -y --arg netrun-mcp
```

### Hermes

```yaml
mcp_servers:
  io-netrun-netrun:
    command: "npx"
    args: ["-y", "netrun-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-netrun-netrun": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-netrun-netrun -t stdio -c npx -a -y netrun-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-netrun-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-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-10-28 (score 60, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 45)

First indexed and scored.

## MCP tools (9)

### `netrun_whoami` (~29 tokens)

Netrun account

The plan, how many projects are available and how much free running time bots have left.

### `netrun_list_projects` (~20 tokens)

List Netrun projects

All projects of the account with URLs and state.

### `netrun_status` (~58 tokens)

Project status

Is the project running, its URL, what blocks it, which secrets are already set and why the last publish failed. It also lists the names of the secrets already saved; their values are never returned.

Input parameters:

- `project_id` (integer, required)

### `netrun_logs` (~58 tokens)

Project logs

Last lines of the application output — the first place to look when a bot goes silent. Most failures name their cause in the last lines.

Input parameters:

- `lines` (integer): How many trailing lines to return
- `project_id` (integer, required)

### `netrun_publish` (~312 tokens)

Publish to Netrun

Uploads a project folder and puts it online — a new project or a new version of an existing one. Detects the stack (Python, Node, Go, Rust, PHP, static HTML, Docker, docker-compose), asks for missing secrets, waits for the build and returns the URL or the failure reason. A new project takes a name; an existing one is updated by project_id. When the code needs secrets that are not set yet, the result is needs_secrets with their names, and values go in “secrets”. A build takes 1-5 minutes.

Input parameters:

- `comment` (string): Short note for the version history, e.g. "fix /start handler"
- `name` (string): Name for a NEW project (becomes part of the URL). Omit when updating an existing project.
- `path` (string, required): Absolute path to the project folder on this machine
- `project_id` (integer): Existing project to update. Omit to create a new one.
- `secrets` (object): Secrets as {"BOT_TOKEN": "123:abc"}. Stored encrypted; delivered to the app as environment variables via .env.
- `skip_secrets` (boolean): Publish even though the code seems to read env variables that were not provided. Use only after the user confirmed the app does not need them.
- `wait` (boolean): Wait for the build to finish (up to wait_seconds). false = return right after upload.
- `wait_seconds` (integer)

### `netrun_set_secrets` (~126 tokens)

Set project secrets

Saves tokens and API keys as environment variables (stored encrypted) and re-publishes so the app picks them up. Values are write-only and are never returned.

Input parameters:

- `file` (string): Which env file to write to; ".env" unless the project uses another
- `project_id` (integer, required)
- `publish` (boolean): Re-publish right away so the running app receives the new values
- `secrets` (object, required): Secrets as {"BOT_TOKEN": "123:abc"}. Stored encrypted; delivered to the app as environment variables via .env.

### `netrun_domains` (~167 tokens)

Custom domain

Points your own domain at the site and checks whether the registrar settings have taken effect. Until they have, it shows which records to add. The result lists the DNS records to add at the registrar; action "check" verifies them. Records take minutes to hours to spread. Custom domains need a paid plan and a website (bots have no address). Removing a domain is only available in the dashboard.

Input parameters:

- `action` (string): "list" shows the domains and their DNS records, "add" attaches one more, "check" asks DNS whether the records have taken effect.
- `domain` (string): The domain itself, for action "add": "example.com" or "shop.example.com". Without http:// and without a trailing slash.
- `project_id` (integer, required)

### `netrun_link` (~241 tokens)

Public link

Decides whether the project gets a public HTTPS address — for example a webhook bot we took for a background program. Re-publishes the project; the link appears if the app answers requests from the internet. Netrun guesses from the code whether a project needs an address, and a webhook bot or an API can look like a background program. needed=true gives the project a URL, needed=false removes it; the choice survives later code updates. The project is re-published (a short restart). The link appears only if the app listens on 0.0.0.0 on the port from the PORT environment variable; otherwise the project keeps running in the background without a link. The URL is not registered with the bot platform automatically (for Telegram that is setWebhook).

Input parameters:

- `needed` (boolean, required): true — the project needs a public HTTPS address (website, API, webhook bot). false — it runs in the background without one.
- `project_id` (integer, required)
- `wait` (boolean): Wait for the re-publish to finish (up to wait_seconds). false = return right away.
- `wait_seconds` (integer)

### `netrun_control` (~49 tokens)

Start / stop / restart

Start, stop or restart a project. On the Free plan a bot’s free running time is counted only while it runs.

Input parameters:

- `action` (string, required)
- `project_id` (integer, required)

## Diagnostics

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

## Score history

- 2026-11-06: 60
- 2026-11-05: 60
- 2026-11-04: 60
- 2026-11-03: 60
- 2026-11-02: 60
- 2026-11-01: 60
- 2026-10-31: 60
- 2026-10-30: 60
- 2026-10-29: 60
- 2026-10-28: 60
- 2026-10-27: 45

## Common questions

### What is the Netrun MCP server?

Netrun is an MCP server listed in the public MCP registry as io.netrun/netrun. Publish websites and Telegram bots to Netrun, upload a folder from your editor, get a URL. This page covers its npm package (netrun-mcp).

### Is the Netrun MCP server safe to use?

Netrun scores 60 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 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 Netrun MCP server expose?

Netrun exposes 9 tools: netrun_whoami, netrun_list_projects, netrun_status, netrun_logs, netrun_publish, and 4 more. Their descriptions and schemas cost roughly 1,060 tokens of context every time the server is loaded.

### Is the Netrun MCP server still maintained?

Netrun is still listed as active in the MCP registry. We last reached this channel on 6 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 Netrun MCP server under?

Netrun declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Netrun MCP server?

VerifyMCP ran 15 checks on Netrun, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Netrun: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/netrun-mcp
- Socket report: https://socket.dev/npm/package/netrun-mcp
- Repository: https://github.com/netrun-io/netrun-mcp
- Website: https://netrun.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-netrun-netrun/netrun-mcp