Code Sandbox (npm) MCP Server
code-sandbox-mcp
npm
v1.0.8
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Codebox MCP provides remote coding environment for AI and agents. It allows AI to act in agent mode to fully automatically develop any apps or websites or data analysis scripts at your request (python, js, desktop electron apps or anything).
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 6
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([runbox_read_file]) and tools that can send data out ([runbox_execute_command]) are exposed together. An agent can move private data to the sink.
Evidence: sources [runbox_read_file] → sinks [runbox_execute_command]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow runbox_read_file → runbox_execute_command
high Tool "runbox_execute_command" exposes command/code executionMTC-CAP-001
Tool "runbox_execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool runbox_execute_command
high Shell/command execution in server code (build/index.js)MTC-SRC-002
In the server's implementation (`build/index.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; import { exec } from "child_process"; import { promisify } from "util"; // Override console.log and console.error for
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/index.js
medium Tool "runbox_write_file" can modify the filesystemMTC-CAP-002
Tool "runbox_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool runbox_write_file
low Mutating tool "runbox_write_file" declares no destructiveHintMTC-CAP-005
Tool "runbox_write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool runbox_write_file
low Mutating tool "runbox_execute_command" declares no destructiveHintMTC-CAP-005
Tool "runbox_execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool runbox_execute_command
Tools 7
Each tool and what it can reach — statically extracted from the published source.
runbox_execute_commandruns code / shellrunbox_read_filereads sensitive datarunbox_write_filewrites filesrunbox_create_sandboxno sensitive capabilityrunbox_expose_portno sensitive capabilityrunbox_list_directoryno sensitive capabilityrunbox_serve_static_websiteno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.8 latest |
A 92/100 | 6 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan code-sandbox-mcp --onlineOther implementations of Code Sandbox 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.