Arr (aplaceforallmystuff) MCP Server

mcp-arr-server npm v1.7.3

Published by aplaceforallmystuff — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for *arr media management suite - Sonarr, Radarr, Lidarr, Prowlarr

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • fetchingests untrusted input
  • lidarr_get_queueingests untrusted input
  • lidarr_search_albumingests untrusted input
  • radarr_delete_queue_itemingests untrusted input
  • radarr_get_moviesingests untrusted input
  • radarr_get_queueingests untrusted input
  • radarr_search_movieingests untrusted input
  • sonarr_get_queueingests untrusted input
  • sonarr_get_seriesingests untrusted input
  • arr_search_allno sensitive capability
Show 34 more tools ↓
  • lidarr_add_artistno sensitive capability
  • lidarr_get_albumsno sensitive capability
  • lidarr_get_artistsno sensitive capability
  • lidarr_get_calendarno sensitive capability
  • lidarr_get_metadata_profilesno sensitive capability
  • lidarr_get_quality_profilesno sensitive capability
  • lidarr_get_root_foldersno sensitive capability
  • lidarr_searchno sensitive capability
  • lidarr_search_missingno sensitive capability
  • prowlarr_get_indexersno sensitive capability
  • prowlarr_get_statsno sensitive capability
  • prowlarr_searchno sensitive capability
  • prowlarr_test_indexersno sensitive capability
  • radarr_add_movieno sensitive capability
  • radarr_get_calendarno sensitive capability
  • radarr_refresh_movieno sensitive capability
  • radarr_searchno sensitive capability
  • radarr_search_moviesno sensitive capability
  • radarr_update_movieno sensitive capability
  • searchno sensitive capability
  • sonarr_add_seriesno sensitive capability
  • sonarr_get_calendarno sensitive capability
  • sonarr_get_episodesno sensitive capability
  • sonarr_refresh_seriesno sensitive capability
  • sonarr_searchno sensitive capability
  • sonarr_search_episodeno sensitive capability
  • sonarr_search_missingno sensitive capability
  • trash_compare_namingno sensitive capability
  • trash_compare_profileno sensitive capability
  • trash_get_namingno sensitive capability
  • trash_get_profileno sensitive capability
  • trash_get_quality_sizesno sensitive capability
  • trash_list_custom_formatsno sensitive capability
  • trash_list_profilesno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.7.3 latest A 96/100 0 1.13.0 2026-09-07
v1.6.5 A 96/100 0 1.12.1 2026-07-29

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-arr-server/badge.svg)](https://mcptrustchecker.com/registry/mcp-arr-server)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-arr-server"><img src="https://mcptrustchecker.com/registry/mcp-arr-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-arr-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-arr-server --online

Use the free API → How scoring works

Other implementations of Arr 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Analytics & Monitoring