Arm MCP Server
Arm's MCP server
Is Arm MCP Server safe? Promising trust profile, but some evidence still deserves review.
Compare Arm MCP Server
How does it stack up against its MCP Servers neighbours?
- Screaming Frog SEO Spider MCP Server +0.2 higher
- build123d MCP +0.1 higher
- MCP Memory Service same score
In detail: Arm MCP Server scores 72.8/100 (Grade B), ranked #311 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 9.0/10; 43% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Arm MCP Server could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Sign every commit43% signed today +2.8 → 75.6 B · #150 of 778
Chain of custody
Scanners check what the code says. This traces who ships Arm MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/arm/mcp, Apache-2.0, last pushed 2026-11-09. 43% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 9.0/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection8
- Signed Releases10
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies9
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 8CI-Tests 10CII-Best-Practices 2Code-Review 10Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 9SAST 10Security-Policy 10Signed-Releases 10Token-Permissions 10Vulnerabilities 10 -
Published packages None
Distributed as the container image docker.io/armlimited/arm-mcp:2.4.0; HVTracker doesn't check that registry's source link yet.
Changes to this chain
- 2026-08-19 OSSF Scorecard: 7.4/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Arm MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Arm MCP Server compares in MCP Servers
- #182 Screaming Frog SEO Spider MCP Server 73.0 +0.2
- #183 build123d MCP 72.9 +0.1
- #184 Arm MCP Server 72.8 this agent
- #185 MCP Memory Service 72.8 ±0
- #186 Better Godot MCP 72.6 −0.2
Bars show each HVTrust score; the tick marks Arm MCP Server’s 72.8.
Where the 72.8 comes from
HVTrust dimensions vs the MCP Servers average
72.8 / 100 · 100.0% confidenceArm MCP Server MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
68.3 / 100Common questions about Arm MCP Server
Does Arm MCP Server publish package provenance?
Does Arm MCP Server have an OpenSSF Scorecard?
Is Arm MCP Server actively maintained?
What license does Arm MCP Server use?
Are Arm MCP Server's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Arm MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Arm MCP Server?
For maintainers
HVTrust scores Arm MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/arm-mcp-server)
<a href="https://hvtracker.net/agents/arm-mcp-server"><img src="https://hvtracker.net/badge/arm-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON