# UniFi (oci · ghcr.io/wyre-ai/unifi-mcp)

MCP server for Ubiquiti UniFi's Cloud Site Manager API.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/wyre-ai/unifi-mcp`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/unifi-mcp`
- Version: `v1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 859 tokens (~95/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the UniFi MCP server?

UniFi runs locally as a container image, launched with docker run --rm -i -e UNIFI_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/unifi-mcp:v1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-unifi-mcp -- docker run --rm -i -e UNIFI_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/unifi-mcp:v1.0.1
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-unifi-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-unifi-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-unifi-mcp -- docker run --rm -i -e UNIFI_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/unifi-mcp:v1.0.1
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-unifi-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-unifi-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "UNIFI_API_KEY", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"]
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-unifi-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-unifi-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UNIFI_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/unifi-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads UNIFI_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 38)

First indexed and scored.

## MCP tools (9)

### `unifi_list_sites` (~109 tokens)

List every UniFi site (from hosts running the UniFi Network application) visible to this API key's UI.com account. Each entry includes the site and host IDs, site metadata (name, timezone, gateway MAC), aggregate statistics (device/client counts, network performance), and the caller's permission level on that site.

Input parameters:

- `nextToken` (string): Pagination token from a previous response, to fetch the next page.
- `pageSize` (number): Number of items to return per page.

### `unifi_list_hosts` (~85 tokens)

List every host (UniFi console or network-server application) associated with this API key's UI.com account. Includes hardware ID, current IP address, ownership/block status, and registration/backup timestamps.

Input parameters:

- `nextToken` (string): Pagination token from a previous response, to fetch the next page.
- `pageSize` (number): Number of items to return per page.

### `unifi_get_host` (~37 tokens)

Get detailed information about a single host by ID (as returned by unifi_list_hosts).

Input parameters:

- `id` (string, required): Host ID.

### `unifi_list_devices` (~142 tokens)

List UniFi devices managed by hosts this API key's account owns or super-admins, grouped by host. Each device includes its MAC address, IP address, model, firmware status, and adoption/uptime info. PII-bearing (device MAC/hostname/IP) - admin-gated.

Input parameters:

- `hostIds` (array): Restrict results to devices managed by these host IDs.
- `nextToken` (string): Pagination token from a previous response, to fetch the next page.
- `pageSize` (number): Number of items to return per page.
- `time` (string): Only return devices last processed at or after this RFC3339 timestamp.

### `unifi_get_isp_metrics` (~184 tokens)

Get WAN/ISP health and traffic metrics for every site linked to this API key's account, at 5-minute or 1-hour granularity. 5-minute data is retained at least 24h; 1-hour data at least 30 days. Provide either `duration` alone, or `beginTimestamp`/`endTimestamp` (not both).

Input parameters:

- `beginTimestamp` (string): Earliest timestamp to retrieve, RFC3339. Cannot be combined with duration.
- `duration` (string): Time range ending now. '24h' for 5m metrics; '7d' or '30d' for 1h metrics. Cannot be combined with beginTimestamp/endTimestamp.
- `endTimestamp` (string): Latest timestamp to retrieve, RFC3339. Cannot be combined with duration.
- `type` (string, required): Metric interval.

### `unifi_query_isp_metrics` (~105 tokens)

Get WAN/ISP health and traffic metrics for specific host/site pairs and time ranges. A filtered read, not a mutation, despite being a POST on UniFi's API. If the API key lacks access to a requested site, the response reports status:partialSuccess for a mixed result or fails outright if none are accessible.

Input parameters:

- `sites` (array, required): Host/site pairs to query, each with an optional time range.
- `type` (string, required): Metric interval.

### `unifi_list_sdwan_configs` (~33 tokens)

List every SD-WAN configuration associated with this API key's account (id, name, type only).

### `unifi_get_sdwan_config` (~83 tokens)

Get the full topology for one SD-WAN configuration: variant, advanced settings, and every hub/spoke including their site/host IDs, attached network IDs, and routed subnets (CIDR). Network-topology data - admin-gated.

Input parameters:

- `id` (string, required): SD-WAN config ID (as returned by unifi_list_sdwan_configs).

### `unifi_get_sdwan_config_status` (~81 tokens)

Get deployment status for one SD-WAN configuration: generation/apply status, and per-hub/spoke details including WAN IPs, latency, routes, and any errors or warnings. Network-topology data - admin-gated.

Input parameters:

- `id` (string, required): SD-WAN config ID (as returned by unifi_list_sdwan_configs).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp#diagnostics

## Score history

- 2026-11-05: 39
- 2026-11-04: 39
- 2026-11-03: 38

## Common questions

### What is the UniFi MCP server?

UniFi is an MCP server listed in the public MCP registry as io.github.WYRE-AI/unifi-mcp. MCP server for Ubiquiti UniFi's Cloud Site Manager API. This page covers its container image (ghcr.io/wyre-ai/unifi-mcp).

### Is the UniFi MCP server safe to use?

UniFi scores 39 out of 100 on VerifyMCP. 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 UniFi MCP server expose?

UniFi exposes 9 tools: unifi_list_sites, unifi_list_hosts, unifi_get_host, unifi_list_devices, unifi_get_isp_metrics, and 4 more. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.

### Is the UniFi MCP server still maintained?

UniFi 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 UniFi MCP server under?

UniFi declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/unifi-mcp
- Repository: https://github.com/WYRE-AI/unifi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-unifi-mcp/ghcr-io-wyre-ai-unifi-mcp