Seerr server manager

PassAudited by ClawScan on May 10, 2026.

Overview

This appears to be a legitimate Seerr management CLI, but it requires a powerful Seerr API key and its optional MCP HTTP modes need careful authentication setup.

Before installing, verify the upstream release or container image, use the least-privilege Seerr API key available, and be careful with MCP HTTP mode. For remote MCP access, prefer HTTPS and bearer-token authentication; avoid no-auth mode or query-string API keys unless the endpoint is isolated and trusted.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If used with an administrative API key, mistakes or unintended commands could change users, requests, issues, or server settings.

Why it was flagged

The CLI is intended to perform mutable and administrative actions on a Seerr server. This matches the skill purpose, but users should recognize that the agent may be able to change requests, users, or server state when given the API key.

Skill content
create and manage media requests, manage users, track issues, and administer a self-hosted Seerr instance
Recommendation

Use a least-privilege Seerr API key where possible and require explicit confirmation before user-management, deletion, or administrative changes.

What this means

Anyone or any process with access to this key can act against the configured Seerr server within that key's permissions.

Why it was flagged

The skill requires a Seerr API key as its primary credential. This is expected for the integration, but it grants delegated account/server access.

Skill content
primary_credential: SEERR_API_KEY ... API key for authenticating with the Seerr server
Recommendation

Store the API key securely, avoid sharing it in chat or logs, rotate it if exposed, and prefer a scoped or non-admin key if the Seerr deployment supports that.

What this means

The security of the installed tool depends on the external release or container image you download.

Why it was flagged

Installation depends on an external latest-release binary or container image, while the provided skill package contains only SKILL.md and no reviewable executable code.

Skill content
Download the latest release archive from https://github.com/electather/seerr-cli/releases/latest ... A Docker image is also available at ghcr.io/electather/seerr-cli
Recommendation

Install only from the expected repository, verify checksums and release provenance, consider pinning a specific version instead of latest, and review the upstream project before providing credentials.

What this means

A poorly secured MCP HTTP endpoint could let other clients invoke Seerr-management tools or expose the API key through URLs, logs, browser history, or intermediaries.

Why it was flagged

The optional MCP HTTP transport can be configured with no authentication, an API key in the URL query string, and CORS for browser clients. These options are disclosed and not the default stdio transport, but they can expose Seerr control if used on an untrusted network.

Skill content
Set to "true" to disable all MCP HTTP authentication ... append ?api_key=<key> to authenticate ... Set to "true" to enable CORS headers
Recommendation

Prefer bearer-token authentication over query-string API keys, use HTTPS, avoid SEERR_MCP_NO_AUTH except on isolated localhost/trusted networks, and do not expose the MCP port publicly without access controls.