mseep-radarr-sonarr-mcp@0.1.2
VERIFIED· not startedPublisher claims: "MCP Server for Radarr and Sonarr media management" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
JELLYFIN_API_KEYPLEX_TOKENRADARR_API_KEYSONARR_API_KEYConfiguration, not credentials: JELLYFIN_BASE_URL, JELLYFIN_USER_ID, MCP_SERVER_PORT, NAS_IP, PLEX_BASE_URL, RADARR_BASE_PATH, RADARR_PORT, SONARR_BASE_PATH, SONARR_PORT- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for JELLYFIN_API_KEY, PLEX_TOKEN, RADARR_API_KEY, SONARR_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 94/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 3 scenarios · 0 deviationsStatic findings
self.base_url = config.get("baseUrl") # e.g., "http://10.0.0.23:32400"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.self.base_url = config.get("baseUrl") # e.g., "http://10.0.0.23:5055"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls."baseUrl": os.environ.get('JELLYFIN_BASE_URL', ''), # e.g., "http://10.0.0.23:5055"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls."baseUrl": os.environ.get('PLEX_BASE_URL', ''), # e.g., "http://10.0.0.23:32400"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mseep-radarr-sonarr-mcp@0.1.2 as of 46 h ago. This is the package itself, not its dependencies.