Arm MCP Server vs Altos
Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Altos is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.4.0 Forks (GitHub): 22 Stars (GitHub): 95 Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:ea7c4d1daeb9 Forks (GitHub): 22 Stars (GitHub): 95 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 | Altos |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 95 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 22 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (docker.io/armlimited/arm-mcp:2.4.0) | Remote server (gateway.pipeworx.io/altos/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/arm/mcp | github.com/pipeworx-io/mcp-altos |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
Altos
Altos Research MCP — Real estate market intelligence
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.0
Altos As a remote MCP server
claude mcp add --transport http altos https://gateway.pipeworx.io/altos/mcp
Requires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Altos has a remote endpoint we check. How we check endpoints
Tools each declares
Only Arm MCP Server has
apx_recipe_runcheck_imageknowledge_base_searchmcamigrate_ease_scanskopeosysreport_instructions
Only Altos has
ai_visibility_checkaltos_active_listingsaltos_inventory_trendaltos_list_filesaltos_market_statsaltos_new_listingsaltos_pending_salesarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_grounded
Show the remaining 36
bet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Altos as of 2026-10-24). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Arm MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Arm MCP Server · What it can do: Altos · 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.