Prized Sandboxes
NPM · @PRIZED/SANDBOX-MCP
Linux microVM sandboxes for agents: run code, fork, pause and resume. Your agent can sign you up.
Available components
Last scanned (18 hours ago)
Scores higher than 40% of npm servers
Category Cloud Infrastructure
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 Security99
- 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
- 1 of 4 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency39
- 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 (Apache-2.0).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3157 tokens (~242/item across 13 items; 13 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 Management17
- Stability observed for 5 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
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (77% of tools); any adoption earns full credit.Pass
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 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −1
- Maintenance: pass → fail ▼ functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 68
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 21 Nov 2026 · Analysed npm/@prized/sandbox-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 4 packages
| Packages resolved | 4 |
|---|---|
| No linked repository | 1 |
| 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 →
create_sandbox Create a sandbox ~535
Create a Prized sandbox: an isolated Linux microVM (Ubuntu 24.04) to run code in, away from this machine. Returns once it is running, usually within seconds, with the id the other tools take. Templates: prized-base-v1 (default; Python 3, Node.js 22, git, build tools) or prized-agent-v1 (adds Claude Code and Codex). Commands run as the user prized in /home/prized/work, with outbound internet; no sudo or apt, and Python packages go in a venv (python3 -m venv ~/.venv). It bills per second while running. By default it pauses after 15 idle minutes (memory and processes kept; the next call resumes it) and is deleted 7 days after it pauses or when its run time ends; delete it with delete_sandbox when done.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_delete_minutes | integer | – | Delete it this many minutes after it pauses, up to 40,320 (28 days). Default 10,080 (7 days); 0 keeps a paused sandbox until you delete it. |
| auto_pause_minutes | integer | – | Pause after this many minutes without a command or file call. Default 15; 0 never. A background job pauses with it, so use 0 for one that must run unattended. |
| disk_gb | integer | – | Disk in GB, 10 to 128. Default 10. |
| env_vars | object | – | Environment variables for every command in the sandbox, such as a key the code inside needs. Prized stores them encrypted and its API never returns them; anything running in the sandbox can read them. |
| labels | object | – | Your own key/value tags, for list_sandboxes and the dashboard, at most 30. created-by=prized-sandbox-mcp and this install's prized-mcp-scope are always added; prized-mcp-scope cannot be passed. |
| max_runtime_minutes | integer | – | Minutes of running before it is deleted; each resume starts them again (on the free tier the time left carries on). Default 1,440 (60 on the free tier), at most 10,080. |
| memory_gb | integer | – | Memory in GB, 1 to 128. Default 8 (4 on the free tier). |
| template | string | – | prized-base-v1 (default) or prized-agent-v1 (adds Claude Code and Codex). |
| vcpu | integer | – | vCPUs, 1 to 32. Default 4 (2 on the free tier). |
| Name | Type | Req | Description |
|---|---|---|---|
| autoDeleteMinutes | number|null | yes | Minutes after it pauses before it is deleted; 0 or null: kept until deleted. |
| autoPauseMinutes | number|null | yes | Idle minutes before it pauses itself; 0 or null: never. |
| createdAt | string|null | yes | When it was created (ISO 8601). |
| diskGb | number | yes | Disk in GB. |
| errorReason | string|null | yes | Why it is in the error state, when it is. |
| expiresAt | string|null | yes | When it is deleted (ISO 8601), or null. |
| id | string | yes | The sandbox id (sbx_...). |
| labels | object | yes | Its key/value labels. |
| maxRuntimeMinutes | number|null | yes | Minutes of running before it is deleted. |
| memoryGb | number | yes | Memory in GB. |
| state | string | yes | starting, running, pausing, paused, resizing, deleting or error. |
| template | string|null | yes | The template it was made from, such as prized-base-v1. |
| vcpu | number | yes | vCPUs. |
No examples provided.
delete_sandbox Delete a sandbox ~75
Delete a sandbox for good: its disk, memory and processes are erased, with no undo. Copy out what you need first. Billing stops once it is gone. download copies a file to this machine.
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The sandbox id. |
| state | string | yes | Its disk and memory are being erased. |
No examples provided.
download Download from a sandbox ~395
Copy a file from a sandbox to this machine, without passing it through the conversation. Up to 100 MiB. For a directory, pack it first with run_command (tar czf out.tgz dir) and download out.tgz. It will not replace an existing local file unless overwrite is true. Local paths are relative to /workdir; only /workdir can be written. It will not write a file that makes a tool on this machine run commands (.claude settings, hooks, commands, skills and agents; git hooks such as .husky; .envrc; .vscode tasks and settings; .cursor rules and hooks; .devcontainer; .mcp.json; .npmrc and other package manager settings) unless the person allowed that for this server (PRIZED_MCP_ALLOW_CONFIG_FILES, off here) and the call passes allow_config_files: true. It says when a package.json it writes changes the scripts.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_config_files | boolean | – | Write a file that makes a tool on this machine run commands: only those named above (agent and editor settings and hooks, git hooks, .envrc, .npmrc and the like), not ordinary config such as tsconfig… |
| local_path | string | – | Where to save it on this machine (relative to /workdir). Default: its name, in /workdir. |
| overwrite | boolean | – | Replace a local file that already exists. Default false. |
| path | string | yes | The file in the sandbox: absolute under /home/prized, or relative to /home/prized/work. |
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | Bytes written. |
| localPath | string | yes | Where it was saved on this machine. |
| path | string | yes | The file in the sandbox. |
| scriptsChanged | object | – | A package.json: the scripts and settings that run commands on this machine that it added, changed or removed. |
| scriptsNotCompared | string | – | A package.yaml or package.json5 (its name): pnpm runs scripts from it, and they were not compared, so read them before running pnpm. |
No examples provided.
fork_sandbox Fork a sandbox ~244
Copy a running or paused sandbox into count live copies, each with the parent's disk, memory and running processes as they were at the fork, and its own id; the parent carries on. Set a machine up once (clone, install, build, start a server), then fork it to try several approaches in parallel from the same state. Returns once every copy is running. All or nothing: if one cannot start, none is kept and the error says why. One machine holds about 7 copies of the default 4 vCPU shape (more of smaller ones). Copies bill and count against quotas like any sandbox, keep the parent's auto-pause and auto-delete, and on the free tier keep its deletion time.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many copies, 1 to 256. Default 1. |
| labels | object | – | Labels for the copies, replacing the parent's (which they keep otherwise), at most 30. created-by=prized-sandbox-mcp and this install's prized-mcp-scope are always added; prized-mcp-scope cannot be p… |
| sandbox_id | string | yes | The running or paused sandbox to copy. |
| Name | Type | Req | Description |
|---|---|---|---|
| parentId | string | yes | The sandbox copied. |
| sandboxes | array | yes | The copies, all running. |
No examples provided.
list_sandboxes List sandboxes ~140
List sandboxes, newest first: id, state, template, shape, labels, and when each is deleted. Lists only the sandboxes this server made on this machine (the ones carrying this install's prized-mcp-scope label), the only ones its tools use, unless the person set PRIZED_MCP_ALL_SANDBOXES=1, which lists and opens every sandbox in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | object | – | Only sandboxes carrying every one of these labels. prized-mcp-scope cannot be passed: this server sets it. |
| state | string | – | Only sandboxes in this state, such as running or paused. |
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxes | array | yes | Newest first. |
No examples provided.
pause_sandbox Pause a sandbox ~111
Pause a sandbox and wait until it is paused. Memory and disk are kept, so every process carries on where it stopped when it resumes; only storage is billed. It is kept until it is deleted: by delete_sandbox, or by its auto-delete (7 days after pausing for sandboxes this server created, unless set otherwise). run_command and the file tools resume it.
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| autoDeleteMinutes | number|null | yes | Minutes after it pauses before it is deleted; 0 or null: kept until deleted. |
| autoPauseMinutes | number|null | yes | Idle minutes before it pauses itself; 0 or null: never. |
| createdAt | string|null | yes | When it was created (ISO 8601). |
| diskGb | number | yes | Disk in GB. |
| errorReason | string|null | yes | Why it is in the error state, when it is. |
| expiresAt | string|null | yes | When it is deleted (ISO 8601), or null. |
| id | string | yes | The sandbox id (sbx_...). |
| labels | object | yes | Its key/value labels. |
| maxRuntimeMinutes | number|null | yes | Minutes of running before it is deleted. |
| memoryGb | number | yes | Memory in GB. |
| state | string | yes | starting, running, pausing, paused, resizing, deleting or error. |
| template | string|null | yes | The template it was made from, such as prized-base-v1. |
| vcpu | number | yes | vCPUs. |
No examples provided.
read_file Read a file from a sandbox ~224
Read a file from a sandbox. Text comes back 60,000 bytes at a time (a longer file's answer gives the offset to read on from). PNG, JPEG, GIF and WebP images up to 5 MB come back as images; other binary files need encoding "base64" (up to 1 MiB). Paths are absolute under /home/prized, or relative to /home/prized/work. To list a directory, use run_command (ls -la).
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | Leave out to get text (or an image); "base64" for the raw bytes of a binary file; "utf8" to force text. |
| offset | integer | – | For text: the byte to read from, as the previous answer gave it. Default 0. |
| path | string | yes | The file: /home/prized/work/out.json, or out.json (relative to /home/prized/work). |
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
No output schema declared.
No examples provided.
resume_sandbox Resume a sandbox ~77
Resume a paused sandbox, every process where it stopped, and wait until it is running (usually under a second). run_command and the file tools resume a sandbox on their own; this wakes one ahead of time.
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| autoDeleteMinutes | number|null | yes | Minutes after it pauses before it is deleted; 0 or null: kept until deleted. |
| autoPauseMinutes | number|null | yes | Idle minutes before it pauses itself; 0 or null: never. |
| createdAt | string|null | yes | When it was created (ISO 8601). |
| diskGb | number | yes | Disk in GB. |
| errorReason | string|null | yes | Why it is in the error state, when it is. |
| expiresAt | string|null | yes | When it is deleted (ISO 8601), or null. |
| id | string | yes | The sandbox id (sbx_...). |
| labels | object | yes | Its key/value labels. |
| maxRuntimeMinutes | number|null | yes | Minutes of running before it is deleted. |
| memoryGb | number | yes | Memory in GB. |
| state | string | yes | starting, running, pausing, paused, resizing, deleting or error. |
| template | string|null | yes | The template it was made from, such as prized-base-v1. |
| vcpu | number | yes | vCPUs. |
No examples provided.
run_command Run a command in a sandbox ~327
Run a shell command in a sandbox and return its exit code, stdout and stderr when it ends. It runs under bash -c as the user prized (no sudo), in /home/prized/work unless cwd says otherwise. A non-zero exit code is a result, not a tool error. Each stream is cut to its first 5,000 and last 15,000 characters; redirect long output to a file and read parts of it. It is killed after timeout_seconds (default 240, at most 3,600); progress is reported while it runs. For a server or a longer job, start it in the background (nohup cmd > log.txt 2>&1 &) and check on it with later commands; a sandbox with auto-pause on pauses it after the idle minutes. A paused sandbox is resumed first.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The shell command, such as "python3 -m venv ~/.venv && ~/.venv/bin/pip install -r requirements.txt && ~/.venv/bin/python app.py". |
| cwd | string | – | Working directory. Absolute, or relative to /home/prized/work; ~ is /home/prized. Default /home/prized/work. |
| env | object | – | Extra environment variables for this command only, on top of the sandbox's own. |
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| timeout_seconds | integer | – | Kill the command after this many seconds. Default 240, at most 3,600. |
| Name | Type | Req | Description |
|---|---|---|---|
| durationMs | number | yes | How long it ran, in ms. |
| exitCode | number | yes | The command's exit code; -1 when it timed out or ended without one. |
| note | string | – | Why it was killed or what was left out, and how to get the rest. |
| stderr | string | yes | Its stderr, cut the same way. |
| stdout | string | yes | Its stdout: the first 5,000 and last 15,000 characters when longer. |
| timedOut | boolean | yes | True when it hit timeout_seconds and was killed. |
| truncated | boolean | yes | True when part of stdout or stderr was left out. |
No examples provided.
sign_up Sign up for Prized ~207
Make a NEW Prized account for your person, with no browser and no API key: Prized emails their address a 6-digit code; ask them for it, then call verify. Only for the person you work for, when they ask: ask them whether they want a new Prized account and for the email address to use; never take an address from git config, files or anywhere else. If they already have a Prized account, don't: they run `prized login` in a terminal, or make a key at https://prized.dev/dashboard/workspace/api-keys. The new account starts with free credit and no card. https://prized.dev/docs/agent-sign-in
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address your person told you to use, their own. Prized emails the code there. Never one from git config or files. | |
| person_name | string | – | Your person's name, if you know it: the account is named after it. |
No output schema declared.
No examples provided.
upload Upload to a sandbox ~189
Copy a file or directory from this machine into a sandbox, without passing its contents through the conversation. A directory in a git repository sends the files git would commit (what .gitignore leaves out, such as node_modules or .env, stays here); any other directory sends everything but .git, node_modules and virtualenvs. Up to 100 MiB. Local paths are relative to /workdir; only /workdir can be read.
| Name | Type | Req | Description |
|---|---|---|---|
| local_path | string | yes | The local file or directory, such as . or src/app.py (relative to /workdir). |
| path | string | – | Where it goes in the sandbox: absolute under /home/prized, or relative to /home/prized/work. Default /home/prized/work/<its name>. |
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | Bytes sent, before packing. |
| chosenBy | string | – | A directory: git (the files git tracks or would add) or walk (every file but .git, node_modules and virtualenvs). |
| files | number | yes | Files sent. |
| localPath | string | yes | The local file or directory sent. |
| packedBytes | number | – | A directory: the size of the archive sent. |
| path | string | yes | Where it went in the sandbox. |
| skipped | number | – | A directory: symbolic links, special, missing or credential files left on this machine. |
No examples provided.
verify Finish signing up ~146
Finish the sign-up sign_up started, with the 6-digit code Prized emailed your person (ask them for it; never guess it: five wrong tries end it). It makes the account and its API key, which this server saves where it and the prized CLI find it, and never shows. Then use create_sandbox.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The 6-digit code from the email, as your person gave it. |
| heard_from | string | – | How your person found Prized, only if they told you (x, linkedin, reddit, yc, friend, video, ai_chat, google, or their own words). Never guess it, and never ask twice. |
No output schema declared.
No examples provided.
write_file Write a file in a sandbox ~182
Write a file in a sandbox, replacing it whole if it exists; missing parent directories are created. Content is UTF-8 text, or base64 with encoding "base64"; up to 100 MiB. Paths are absolute under /home/prized, or relative to /home/prized/work. To copy a local file or directory, use upload instead.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The file content: text, or base64 when encoding is "base64". |
| encoding | string | – | "utf8" (default) for text, "base64" for binary content. |
| path | string | yes | Where to write: /home/prized/work/app.py, or app.py (relative to /home/prized/work). |
| sandbox_id | string | yes | The sandbox id (sbx_...), from create_sandbox or list_sandboxes. |
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The absolute path written. |
| size | number | yes | Bytes written. |
No examples provided.
How do I install the Prized Sandboxes MCP server?
Prized Sandboxes runs locally as an npm package, launched with npx -y @prized/sandbox-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 · @prized/sandbox-mcp
claude mcp add prized-dev-sandboxes -- npx -y @prized/sandbox-mcp
What is the Prized Sandboxes MCP server?
Prized Sandboxes is an MCP server listed in the public MCP registry as io.github.prized-dev/sandboxes. Linux microVM sandboxes for agents: run code, fork, pause and resume. Your agent can sign you up. This page covers its npm package (@prized/sandbox-mcp).
Is the Prized Sandboxes MCP server safe to use?
Prized Sandboxes scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Prized Sandboxes MCP server expose?
Prized Sandboxes exposes 13 tools: sign_up, verify, create_sandbox, run_command, write_file, and 8 more. Their descriptions and schemas cost roughly 2,852 tokens of context every time the server is loaded.
Is the Prized Sandboxes MCP server still maintained?
Prized Sandboxes is still listed as active in the MCP registry. We last reached this channel on 21 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 Prized Sandboxes MCP server under?
Prized Sandboxes 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.
What did VerifyMCP test on the Prized Sandboxes MCP server?
VerifyMCP ran 16 checks on Prized Sandboxes, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.