Yukkit E2b MCP Server
@yukkit/e2b-mcp-server
npm
v0.6.0
Source verified
Published by yukkit — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
A Model Context Protocol server
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 − 3.6 = 96. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −3.6 | Near-miss of exa-mcp-server MTC-SUP-005 | supply-chain |
2. Client adoption risk — 96 − 10 = 86. 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 |
|---|---|
| −10 | capability blast radius (critical) — client exposure if the model is manipulated |
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 8
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: get_file_download_url → list_files → run_code. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow get_file_download_url → list_files → run_code
high Tool "run_command" exposes command/code executionMTC-CAP-001
Tool "run_command" appears to run shell commands or evaluate code (keyword "run_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 run_command
high Tool "run_code" exposes command/code executionMTC-CAP-001
Tool "run_code" appears to run shell commands or evaluate code (keyword "run_code" 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 run_code
medium Tool "write_file" can modify the filesystemMTC-CAP-002
Tool "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 write_file
medium Near-miss of exa-mcp-server (edit distance 2)MTC-SUP-005
"@yukkit/e2b-mcp-server" is edit-distance 2 from the package "exa-mcp-server". Verify this is the intended package.
Fix: Confirm you meant "exa-mcp-server". Install packages only from their documented, official name.
Location: package @yukkit/e2b-mcp-server
low Mutating tool "run_command" declares no destructiveHintMTC-CAP-005
Tool "run_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 run_command
low Mutating tool "write_file" declares no destructiveHintMTC-CAP-005
Tool "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 write_file
low Mutating tool "run_code" declares no destructiveHintMTC-CAP-005
Tool "run_code" 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 run_code
Tools 10
Each tool and what it can reach — statically extracted from the published source.
get_file_download_urlingests untrusted inputlist_filesreads sensitive dataread_filereads sensitive datarun_coderuns code / shellrun_commandruns code / shellwrite_filewrites filescreate_sandboxno sensitive capabilityget_sandbox_urlno sensitive capabilitykill_sandboxno sensitive capabilitylist_sandbox_idsno 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 (10 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 |
|---|---|---|---|---|
v0.6.0 latest |
B 86/100 | 8 | 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 @yukkit/e2b-mcp-server --onlineOther implementations of Yukkit E2b 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
E2B’s official MCP server: run code safely in isolated cloud sandboxes.
E2B MCP Server
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.