E2B vs CleanCode AI
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). CleanCode AI is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 229 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | CleanCode AI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 393 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 23 229 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 72 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | Remote server (cleancode-ai-mcp.vercel.app/api/mcp) |
| Transport (differs) | stdio | SSE |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/e2b-dev/mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (2 days 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).
CleanCode AI
Automated codebase refactoring and type safety validator.
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)
CleanCode AI As a remote MCP server
claude mcp add --transport sse cleancode-ai https://cleancode-ai-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only CleanCode AI has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of CleanCode AI publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of CleanCode AI publish no settings it asks for, so we do not compare settings.
What it can do: E2B · What it can do: CleanCode AI · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.