Exec Sandbox vs RLM Tools
Exec Sandbox is an MCP server published by inhuman. Marketplaces we read that list it: 1 (Official MCP Registry). RLM Tools is an MCP server published by stefanoshea. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Exec Sandbox |  RLM Tools |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.4 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 63 Downloads/week (PyPI): 13 Forks (GitHub): 4 Stars (GitHub): 8 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Exec Sandbox | RLM Tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (docker.io/idconstruct/mcp-exec:v0.5.4) | On your machine (rlm-tools) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/inhuman/mcp-exec | github.com/stefanoshea/rlm-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Exec Sandbox
Single exec tool running caller Python in a network-isolated locked-down sandbox.
RLM Tools
Persistent Python sandbox for token-efficient codebase exploration in MCP clients
How to run each
Exec Sandbox As a local MCP server: Docker image
claude mcp add --env "MCP_EXEC_AUTH_TOKEN=<YOUR_MCP_EXEC_AUTH_TOKEN>" --transport stdio mcp-exec -- docker run -i --rm -e MCP_EXEC_AUTH_TOKEN --network none --cap-drop ALL --security-opt no-new-privileges --user 65532:65532 --tmpfs /tmp:rw,noexec,nosuid,size=64m --memory 256m --pids-limit 128 --cpus 1 docker.io/idconstruct/mcp-exec:v0.5.4Requires: MCP_EXEC_AUTH_TOKEN (secret)
RLM Tools As a local MCP server: PyPI package
claude mcp add --transport stdio rlm-tools -- uvx rlm-toolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of RLM Tools publish no settings it asks for, so we do not compare settings.
What it can do: Exec Sandbox · What it can do: RLM Tools · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.