E2B vs Utilix
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). Utilix is an MCP server published by utilix-tech. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-13. 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 |  E2B |  Utilix |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 73 Pulls (Docker Hub): 23 961 Stars (Docker Hub): 2 Stars (GitHub): 394 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.106.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.106.0 Downloads/month (npm): 3 452 Downloads/week (npm): 1 016 Forks (GitHub): 0 Stars (GitHub): 0 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 | E2B | Utilix |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 394 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 23 961 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 73 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-13 |
| Where it runs (differs) | On your machine (mcp/e2b) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/utilix-tech/utilix-mcp |
| Changes in the last 7 days (differs) | 0 | 20 or more |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 11 h ago |
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
E2B
Giving Claude ability to run code with E2B via MCP (Model Context Protocol).
Utilix
300+ offline developer utilities, plus 21 AI tools with a free API key. JSON, JWT, regex, cron, SQL.
How to run each
E2B As a local MCP server: Docker image
claude mcp add --env "E2B_API_KEY=<YOUR_E2B_API_KEY>" --transport stdio e2b -- docker run -i --rm -e E2B_API_KEY mcp/e2bRequires: E2B_API_KEY (secret)
Utilix As a remote MCP server
claude mcp add --transport http utilix-mcp https://mcp.utilix.tech --header "Authorization: Bearer <YOUR_TOKEN>"Requires: UTILIX_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Utilix has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Utilix publish no list of tools, so we do not compare tools.
Settings each asks for
Only E2B asks for
E2B_API_KEY (secret)
Only Utilix asks for
UTILIX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: E2B · What it can do: Utilix · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.