Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Netrun

NPM · NETRUN-MCP · SCANNED SEP 25

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

Available components

68 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1000 tokens (~142/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

npm · netrun-mcp

# add to Claude Code
claude mcp add fadeynotchenko-netrun -- npx -y netrun-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "fadeynotchenko-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fadeynotchenko-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add fadeynotchenko-netrun -- npx -y netrun-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fadeynotchenko-netrun": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "netrun-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fadeynotchenko-netrun --command npx --arg -y --arg netrun-mcp
# ~/.hermes/config.yaml
mcp_servers:
  fadeynotchenko-netrun:
    command: "npx"
    args: ["-y", "netrun-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fadeynotchenko-netrun": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add fadeynotchenko-netrun -t stdio -c npx -a -y netrun-mcp
// mcp.json
{
  "mcpServers": {
    "fadeynotchenko-netrun": {
      "command": "npx",
      "args": [
        "-y",
        "netrun-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/netrun-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 98 packages
Packages resolved 98
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~695 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
netrun_control ~46

Start, stop or restart a project. Stopping a Free-plan bot does not pause its free running time.

NameTypeReqDescription
actionstringyes–
project_idintegeryes–

No output schema declared.

No examples provided.

netrun_list_projects ~35

All projects of the account with id, kind, status and public URL. Use it to find project_id for other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

netrun_logs ~57

Last lines of the application output (stdout/stderr) — the first place to look when a bot is silent or a site errors.

NameTypeReqDescription
linesinteger–How many trailing lines to return
project_idintegeryes–

No output schema declared.

No examples provided.

netrun_publish ~296

Upload a project folder and put it online: creates a new project (pass name) or ships a new version of an existing one (pass project_id). Detects the language automatically (Python, Node, Go, Rust, PHP, static HTML, Docker, docker-compose…). Waits for the build and returns the public URL or the failure reason. If it returns needs_secrets, ask the user for the values and call again with "secrets".

NameTypeReqDescription
commentstring–Short note for the version history, e.g. "fix /start handler"
namestring–Name for a NEW project (becomes part of the URL). Omit when updating an existing project.
pathstringyesAbsolute path to the project folder on this machine
project_idinteger–Existing project to update. Omit to create a new one.
secretsobject–Secrets as {"BOT_TOKEN": "123:abc"}. Stored encrypted; delivered to the app as environment variables via .env. Ask the user for values — never invent them.
skip_secretsboolean–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.
waitboolean–Wait for the build to finish (up to wait_seconds). false = return right after upload.
wait_secondsinteger––

No output schema declared.

No examples provided.

netrun_set_secrets ~153

Save environment variables (tokens, API keys, passwords) for a project. Values are stored encrypted and never returned. By default the project is re-published so the app picks them up. Ask the user for the values — do not invent them.

NameTypeReqDescription
filestring–Which env file to write to; ".env" unless the project uses another
project_idintegeryes–
publishboolean–Re-publish right away so the running app receives the new values
secretsobjectyesSecrets as {"BOT_TOKEN": "123:abc"}. Stored encrypted; delivered to the app as environment variables via .env. Ask the user for values — never invent them.

No output schema declared.

No examples provided.

netrun_status ~51

Current state of one project: is it running, its URL, what blocks it, and — if the last publish failed — why (stage, reason, stderr tail).

NameTypeReqDescription
project_idintegeryes–

No output schema declared.

No examples provided.

netrun_whoami ~57

Who the configured key belongs to, the current plan, project limit and — on the Free plan — how much free running time bots have left. Call it first when the user asks anything about their Netrun account or limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Netrun MCP server?

Netrun is an MCP server listed in the public MCP registry as io.github.fadeynotchenko/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 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 7 tools: netrun_whoami, netrun_list_projects, netrun_status, netrun_logs, netrun_publish, and 2 more. Their descriptions and schemas cost roughly 695 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 25 September 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.