Sandboxd Code Run
REMOTE · SANDBOXD-CODE-RUN.SAASTEMLY.COM · SCANNED OCT 2
Hosted one-shot code execution: send a snippet plus optional files, get stdout, stderr, exit...
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 569 tokens (~284/item across 2 items; 2 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 Management3
- Stability observed for 1 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute-code" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Sandboxd Code Run MCP server?
Sandboxd Code Run is a hosted endpoint at https://sandboxd-code-run.saastemly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sandboxd-code-run.saastemly.com
claude mcp add --transport http com-saastemly-sandboxd-code-run 'https://sandboxd-code-run.saastemly.com/mcp'
{
"mcpServers": {
"com-saastemly-sandboxd-code-run": {
"url": "https://sandboxd-code-run.saastemly.com/mcp"
}
}
} {
"servers": {
"com-saastemly-sandboxd-code-run": {
"type": "http",
"url": "https://sandboxd-code-run.saastemly.com/mcp"
}
}
} [mcp_servers.com-saastemly-sandboxd-code-run] url = "https://sandboxd-code-run.saastemly.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-saastemly-sandboxd-code-run": {
"type": "remote",
"url": "https://sandboxd-code-run.saastemly.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-saastemly-sandboxd-code-run --url 'https://sandboxd-code-run.saastemly.com/mcp' --transport streamable-http
mcp_servers:
com-saastemly-sandboxd-code-run:
url: "https://sandboxd-code-run.saastemly.com/mcp" {
"McpServers": {
"com-saastemly-sandboxd-code-run": {
"Transport": "http",
"Url": "https://sandboxd-code-run.saastemly.com/mcp"
}
}
} assistant mcp add com-saastemly-sandboxd-code-run -t streamable-http -u 'https://sandboxd-code-run.saastemly.com/mcp'
{
"mcpServers": {
"com-saastemly-sandboxd-code-run": {
"type": "http",
"url": "https://sandboxd-code-run.saastemly.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 55
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 2 Oct 2026 · Probed https://sandboxd-code-run.saastemly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saastemly.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c2945907687f074a0eb16d40fea074d5 |
| SANs: saastemly.com, sandboxd-code-run.saastemly.com, *.sandboxd-code-run.saastemly.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sandboxd-code-run.saastemly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| saastemly.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sandboxd-code-run.saastemly.com/mcp | Verified | 200 | |
| http (plaintext) | http://sandboxd-code-run.saastemly.com/mcp | Inconclusive | 405 |
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 →
execute-code Runs Python, JavaScript or TypeScript code in an isolated one-shot sandbox and r ~272
Runs Python, JavaScript or TypeScript code in an isolated one-shot sandbox and returns stdout, stderr, exit code and artifacts (Daytona CodeRunRequest/ExecuteResponse compatible) Price: $0.002 a call.
| Name | Type | Req | Description |
|---|---|---|---|
| argv | array | – | Command-line arguments for the program (sys.argv[1:] in Python, process.argv.slice(2) in Node) |
| code | string | yes | The code to run (up to 1 MB of UTF-8) |
| env | object | – | Environment variables; keys must match [A-Za-z_][A-Za-z0-9_]* (Daytona's rule) |
| files | object | – | Text files written into the work directory next to the program (up to 50, 1 MB each, 4 MB total); the entry point main.py/main.js/main.ts is reserved |
| language | string | yes | "python", "javascript" or "typescript" |
| outputs | array | – | Relative paths to read back after the run (up to 20); up to 1 MB each comes back base64 in outputFiles, larger in tooLargeOutputs, absent in missingOutputs |
| timeout | integer | – | Run timeout in seconds, 1-120 (default 60); a timed-out run answers exitCode 124 |
No output schema declared.
No examples provided.
execute-command Runs a shell command in an isolated one-shot sandbox and returns stdout, stderr ~220
Runs a shell command in an isolated one-shot sandbox and returns stdout, stderr and the exit code (Daytona ExecuteRequest/ExecuteResponse compatible) Price: $0.002 a call.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The shell command to run (up to 64 KB) |
| cwd | string | – | Working directory, relative to the run's work directory |
| env | object | – | Environment variables; keys must match [A-Za-z_][A-Za-z0-9_]* (Daytona's rule) |
| files | object | – | Text files written into the work directory before the run (up to 50, 1 MB each, 4 MB total) |
| outputs | array | – | Relative paths to read back after the run (up to 20); up to 1 MB each comes back base64 in outputFiles, larger in tooLargeOutputs, absent in missingOutputs |
| timeout | integer | – | Run timeout in seconds, 1-120 (default 60); a timed-out run answers exitCode 124 |
No output schema declared.
No examples provided.
What is the Sandboxd Code Run MCP server?
Sandboxd Code Run is an MCP server listed in the public MCP registry as com.saastemly/sandboxd-code-run. Hosted one-shot code execution: send a snippet plus optional files, get stdout, stderr, exit... This page covers its hosted endpoint (https://sandboxd-code-run.saastemly.com/mcp).
Is the Sandboxd Code Run MCP server safe to use?
Sandboxd Code Run scores 56 out of 100 on VerifyMCP. 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 Sandboxd Code Run MCP server expose?
Sandboxd Code Run exposes 2 tools: execute-code, execute-command. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.
Does the Sandboxd Code Run MCP server require authentication?
No. We connected to Sandboxd Code Run without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sandboxd Code Run MCP server still maintained?
Sandboxd Code Run is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.