Frigate Auth
PYPI · FRIGATE-AUTH-MCP
MCP server with authentication for Frigate NVR (authenticated port, viewer role)
Available components
Last scanned (10 hours ago)
Scores higher than 80% of PyPI servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to adel-s/frigate-auth-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 436 tokens (~62/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (29% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Schema quality: 50 → 62 ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Schema quality: fair → good functional
- Package version: 0.1.1 → 0.3.0 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/frigate-auth-mcp@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | adel-s/frigate-auth-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/adel-s/frigate-auth-mcp/.github/workflows/publish.yml@refs/tags/v0.3.0 |
| Rekor log index | 3654966309 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:2594540828f7f4ee3d3f2276635f33e805b90a1060d529d9149a400a95ed65a0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
event_snapshot ~83
Snapshot of an event with its bounding box; crop=True zooms on the object. Keep the default height/quality; raise them only when the user needs a detail that is too small to see. The server may cap both.
| Name | Type | Req | Description |
|---|---|---|---|
| crop | boolean | – | – |
| event_id | string | yes | – |
| height | integer | – | – |
| quality | integer | – | – |
No output schema declared.
No examples provided.
frigate_status ~29
Frigate version, uptime, the cameras this user may see and per-camera fps / detection fps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_event ~31
One event in detail, including the GenAI description when there is one.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
latest_frame ~66
The current frame of a camera. Keep the default height/quality; raise them only when the user needs a detail that is too small to see. The server may cap both.
| Name | Type | Req | Description |
|---|---|---|---|
| camera | string | yes | – |
| height | integer | – | – |
| quality | integer | – | – |
No output schema declared.
No examples provided.
list_events ~85
Tracked-object events, newest first. after/before: ISO 8601 or unix seconds. label e.g. person, cat, squirrel. has_description=True keeps only events with a GenAI description.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| before | – | – | – |
| camera | – | – | – |
| has_description | boolean | – | – |
| label | – | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_reviews ~91
Review items (what the Frigate UI shows), newest first. severity: alert or detection. after/before: ISO 8601 or unix seconds; after defaults to 7 days ago (Frigate itself returns only the last 24 hours when it is not set).
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| before | – | – | – |
| camera | – | – | – |
| limit | integer | – | – |
| severity | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
review_summary ~51
Counts of alerts and detections for the last 24 hours and per day for the last `days` days (reviewed / not reviewed), as in the Frigate UI.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Frigate Auth MCP server?
Frigate Auth runs locally as a PyPI package, launched with uvx frigate-auth-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · frigate-auth-mcp
claude mcp add adel-s-frigate-auth-mcp -- uvx frigate-auth-mcp
What is the Frigate Auth MCP server?
Frigate Auth is an MCP server listed in the public MCP registry as io.github.adel-s/frigate-auth-mcp. MCP server with authentication for Frigate NVR (authenticated port, viewer role). This page covers its PyPI package (frigate-auth-mcp).
Is the Frigate Auth MCP server safe to use?
Frigate Auth scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Frigate Auth MCP server expose?
Frigate Auth exposes 7 tools: frigate_status, list_events, get_event, event_snapshot, latest_frame, and 2 more. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the Frigate Auth MCP server still maintained?
Frigate Auth is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Frigate Auth MCP server under?
Frigate Auth declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.