mcp-registry/io.github.csoai-org/code-executor-mcp/run_command / alternatives

Live alternatives to mcp-registry/io.github.csoai-org/code-executor-mcp/run_command

The best live alternatives to mcp-registry/io.github.csoai-org/code-executor-mcp/run_command right now are mcp-registry/sh.agentdrive/agentdrive/drive_sandbox_exec, mcp-registry/com.vandorla/workspace-tools/execute_command, mcp-registry/io.github.rubentay/agent-vending-factory/tool_compute_sandbox, mcp-registry/io.github.lastmanupinc-hub/axis-toolbox/iliad_code_sandbox, mcp-registry/com.obsmetrics.paygent/agents/tool-call-guard — capability-matched and ranked by current reliability. mcp-registry/io.github.csoai-org/code-executor-mcp/run_command itself is currently "unknown".

alternative	server
mcp-registry/sh.agentdrive/agentdrive/drive_sandbox_exec	sh.agentdrive/agentdrive	live status →
mcp-registry/com.vandorla/workspace-tools/execute_command	com.vandorla/workspace-tools	live status →
mcp-registry/io.github.rubentay/agent-vending-factory/tool_compute_sandbox	io.github.RubenTay/agent-vending-factory	live status →
mcp-registry/io.github.lastmanupinc-hub/axis-toolbox/iliad_code_sandbox	io.github.lastmanupinc-hub/axis-toolbox	live status →
mcp-registry/com.obsmetrics.paygent/agents/tool-call-guard	com.obsmetrics.paygent/agents	live status →
pulsemcp/x711/x711_code_sandbox	x711	live status →
mcp-registry/io.github.keploy/mcp/replay_sandbox_test	io.github.keploy/mcp	live status →
mcp-registry/io.github.keploy/mcp/devloop_switch_to_sandbox	io.github.keploy/mcp	live status →
mcp-registry/sh.agentdrive/agentdrive/drive_sandbox_commit	sh.agentdrive/agentdrive	live status →
mcp-registry/space.customjs/customjs-mcp/customjs_run_code	space.customjs/customjs-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.csoai-org/code-executor-mcp/run_command?

mcp-registry/sh.agentdrive/agentdrive/drive_sandbox_exec is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.vandorla/workspace-tools/execute_command, mcp-registry/io.github.rubentay/agent-vending-factory/tool_compute_sandbox, mcp-registry/io.github.lastmanupinc-hub/axis-toolbox/iliad_code_sandbox, mcp-registry/com.obsmetrics.paygent/agents/tool-call-guard. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.csoai-org/code-executor-mcp/run_command down right now?

mcp-registry/io.github.csoai-org/code-executor-mcp/run_command's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.csoai-org%2Fcode-executor-mcp%2Frun_command.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.csoai-org%2Fcode-executor-mcp%2Frun_command or MCP find_alternatives. Check mcp-registry/io.github.csoai-org/code-executor-mcp/run_command's live status: https://glimind.com/tool/mcp-registry/io.github.csoai-org/code-executor-mcp/run_command.