Arm MCP Server vs Signal by StackEnhance
Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Signal by StackEnhance is an MCP server published by gimarcus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  Arm MCP Server |  Signal by StackEnhance |
|---|---|---|
| Official MCP Registry | Listed Version: 2.4.0 Forks (GitHub): 22 Stars (GitHub): 94 Not marked · First seen |
Listed, marked deprecated Version: 1.2.1 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:ea7c4d1daeb9 Forks (GitHub): 22 Stars (GitHub): 94 Not marked · First seen |
Not listed |
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 | Arm MCP Server | Signal by StackEnhance |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 94 | No figure on GitHub |
| Forks (GitHub) (differs) | 22 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (docker.io/armlimited/arm-mcp:2.4.0) | Remote server (stackenhance.com/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/arm/mcp | 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 | Responded 39 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
Arm MCP Server
Official Arm MCP server for code migration, optimization, and Arm architecture guidance
Signal by StackEnhance
Moved to com.stackenhance/signal: the same server, now published under the StackEnhance domain.
How to run each
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.0Signal by StackEnhance As a remote MCP server
claude mcp add --transport http signal https://stackenhance.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Signal by StackEnhance has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Signal by StackEnhance 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: Arm MCP Server · What it can do: Signal by StackEnhance · Compare two other plugins
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.