Arr MCP

One MCP server for the whole self-hosted media stack: Radarr, Sonarr, Prowlarr, Bazarr, Jellyfin, Plex, Seerr, SABnzbd,

MCP Servers TypeScript Grade C Listed MIT
60.9/100
Rank #433 of 1320
Compare Arr MCP

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +4

Is Arr MCP safe? Arr MCP scores 60.9/100 (Grade C), ranked #433 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 100% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 18 spots (#408 → #426)
2026-09-02
Rank Moved
Rank dropped 11 spots (#397 → #408)
2026-09-01
Rank Moved
Rank dropped 11 spots (#386 → #397)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
58.8
Activity sub-score · out of 100
#204

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:02 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
16
Forks
1
Last Push
2026-09-04
today
Commits (4 wk)
149
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▼7
was #426

Analysis

HVTrust Dimensions vs MCP Servers

60.9 / 100 · 100.0% confidence

Arr MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
2.3 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.4 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.0 / 20
3.3 below avg 6.3

Activity Inputs

58.8 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Aug 30, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 10
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 9

Is Arr MCP safe?

Arr MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Arr MCP publish package provenance?
No published build provenance is currently detected for Arr MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Arr MCP have an OpenSSF Scorecard?
Arr MCP has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Arr MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Arr MCP use?
Arr MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Arr MCP's commits signed?
100% of the last 100 commits to Arr MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 →

MCP Server Support
high confidence
Implemented
Arr MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Arr MCP?

For maintainers

HVTrust scores Arr MCP 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
Rank 7Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-03
Rank Moved
Rank dropped 18 spots (#408 → #426)
2026-09-02
Rank Moved
Rank dropped 11 spots (#397 → #408)
2026-09-01
Rank Moved
Rank dropped 11 spots (#386 → #397)
2026-08-31
Rank Moved
Rank dropped 20 spots (#366 → #386)
2026-08-29
Rank Moved
Rank dropped 11 spots (#360 → #371)
2026-08-27
Rank Moved
Rank dropped 10 spots (#348 → #358)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.5/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 485 spots (#833 → #348)
2026-08-26
HVTrust Changed
HVTrust up 35.1pts (25.6 → 60.7)
2026-08-16
Newly Listed
First tracked at rank #836

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/arr-mcp.svg)](https://hvtracker.net/agents/arr-mcp)
HTML:
<a href="https://hvtracker.net/agents/arr-mcp"><img src="https://hvtracker.net/badge/arr-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON