E2B vs upstream-backport
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). upstream-backport is a plugin bundle for AI coding tools published by JZ Loh. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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 234 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Not listed |
| Community marketplace bitshelf/linux-skills | Not listed | Not seen in the last pass Version: 1.0.1 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 | upstream-backport |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 393 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 23 234 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 72 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | Remote server (mcp.deepwiki.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/bitshelf/linux-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 24 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).
upstream-backport
免克隆取证 + 五阶段 backport 工作流（Buildroot/Yocto/AOSP/Debian/内核）
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)
upstream-backport As a Claude Code plugin
/plugin marketplace add bitshelf/linux-skills
/plugin install upstream-backport@embedded-backport-toolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only upstream-backport has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of upstream-backport publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of upstream-backport publish no settings it asks for, so we do not compare settings.
What it can do: E2B · What it can do: upstream-backport · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.