bns-dev vs Arm MCP Server
bns-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
bns-dev is a plugin bundle for AI coding tools published by chekos. No marketplace we read lists it any more. Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Arm MCP Server | |
|---|---|---|
| Community marketplace chekos/bns-marketplace | Removed on 2026-10-20 Version: 0.2.0 Forks (GitHub): 3 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.4.0 Forks (GitHub): 22 Stars (GitHub): 94 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:ea7c4d1daeb9 Forks (GitHub): 22 Stars (GitHub): 94 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 | bns-devno longer listed · | Arm MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 5 | 94 |
| Forks (GitHub) (differs) | 3 | 22 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (docker.io/armlimited/arm-mcp:2.4.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 7 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/chekos/bns-marketplace | github.com/arm/mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of bns-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.
-
Blaxel is the perpetual sandbox platform. It lets you keep infinite, secure sandboxes on automatic standby, while co-hosting your agents and context for near instant latency. The…
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
What each says it does
bns-dev
The brasas & nube development plugin. Ships the image-generator skill (Gemini Nano Banana Pro image generation) and the repo-modernization-auditor skill (audit and modernize aging repos to be clean, current, safe, and agent-friendly); home for dev tooling as it emerges.
Arm MCP Server
Official Arm MCP server for code migration, optimization, and Arm architecture guidance
How to run each
bns-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Arm MCP Server As a local MCP server: Docker image
claude mcp add --transport stdio arm-mcp -- docker run -i --rm run --rm -i -v "<YOUR_WORKSPACE_PATH>:/workspace" -v "<YOUR_SSH_PRIVATE_KEY_PATH>:/run/keys/ssh-key.pem:ro" -v "<YOUR_SSH_KNOWN_HOSTS_PATH>:/run/keys/known_hosts:ro" docker.io/armlimited/arm-mcp:2.4.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of bns-dev publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: bns-dev · What it can do: Arm MCP Server · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.