updated 2026-11-10 04:07 UTC

UniFi Access MCP

Repository Website

MCP servers & Graph API for the UniFi suite of applications, Network, Protect, and Access

MCP Servers Python Listed MIT

Is UniFi Access MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.1 / 10
Provenance Attested
Signed commits 78%
Last push yesterday
Compare UniFi Access MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: UniFi Access MCP scores 82.1/100 (Grade A), ranked #145 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.1/10; 78% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How UniFi Access MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships UniFi Access MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/sirkirby/unifi-mcp, MIT, last pushed 2026-11-09. 78% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.1/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 5
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 5
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Partly attested

    • PyPI unifi-access-mcp Source link isn't a GitHub repo Build provenance attested

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-27 OSSF Scorecard: 6.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues UniFi Access MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How UniFi Access MCP compares in MCP Servers

  1. #61 Quicken Mac MCP 82.4 +0.3
  2. #62 Api MCP Server 82.2 +0.1
  3. #63 UniFi Access MCP 82.1 this agent
  4. #64 Zotero MCP 82.1 ±0
  5. #65 Gongio MCP 82.0 −0.1

Bars show each HVTrust score; the tick marks UniFi Access MCP’s 82.1.

Where the 82.1 comes from

HVTrust dimensions vs the MCP Servers average

82.1 / 100 · 100.0% confidence

UniFi Access MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.0 / 25
8.2 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.4 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
11.0 / 20
3.4 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-14
Rank Moved
Rank rose 12 spots (#147 → #135)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
78.1
Activity sub-score · out of 100
#63
In MCP Servers

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

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
1.0k
Forks
138
Last Push
2026-11-09
yesterday
Commits (4 wk)
155
Downloads (7d)
645
pypi
HN mentions (30d)
—
Open Issues
9
Rank Change
▼2
was #143

Analysis

Activity Inputs

78.1 / 100
StarsRepository reach
18.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.0 / 20

Common questions about UniFi Access MCP

Public supply-chain signals for UniFi Access MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but UniFi Access MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does UniFi Access MCP publish package provenance?
Yes. UniFi Access MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does UniFi Access MCP have an OpenSSF Scorecard?
UniFi Access MCP has an OpenSSF Scorecard score of 6.1/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 UniFi Access MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does UniFi Access MCP use?
UniFi Access MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are UniFi Access MCP's commits signed?
78% of the last 100 commits to UniFi Access 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
medium confidence
Implemented
UniFi Access MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to UniFi Access MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain UniFi Access MCP?

For maintainers

HVTrust scores UniFi Access 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 9HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1Surface 1
2026-10-14
Rank Moved
Rank rose 12 spots (#147 → #135)
2026-10-03
Rank Moved
Rank dropped 15 spots (#124 → #139)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 473 spots (#594 → #121)
2026-09-23
HVTrust Changed
HVTrust up 48.0pts (34.1 → 82.1)
2026-09-22
Newly Listed
First tracked at rank #594
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Rank Moved
Rank dropped 19 spots (#77 → #96)
2026-08-31
Rank Moved
Rank dropped 12 spots (#68 → #80)
2026-08-27
Scorecard Added
OSSF Scorecard: 6.3/10
2026-08-27
Grade Changed
Trust grade B → A
2026-08-27
Rank Moved
Rank rose 111 spots (#181 → #70)
2026-08-27
HVTrust Changed
HVTrust up 13.3pts (68.8 → 82.1)
2026-08-26
Rank Moved
Rank dropped 16 spots (#165 → #181)
2026-08-22
Rank Moved
Rank rose 21 spots (#183 → #162)
2026-08-19
Rank Moved
Rank dropped 10 spots (#166 → #176)
GitHub → Website → PyPI: unifi-access-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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