# Unitrends Backup (oci · ghcr.io/wyre-ai/unitrends-mcp:v1.1.4)

MCP server for Unitrends Backup — appliances, jobs, recovery points, restores, alerts.

- Trust score: 54/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/wyre-ai/unitrends-mcp:v1.1.4`: 54/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-unitrends-mcp/ghcr-io-wyre-ai-unitrends-mcp-v1-1-4.md), [page](https://verifymcp.io/servers/wyre-ai-unitrends-mcp/ghcr-io-wyre-ai-unitrends-mcp-v1-1-4)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/unitrends-mcp:v1.1.4`
- 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-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 540 tokens (~45/item across 12 items; 11 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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.
  - Supports UI / widget rendering.

**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 Unitrends Backup MCP server?

Unitrends Backup runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/unitrends-mcp:v1.1.4. 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-unitrends-mcp -- docker run --rm -i ghcr.io/wyre-ai/unitrends-mcp:v1.1.4
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-unitrends-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-unitrends-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-unitrends-mcp -- docker run --rm -i ghcr.io/wyre-ai/unitrends-mcp:v1.1.4
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-unitrends-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-unitrends-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-unitrends-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-unitrends-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/unitrends-mcp:v1.1.4"
      ]
    }
  }
}
```

## 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-09-20 (score 54, +1)

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

### 2026-09-18 (score 53, +1)

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

### 2026-09-16 (score 52, +1)

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

### 2026-09-14 (score 51, +1)

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

### 2026-09-12 (score 50, +1)

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

### 2026-09-09 (score 49, +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-09-07 (score 48, +1)

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

### 2026-09-05 (score 47, +1)

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

## MCP tools (11)

### `unitrends_list_appliances` (~43 tokens)

List Unitrends appliances visible to the connected MSP Console. Only returns data when pointed at the MSP Console; single-appliance deployments return an empty list.

### `unitrends_get_appliance` (~55 tokens)

Get details for a single Unitrends appliance by its identifier. Only returns data when pointed at the MSP Console; single-appliance deployments do not expose this endpoint.

Input parameters:

- `applianceId` (string, required): Appliance identifier

### `unitrends_list_assets` (~66 tokens)

List protected assets (machines / agents) on a Unitrends appliance. If applianceId is omitted and an MSP Console is in use, the user will be prompted to pick one.

Input parameters:

- `applianceId` (string): Appliance identifier (optional — will elicit if omitted)

### `unitrends_get_asset` (~39 tokens)

Fetch details for a single protected asset.

Input parameters:

- `applianceId` (string, required): Appliance identifier
- `assetId` (string, required): Asset identifier

### `unitrends_list_running_jobs` (~20 tokens)

List currently running and queued backup jobs.

### `unitrends_list_job_history` (~63 tokens)

List historical backup jobs. If date range is omitted, the user will be prompted to choose a window.

Input parameters:

- `since` (string): ISO 8601 start datetime (optional)
- `until` (string): ISO 8601 end datetime (optional)

### `unitrends_list_recovery_points` (~35 tokens)

List recovery points (backups) available for an asset.

Input parameters:

- `assetId` (string, required): Asset identifier

### `unitrends_queue_restore` (~80 tokens)

Queue a restore from a recovery point. DESTRUCTIVE: writes data back into the target asset. Requires explicit confirmation.

Input parameters:

- `recoveryPointId` (string, required): Recovery point identifier to restore from
- `targetAssetId` (string): Target asset identifier (defaults to source if omitted)
- `targetPath` (string): Optional restore destination path

### `unitrends_get_restore_status` (~33 tokens)

Check the status / progress of a queued restore.

Input parameters:

- `restoreId` (string, required): Restore job identifier

### `unitrends_list_alerts` (~21 tokens)

List open alarms / alerts on the appliance.

### `unitrends_get_success_rate` (~64 tokens)

Get RPO compliance / backup success-rate report. If date range is omitted, the user will be prompted.

Input parameters:

- `since` (string): ISO 8601 start datetime (optional)
- `until` (string): ISO 8601 end datetime (optional)

## Diagnostics

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

## Score history

- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 51
- 2026-09-13: 50
- 2026-09-12: 50
- 2026-09-11: 49
- 2026-09-10: 49
- 2026-09-09: 49
- 2026-09-08: 48
- 2026-09-07: 48
- 2026-09-06: 47
- 2026-09-05: 47
- 2026-09-04: 46
- 2026-09-03: 46
- 2026-09-02: 45
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42
- 2026-08-27: 42
- 2026-08-26: 42

## Common questions

### What is the Unitrends Backup MCP server?

Unitrends Backup is an MCP server listed in the public MCP registry as io.github.WYRE-AI/unitrends-mcp. MCP server for Unitrends Backup, appliances, jobs, recovery points, restores, alerts. This page covers its container image (ghcr.io/wyre-ai/unitrends-mcp:v1.1.4).

### Is the Unitrends Backup MCP server safe to use?

Unitrends Backup scores 54 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 Unitrends Backup MCP server expose?

Unitrends Backup exposes 11 tools: unitrends_list_appliances, unitrends_get_appliance, unitrends_list_assets, unitrends_get_asset, unitrends_list_running_jobs, and 6 more. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

### Is the Unitrends Backup MCP server still maintained?

Unitrends Backup is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Unitrends Backup MCP server under?

Unitrends Backup declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/WYRE-AI/unitrends-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-unitrends-mcp/ghcr-io-wyre-ai-unitrends-mcp-v1-1-4.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-unitrends-mcp/ghcr-io-wyre-ai-unitrends-mcp-v1-1-4.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-unitrends-mcp/ghcr-io-wyre-ai-unitrends-mcp-v1-1-4