Netrun
NPM · NETRUN-MCP · 2 COMPONENTS
Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL
Available components
Last scanned (7 hours ago)
Scores higher than 31% of npm servers
Category CI/CD and DevOps
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- 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. 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
- 63% 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 10 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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 45
First indexed and scored.
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 5 Nov 2026 · Analysed npm/netrun-mcp@0.4.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
netrun_control Start / stop / restart ~49
Start, stop or restart a project. On the Free plan a bot’s free running time is counted only while it runs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| project_id | integer | yes | – |
No output schema declared.
No examples provided.
netrun_domains Custom domain ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
netrun_link Public link ~241
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).
| Name | Type | Req | Description |
|---|---|---|---|
| needed | boolean | yes | true — the project needs a public HTTPS address (website, API, webhook bot). false — it runs in the background without one. |
| project_id | integer | yes | – |
| wait | boolean | – | Wait for the re-publish to finish (up to wait_seconds). false = return right away. |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
netrun_list_projects List Netrun projects ~20
All projects of the account with URLs and state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netrun_logs Project logs ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | integer | – | How many trailing lines to return |
| project_id | integer | yes | – |
No output schema declared.
No examples provided.
netrun_publish Publish to Netrun ~312
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No output schema declared.
No examples provided.
netrun_set_secrets Set project secrets ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Which env file to write to; ".env" unless the project uses another |
| project_id | integer | yes | – |
| publish | boolean | – | Re-publish right away so the running app receives the new values |
| secrets | object | yes | Secrets as {"BOT_TOKEN": "123:abc"}. Stored encrypted; delivered to the app as environment variables via .env. |
No output schema declared.
No examples provided.
netrun_status Project status ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | – |
No output schema declared.
No examples provided.
netrun_whoami Netrun account ~29
The plan, how many projects are available and how much free running time bots have left.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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
claude mcp add io-netrun-netrun -- npx -y netrun-mcp
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 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 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 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 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.