# UISP (oci · ghcr.io/wyre-ai/uisp-mcp)

MCP server for Ubiquiti UISP's REST API - network/ISP infrastructure monitoring for MSPs.

- Trust score: 46/100 (low)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/uisp-mcp`
- Version: `v1.0.0`
- 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-10-18.

- **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 15 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 1841 tokens (~68/item across 27 items; 27 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 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 UISP MCP server?

UISP runs locally as a container image, launched with docker run --rm -i -e UISP_API_KEY -e UISP_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/uisp-mcp:v1.0.0. 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-uisp-mcp -- docker run --rm -i -e UISP_API_KEY -e UISP_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/uisp-mcp:v1.0.0
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UISP_API_KEY",
        "-e",
        "UISP_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UISP_API_KEY",
        "-e",
        "UISP_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp -- docker run --rm -i -e UISP_API_KEY -e UISP_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/uisp-mcp:v1.0.0
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "UISP_API_KEY",
        "-e",
        "UISP_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "UISP_API_KEY", "-e", "UISP_BASE_URL", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"]
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UISP_API_KEY",
        "-e",
        "UISP_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-uisp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "UISP_API_KEY",
        "-e",
        "UISP_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/uisp-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads UISP_API_KEY, UISP_BASE_URL, 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-10-18 (score 46, +1)

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

### 2026-10-16 (score 45, +1)

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

### 2026-10-14 (score 44, +6)

- [functional improvement] Stability: unverified → 0.40

### 2026-10-06 (score 38, 0)

- [security regression] Provenance: unverified → fail

### 2026-10-04 (score 38, 0)

- [security regression] Provenance: fail → unverified

### 2026-10-02 (score 38)

First indexed and scored.

## MCP tools (27)

### `uisp_list_sites` (~160 tokens)

List sites (network locations - sites, endpoints, and clients - each optionally tied to a UCRM client/service record). Each site's `id` chains into uisp_get_site, uisp_list_site_clients, uisp_list_devices (siteId filter), and uisp_get_site_statistics.

Input parameters:

- `deviceId` (string): Filter to the site containing this device ID.
- `id` (array): Filter to specific site IDs.
- `ip` (string): Filter to the site whose endpoint has this IP address.
- `type` (string): Filter by site type.
- `ucrm` (boolean): Only return sites linked to a UCRM client/service record.
- `ucrmDetails` (boolean): Include the linked UCRM client/service detail.

### `uisp_get_site` (~62 tokens)

Get a single site's detail, including its status and (if linked) UCRM client/service reference.

Input parameters:

- `id` (string, required): Site ID (from uisp_list_sites).
- `ucrmDetails` (boolean): Include the linked UCRM client/service detail.

### `uisp_search_sites` (~126 tokens)

Search sites, endpoints, and clients by name, address, MAC address, or IP address.

Input parameters:

- `count` (number, required): Number of results per page.
- `latitude` (number): Latitude to bias/scope the search geographically.
- `longitude` (number): Longitude to bias/scope the search geographically.
- `page` (number, required): Page number (1-indexed).
- `query` (string): Search text.
- `type` (string): Restrict results to this site type.
- `ucrm` (boolean): Only return results linked to a UCRM client/service record.

### `uisp_list_site_clients` (~40 tokens)

List all client sites belonging to a given (parent) site.

Input parameters:

- `id` (string, required): Parent site ID (from uisp_list_sites).

### `uisp_get_site_statistics` (~57 tokens)

Get upload/download traffic between a site and its parent site, bucketed by interval.

Input parameters:

- `interval` (string, required): Time bucket for the traffic figures.
- `siteId` (string, required): Site ID (from uisp_list_sites).

### `uisp_get_site_traffic_summary` (~56 tokens)

Get a site's total upload/download for the given interval up to now.

Input parameters:

- `interval` (string, required): Time bucket for the traffic figures.
- `siteId` (string, required): Site ID (from uisp_list_sites).

### `uisp_list_devices` (~144 tokens)

List devices (hostname/IP/MAC, status, parent site), optionally filtered by site/type/role/authorization. Each device's `id` chains into uisp_get_device, uisp_get_device_detail, uisp_get_device_statistics, and uisp_list_device_interfaces.

Input parameters:

- `authorized` (boolean): Filter to authorized (true) or pending-authorization (false) devices.
- `role` (array): Filter by device role.
- `siteId` (string): Filter to devices at this site (from uisp_list_sites).
- `type` (array): Filter by device type.
- `withInterfaces` (boolean): Include each device's interfaces in the response.

### `uisp_get_device` (~35 tokens)

Get a single device's status overview by ID.

Input parameters:

- `id` (string, required): Device ID (from uisp_list_devices).

### `uisp_get_device_detail` (~57 tokens)

Get a single device's detail, optionally including its interfaces and/or connected stations.

Input parameters:

- `id` (string, required): Device ID (from uisp_list_devices).
- `withStations` (boolean): Include the device's connected wireless stations.

### `uisp_get_device_statistics` (~58 tokens)

Get device telemetry (CPU/RAM/signal/temperature/throughput) bucketed by interval.

Input parameters:

- `id` (string, required): Device ID (from uisp_list_devices).
- `interval` (string, required): Time bucket for the statistics.

### `uisp_list_device_interfaces` (~42 tokens)

List a device's network interfaces, including their configured IP addresses and status.

Input parameters:

- `deviceId` (string, required): Device ID (from uisp_list_devices).

### `uisp_get_device_by_mac` (~50 tokens)

Look up a device by its MAC address.

Input parameters:

- `mac` (string, required): Device MAC address, e.g. 78:8a:20:5f:2a:ff.

### `uisp_list_discovered_devices` (~29 tokens)

List devices UISP has discovered on the network but which have not yet been added.

### `uisp_list_outages` (~144 tokens)

List network outages - UISP's alerting surface - each tied to a site and device. Filter by device, type (outage/unreachable), a text query, or in-progress state.

Input parameters:

- `count` (number, required): Number of results per page.
- `deviceId` (string): Filter to outages for this device ID.
- `inProgress` (boolean): Filter to outages that are still ongoing.
- `page` (number, required): Page number (1-indexed).
- `period` (number): Restrict to outages within the last N days.
- `query` (string): Text search across outage records.
- `type` (string): Filter by outage type.

### `uisp_list_logs` (~167 tokens)

List the UISP event/audit log (e.g. logins, device state changes, backups, upgrades). Log messages can embed device MAC/IP addresses. Filter by site, device, severity level, event tag, or a text query.

Input parameters:

- `count` (number, required): Number of results per page.
- `deviceId` (array): Filter to log items for these device IDs.
- `level` (string): Filter by severity level.
- `page` (number, required): Page number (1-indexed).
- `period` (number): Restrict to log items within the last N days.
- `query` (string): Text search across log messages.
- `siteId` (string): Filter to log items for this site.
- `tag` (string): Filter by event tag/category.

### `uisp_list_data_links` (~59 tokens)

List data links - the wireless/wired links UISP has mapped between devices and sites, with signal/frequency/distance detail.

Input parameters:

- `siteLinksOnly` (boolean): Only return data links between sites (excludes device-to-device links).

### `uisp_get_data_link` (~38 tokens)

Get a single data link's detail by ID.

Input parameters:

- `id` (string, required): Data link ID (from uisp_list_data_links).

### `uisp_list_site_data_links` (~37 tokens)

List data links attached to a given site.

Input parameters:

- `siteId` (string, required): Site ID (from uisp_list_sites).

### `uisp_list_gateways` (~31 tokens)

List gateways - routers configured as network gateways - and their NetFlow/QoS/suspend configuration.

### `uisp_get_gateway` (~35 tokens)

Get a single gateway's detail by ID.

Input parameters:

- `id` (string, required): Gateway ID (from uisp_list_gateways).

### `uisp_list_tasks` (~81 tokens)

List background tasks (e.g. firmware upgrades, backups, mass operations) and their status.

Input parameters:

- `count` (number, required): Number of results per page.
- `page` (number, required): Page number (1-indexed).
- `period` (number): Restrict to tasks within the last N days.
- `status` (string): Filter by task status.

### `uisp_get_tasks_in_progress` (~21 tokens)

Get the number of tasks currently in progress.

### `uisp_list_firmwares` (~26 tokens)

Get the firmware versions available to UISP for its supported device models.

### `uisp_get_speed_tests` (~20 tokens)

Get detail about running and recent speed tests.

### `uisp_get_version` (~31 tokens)

Get the UISP version, deployment type and build info. Useful as a credential/connectivity sanity check.

### `uisp_get_network_statistics` (~77 tokens)

Get network-wide statistics: client/site counts, network health, signal/link/ISP scores, data-link and uplink/downlink utilization, and outage counts.

Input parameters:

- `interval` (string, required): Time bucket for the statistics.
- `siri` (boolean): Include the SIRI (Signal Interference Ratio Index) score. Defaults to false.

### `uisp_get_summary` (~158 tokens)

Get badge-count-like values across the instance: unread logs/outages/firmwares, active/all client and site counts, devices needing authorization, firmware up-to-dateness. Each *Timestamp param scopes that count to items newer than the given epoch-ms timestamp — pass 0 for the instance's current totals.

Input parameters:

- `firmwaresTimestamp` (number): Epoch-ms timestamp; only firmwares newer than this count toward firmwaresUnreadCount.
- `logsLevel` (array, required): Which log severities to count toward logsUnreadCount.
- `logsTimestamp` (number): Epoch-ms timestamp; only logs newer than this count toward logsUnreadCount.
- `outagesTimestamp` (number): Epoch-ms timestamp; only outages newer than this count toward outagesUnreadCount.

## Diagnostics

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

## Score history

- 2026-10-18: 46
- 2026-10-17: 45
- 2026-10-16: 45
- 2026-10-15: 44
- 2026-10-14: 44
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-10: 38
- 2026-10-07: 38
- 2026-10-06: 38
- 2026-10-04: 38
- 2026-10-03: 38
- 2026-10-02: 38

## Common questions

### What is the UISP MCP server?

UISP is an MCP server listed in the public MCP registry as io.github.WYRE-AI/uisp-mcp. MCP server for Ubiquiti UISP's REST API - network/ISP infrastructure monitoring for MSPs. This page covers its container image (ghcr.io/wyre-ai/uisp-mcp).

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

UISP scores 46 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 UISP MCP server expose?

UISP exposes 27 tools: uisp_list_sites, uisp_get_site, uisp_search_sites, uisp_list_site_clients, uisp_get_site_statistics, and 22 more. Their descriptions and schemas cost roughly 1,841 tokens of context every time the server is loaded.

### Is the UISP MCP server still maintained?

UISP is still listed as active in the MCP registry. We last reached this channel on 18 October 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 UISP MCP server under?

UISP 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/uisp-mcp
- Repository: https://github.com/WYRE-AI/uisp-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-uisp-mcp/ghcr-io-wyre-ai-uisp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-uisp-mcp/ghcr-io-wyre-ai-uisp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-uisp-mcp/ghcr-io-wyre-ai-uisp-mcp