upstream-backport vs io.github.OtaKit/otakit
upstream-backport is a plugin bundle for AI coding tools published by JZ Loh. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.OtaKit/otakit is an MCP server published by OtaKit. Marketplaces we read that list it: 2 (Official MCP Registry, 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 |  io.github.OtaKit/otakit | |
|---|---|---|
| Community marketplace bitshelf/linux-skills | Not seen in the last pass Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.10.0 Downloads/month (npm): 6 454 Downloads/week (npm): 1 166 Forks (GitHub): 1 Stars (GitHub): 47 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 | upstream-backport | io.github.OtaKit/otakit |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 47 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 8 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bitshelf/linux-skills | github.com/otakit/otakit |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 25 h ago | not checked yet |
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
upstream-backport
免克隆取证 + 五阶段 backport 工作流（Buildroot/Yocto/AOSP/Debian/内核）
io.github.OtaKit/otakit
Inspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates.
How to run each
upstream-backport As a Claude Code plugin
/plugin marketplace add bitshelf/linux-skills
/plugin install upstream-backport@embedded-backport-toolsio.github.OtaKit/otakit As a remote MCP server
claude mcp add --transport http otakit https://console.otakit.app/mcpCommands 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: upstream-backport · What it can do: io.github.OtaKit/otakit · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.