LLM Sandbox vs SanctionsKit developer MCP
A side-by-side look at the LLM Sandbox and SanctionsKit developer MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LLM Sandbox for code execution work; choose SanctionsKit developer MCP for code execution. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose LLM Sandbox when
- You need dedicated capabilities in the Code Execution domain.
- You want tools like
execute_code, get_supported_languages, get_language_details.
Choose SanctionsKit developer MCP when
- You need dedicated capabilities in the Code Execution domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 53/100 · Good | 29/100 · Emerging |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,130 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View LLM Sandbox | View SanctionsKit developer MCP |
Tools & capabilities
LLM Sandbox tools 3
execute_codeget_supported_languagesget_language_details
SanctionsKit developer MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
LLM Sandbox
No confirmed install command for LLM Sandbox yet — follow the setup steps linked from its listing page rather than a guessed package name.
SanctionsKit developer MCP
No confirmed install command for SanctionsKit developer MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
LLM Sandbox is categorized under Code Execution and uses an install path we have not confirmed yet. SanctionsKit developer MCP belongs to Code Execution and uses an install path we have not confirmed yet. Pick LLM Sandbox for code execution work and SanctionsKit developer MCP for code execution.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
LLM Sandbox has no declared pricing — check the project's own site. SanctionsKit developer MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add llm-sandbox and sanctionskit-developer-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LLM Sandbox has a quality signal of 53/100 (Good) with 3 views, 0 installs and 1,130 GitHub stars. SanctionsKit developer MCP has 29/100 (Emerging) with 0 views, 0 installs and 1 GitHub stars.