# Acronis Cyber Protect Cloud (oci · ghcr.io/wyre-ai/acronis-mcp)

Acronis Cyber Protect Cloud MCP: alerts, policies, resources, agents, tenants and EDR incidents.

- Trust score: 41/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/acronis-mcp`
- Version: `v1.0.3`
- 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-21.

- **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 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1214 tokens (~35/item across 34 items; 34 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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 34 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 Acronis Cyber Protect Cloud MCP server?

Acronis Cyber Protect Cloud runs locally as a container image, launched with docker run --rm -i -e ACRONIS_BASE_URL -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET -e ACRONIS_ENABLE_WRITES -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/acronis-mcp:v1.0.3. 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-acronis-mcp -- docker run --rm -i -e ACRONIS_BASE_URL -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET -e ACRONIS_ENABLE_WRITES -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/acronis-mcp:v1.0.3
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACRONIS_BASE_URL",
        "-e",
        "ACRONIS_CLIENT_ID",
        "-e",
        "ACRONIS_CLIENT_SECRET",
        "-e",
        "ACRONIS_ENABLE_WRITES",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/acronis-mcp:v1.0.3"
      ]
    }
  }
}
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACRONIS_BASE_URL",
        "-e",
        "ACRONIS_CLIENT_ID",
        "-e",
        "ACRONIS_CLIENT_SECRET",
        "-e",
        "ACRONIS_ENABLE_WRITES",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/acronis-mcp:v1.0.3"
      ]
    }
  }
}
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp -- docker run --rm -i -e ACRONIS_BASE_URL -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET -e ACRONIS_ENABLE_WRITES -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/acronis-mcp:v1.0.3
```

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

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "ACRONIS_BASE_URL", "-e", "ACRONIS_CLIENT_ID", "-e", "ACRONIS_CLIENT_SECRET", "-e", "ACRONIS_ENABLE_WRITES", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/acronis-mcp:v1.0.3"]
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACRONIS_BASE_URL",
        "-e",
        "ACRONIS_CLIENT_ID",
        "-e",
        "ACRONIS_CLIENT_SECRET",
        "-e",
        "ACRONIS_ENABLE_WRITES",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/acronis-mcp:v1.0.3"
      ]
    }
  }
}
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-acronis-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACRONIS_BASE_URL",
        "-e",
        "ACRONIS_CLIENT_ID",
        "-e",
        "ACRONIS_CLIENT_SECRET",
        "-e",
        "ACRONIS_ENABLE_WRITES",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/acronis-mcp:v1.0.3"
      ]
    }
  }
}
```

This image reads ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET, ACRONIS_ENABLE_WRITES, 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-20 (score 41, +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-11-18 (score 40, +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-11-16 (score 39, +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.

### 2026-11-14 (score 38, +1)

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

### 2026-11-11 (score 37, +1)

- [functional] Package version: v1.0.2 → v1.0.3

### 2026-11-10 (score 36, 0)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: v1.0.1 → v1.0.2

### 2026-11-09 (score 36, +1)

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

### 2026-11-07 (score 35, +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.

## MCP tools (34)

### `acronis_fetch_tenant` (~37 tokens)

Fetches a tenant by ID.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_tenants_batch` (~48 tokens)

Gets several tenants at once, by up to 100 tenant IDs, by parent tenant, or as a tenant and everything under it.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_tenant_children` (~49 tokens)

Lists the IDs of the tenants directly under a tenant, such as a partner's customers.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_tenant_users` (~44 tokens)

Fetches a list of UUIDs of the tenant's users.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_users_batch` (~28 tokens)

Gets details for several users at once.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_user` (~36 tokens)

Fetches a user by ID.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_current_user_info` (~21 tokens)

Fetches information about the currently authenticated user.

### `acronis_search` (~24 tokens)

Searches for tenants and users.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_tenant_mfa_status` (~39 tokens)

Provides MFA status for tenant and progress of TOTP enablement by users.

Input parameters:

- `path` (object, required): URI path parameters

### `acronis_fetch_tenant_usages` (~44 tokens)

Fetches a list of common usage metrics of the tenant.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_all_alerts` (~30 tokens)

Fetches all alerts by optional filtering parameters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_alert` (~39 tokens)

Fetches the information about the alert by ID.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_categories` (~28 tokens)

