Ext Ops Panel
Open dashboard
Comparison

Arm MCP Server vs American Samoa Code

Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). American Samoa Code 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-26. 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

Where each is published
MarketplaceArm MCP ServerAmerican Samoa Code
Official MCP Registry Listed
Version: 2.4.0
Forks (GitHub): 22
Stars (GitHub): 95
Not marked · First seen 		Listed
Version: 0.1.3
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

Arm MCP Server vs American Samoa Code
FactArm MCP ServerAmerican Samoa Code
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 published2026-10-22
Where it runs (differs)On your machine (docker.io/armlimited/arm-mcp:2.4.0)Remote server (gateway.pipeworx.io/american-samoa-code/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/arm/mcpgithub.com/pipeworx-io/mcp-american-samoa-code
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

In its own words, on Official MCP Registry:

Official Arm MCP server for code migration, optimization, and Arm architecture guidance

American Samoa Code

In its own words, on Official MCP Registry:

American Samoa Code Annotated (A.S.C.A.) — section lookup by citation and topic/keyword search…

How to run each

Arm MCP Server As a local MCP server: Docker image

Claude Code
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

American Samoa Code As a remote MCP server

Claude Code
claude mcp add --transport http american-samoa-code https://gateway.pipeworx.io/american-samoa-code/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only American Samoa Code has a remote endpoint we check. How we check endpoints

Tools each declares

Only Arm MCP Server has

  • apx_recipe_run
  • check_image
  • knowledge_base_search
  • mca
  • migrate_ease_scan
  • skopeo
  • sysreport_instructions

Only American Samoa Code has

  • ai_visibility_check
  • archive_compare
  • archive_evidence
  • as_search
  • as_statute
  • as_titles
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
Show the remaining 33
  • company_register_search
  • compare_entities
  • deep_research
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • kalshi_weather_edge
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • prediction_calibration
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (American Samoa Code as of 2026-10-25). More tools is not better in itself: compare what each needs for the job.

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: American Samoa Code · 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.

Where the data comes from: how the catalog is built