Sandbox Studio MCP Server

sandbox-studio-mcp npm v1.0.3

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.

A local MCP server for the Sandbox Studio API

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

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:

PointsAdoption-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 4

high Tool "update_cleanup_hook" exposes command/code executionMTC-CAP-001

Tool "update_cleanup_hook" appears to run shell commands or evaluate code (parameter "script"). 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 update_cleanup_hook

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([list_accounts, list_unregistered_accounts, get_account_lease_history, list_approvals, list_events, list_leases, list_public_templates, list_managed_templates, get_template_leases, list_users, list_groups]) co-exist with external-action tools ([update_cleanup_hook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [list_accounts, list_unregistered_accounts, get_account_lease_history, list_approvals, list_events, list_leases, list_public_templates, list_managed_t

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow list_accounts → update_cleanup_hook

medium Unconstrained command parameter "script" on "update_cleanup_hook"MTC-CAP-006

Tool "update_cleanup_hook" takes a command-shaped parameter "script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool update_cleanup_hook · inputSchema.properties.script

low Mutating tool "update_cleanup_hook" declares no destructiveHintMTC-CAP-005

Tool "update_cleanup_hook" 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 update_cleanup_hook

Tools 81

Each tool and what it can reach — statically extracted from the published source.

  • get_account_lease_historyingests untrusted input
  • get_template_leasesingests untrusted input
  • list_accountsingests untrusted input
  • list_approvalsingests untrusted input
  • list_eventsingests untrusted input
  • list_groupsingests untrusted input
  • list_leasesingests untrusted input
  • list_managed_templatesingests untrusted input
  • list_public_templatesingests untrusted input
  • list_unregistered_accountsingests untrusted input
Show 71 more tools ↓
  • list_usersingests untrusted input
  • update_cleanup_hookruns code / shell
  • add_event_teamsno sensitive capability
  • assign_event_team_ownerno sensitive capability
  • create_eventno sensitive capability
  • create_oauth_clientno sensitive capability
  • create_templateno sensitive capability
  • delete_oauth_clientno sensitive capability
  • delete_templateno sensitive capability
  • eject_accountsno sensitive capability
  • get_accountno sensitive capability
  • get_account_cleanup_logsno sensitive capability
  • get_account_failed_resourcesno sensitive capability
  • get_cleanup_hookno sensitive capability
  • get_cleanup_settingsno sensitive capability
  • get_email_settingsno sensitive capability
  • get_eventno sensitive capability
  • get_event_teamsno sensitive capability
  • get_global_configno sensitive capability
  • get_leaseno sensitive capability
  • get_lease_costsno sensitive capability
  • get_lease_logsno sensitive capability
  • get_lease_secretsno sensitive capability
  • get_lease_team_membersno sensitive capability
  • get_runtime_configno sensitive capability
  • get_smtp_settingsno sensitive capability
  • get_tagsno sensitive capability
  • get_templateno sensitive capability
  • get_template_infono sensitive capability
  • get_template_launch_settingsno sensitive capability
  • get_template_permissionsno sensitive capability
  • get_terms_of_serviceno sensitive capability
  • get_terms_versionno sensitive capability
  • import_accountsno sensitive capability
  • list_all_oauth_clientsno sensitive capability
  • list_my_oauth_clientsno sensitive capability
  • list_terms_versionsno sensitive capability
  • provision_eventno sensitive capability
  • publish_terms_of_serviceno sensitive capability
  • request_leaseno sensitive capability
  • resume_leaseno sensitive capability
  • retry_account_cleanupno sensitive capability
  • review_leaseno sensitive capability
  • send_test_emailno sensitive capability
  • share_leaseno sensitive capability
  • start_eventno sensitive capability
  • suspend_leaseno sensitive capability
  • terminate_eventno sensitive capability
  • terminate_leaseno sensitive capability
  • trigger_drift_detectionno sensitive capability
  • trigger_lease_monitoringno sensitive capability
  • unshare_leaseno sensitive capability
  • update_cleanup_settingsno sensitive capability
  • update_email_settingsno sensitive capability
  • update_eventno sensitive capability
  • update_global_configno sensitive capability
  • update_leaseno sensitive capability
  • update_oauth_clientno sensitive capability
  • update_preferencesno sensitive capability
  • update_smtp_settingsno sensitive capability
  • update_template_budgetno sensitive capability
  • update_template_durationno sensitive capability
  • update_template_infono sensitive capability
  • update_template_launch_settingsno sensitive capability
  • update_template_managersno sensitive capability
  • update_template_permissionsno sensitive capability
  • update_template_sharingno sensitive capability
  • update_template_tagsno sensitive capability
  • validate_s3_pathno sensitive capability
  • validate_usersno sensitive capability
  • withdraw_leaseno 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

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.

VersionScoreFindingsEngineScanned
v1.0.3 latest A 92/100 4 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.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sandbox-studio-mcp/badge.svg)](https://mcptrustchecker.com/registry/sandbox-studio-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/sandbox-studio-mcp"><img src="https://mcptrustchecker.com/registry/sandbox-studio-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sandbox-studio-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 sandbox-studio-mcp --online

Use the free API → How scoring works

More in Cloud & DevOps