Lists the alert categories that are turned on.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_alert_counters` (~34 tokens)

Fetches the alert counters that may be grouped by optional parameters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_alerts_grouped_by_scope` (~44 tokens)

Gets the most recent of the most severe alerts for each group, grouped by the scope you choose.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_all_alert_types` (~28 tokens)

Fetches all registered alert types.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_resources_with_top_severity_alerts` (~44 tokens)

Fetches the resources' statuses that contain the alerts with the highest severity found for the resources.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_alert_counts_per_customer` (~30 tokens)

Fetches count of alerts per customer.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_alerts_grouped_per_customer` (~32 tokens)

Fetches alerts of the specified customers.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_active_alert_count` (~22 tokens)

Returns count of active alerts and last modification time.

### `acronis_fetch_policies` (~34 tokens)

Lists protection policies (called protection plans in the Acronis console).

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_policy` (~39 tokens)

Gets one protection policy and its settings by ID.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_policy_applications` (~38 tokens)

Lists where policies are applied, meaning which resources each policy covers, with optional filters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_applications_issue_statistics` (~32 tokens)

Counts problems with applied policies, grouped by issue.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_application_statuses_by_policy` (~36 tokens)

Gets the status of every resource a given policy is applied to.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_resources` (~34 tokens)

Lists resources (machines, mailboxes and other workloads), with optional filters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_resource_count` (~31 tokens)

Fetch a count of all resources that match filter parameters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_resource` (~44 tokens)

Gets one resource (a machine, mailbox or other workload) by ID.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_resource_protection_status` (~31 tokens)

Shows which resources are protected and which aren't.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_agents` (~32 tokens)

Lists the Acronis agents installed on machines in a tenant.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_agent` (~29 tokens)

Gets one Acronis agent by ID.

Input parameters:

- `path` (object, required): URI path parameters

### `acronis_fetch_incidents` (~30 tokens)

Lists EDR security incidents, with optional filters.

Input parameters:

- `query` (object): Query parameters

### `acronis_fetch_incident` (~51 tokens)

Gets the details of one EDR security incident by ID.

Input parameters:

- `headers` (object): Request headers
- `path` (object, required): URI path parameters
- `query` (object): Query parameters

### `acronis_fetch_response_action_status` (~52 tokens)

Gets the status of a response action that was started on an incident, such as isolating a machine.

Input parameters:

- `path` (object, required): URI path parameters
- `query` (object): Query parameters

## Diagnostics

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

## Score history

- 2026-11-21: 41
- 2026-11-20: 41
- 2026-11-19: 40
- 2026-11-18: 40
- 2026-11-17: 39
- 2026-11-16: 39
- 2026-11-15: 38
- 2026-11-14: 38
- 2026-11-13: 37
- 2026-11-12: 37
- 2026-11-11: 37
- 2026-11-10: 36
- 2026-11-09: 36
- 2026-11-08: 35
- 2026-11-07: 35
- 2026-11-06: 34

## Common questions

### What is the Acronis Cyber Protect Cloud MCP server?

Acronis Cyber Protect Cloud is an MCP server listed in the public MCP registry as io.github.WYRE-AI/acronis-mcp. Acronis Cyber Protect Cloud MCP: alerts, policies, resources, agents, tenants and EDR incidents. This page covers its container image (ghcr.io/wyre-ai/acronis-mcp).

### Is the Acronis Cyber Protect Cloud MCP server safe to use?

Acronis Cyber Protect Cloud scores 41 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 Acronis Cyber Protect Cloud MCP server expose?

Acronis Cyber Protect Cloud exposes 34 tools: acronis_fetch_tenant, acronis_fetch_tenants_batch, acronis_fetch_tenant_children, acronis_fetch_tenant_users, acronis_fetch_users_batch, and 29 more. Their descriptions and schemas cost roughly 1,214 tokens of context every time the server is loaded.

### Is the Acronis Cyber Protect Cloud MCP server still maintained?

Acronis Cyber Protect Cloud is still listed as active in the MCP registry. We last reached this channel on 21 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 Acronis Cyber Protect Cloud MCP server under?

Acronis Cyber Protect Cloud 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.

### What did VerifyMCP test on the Acronis Cyber Protect Cloud MCP server?

VerifyMCP ran 12 checks on Acronis Cyber Protect Cloud, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Acronis Cyber Protect Cloud: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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