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.

Runtime Cloud

NPM · WITHRUNTIME · 2 COMPONENTS · SCANNED SEP 26

Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake.

Available components

remote · api.withruntime.com 39 npm · withruntime 62
62 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 Security63
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 131 tokens (~131/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the Runtime Cloud MCP server?

Runtime Cloud runs locally as an npm package, launched with npx -y withruntime. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · withruntime

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

  • 26 Sept 26 −6
    • Known CVEs: pass → unverified ▼ security
    • Source repository: fail → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 0.6.1 → 0.7.1 functional
    • Package version: 0.6.1 → 0.7.0 functional
  • 25 Sept 26 +18
    • Malware scan: unverified → pass ▲ security
    • License: fail → pass ▲ functional
    • Licence: Apache-2.0 functional
    • Package version: 0.5.1 → 0.6.1 functional
    • Package version: 0.5.1 → 0.6.0 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −14
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.4.0 → 0.5.1 functional
    • Package version: 0.4.0 → 0.5.0 functional
  • 23 Sept 26 64

    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 26 Sept 2026 · Analysed npm/withruntime@0.7.1

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 →

MCP tools · 1 exposed · ~65 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
runtime_connect ~65

Connect Runtime on this machine with a browser approval. The first call returns a link and a code: show them to the person you work for and ask them to approve. Call again after they have; it waits up to 45 seconds for the approval, then Runtime's tools appear.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Runtime Cloud MCP server?

Runtime Cloud is an MCP server listed in the public MCP registry as com.withruntime/runtime. Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake. This page covers its npm package (withruntime).

Is the Runtime Cloud MCP server safe to use?

Runtime Cloud scores 62 out of 100 on VerifyMCP. 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 Runtime Cloud MCP server expose?

Runtime Cloud exposes 1 tool: runtime_connect. Their descriptions and schemas cost roughly 65 tokens of context every time the server is loaded.

Is the Runtime Cloud MCP server still maintained?

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

Runtime Cloud 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.