# Datto BCDR (oci · ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5)

MCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5`
- 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**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 598 tokens (~54/item across 11 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Datto BCDR MCP server?

Datto BCDR runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5. 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-datto-bcdr-mcp -- docker run --rm -i ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add wyre-ai-datto-bcdr-mcp -- docker run --rm -i ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5
```

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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-18 (score 54, +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 53, +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 52, +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 51, +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-10 (score 50, +1)

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

### 2026-09-08 (score 49, +1)

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

### 2026-09-06 (score 48, +1)

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

### 2026-09-03 (score 47, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (10)

### `datto_bcdr_list_devices` (~59 tokens)

List all SIRIS/Alto BCDR appliances in the partner portal.

Input parameters:

- `page` (number): Page number (default: 1)
- `perPage` (number): Results per page (default: 250)

### `datto_bcdr_get_device` (~37 tokens)

Get details for a specific BCDR appliance by serial number.

Input parameters:

- `serialNumber` (string, required): The appliance serial number

### `datto_bcdr_list_assets` (~61 tokens)

List protected agents (assets) on a BCDR appliance. If serialNumber is omitted, the user will be prompted to choose or enter one.

Input parameters:

- `serialNumber` (string): Appliance serial number (optional — will elicit if omitted)

### `datto_bcdr_get_asset` (~44 tokens)

Get details for a specific protected agent on an appliance.

Input parameters:

- `agentId` (string, required): Agent identifier
- `serialNumber` (string, required): Appliance serial number

### `datto_bcdr_list_backups` (~47 tokens)

List recovery points / backups for a protected agent on an appliance.

Input parameters:

- `agentId` (string, required): Agent identifier
- `serialNumber` (string, required): Appliance serial number

### `datto_bcdr_list_screenshots` (~44 tokens)

List screenshot verifications for a protected agent.

Input parameters:

- `agentId` (string, required): Agent identifier
- `serialNumber` (string, required): Appliance serial number

### `datto_bcdr_get_screenshot` (~63 tokens)

Fetch a specific screenshot verification PNG. Returns base64-encoded image content.

Input parameters:

- `agentId` (string, required): Agent identifier
- `epoch` (number, required): Epoch timestamp of the screenshot to retrieve
- `serialNumber` (string, required): Appliance serial number

### `datto_bcdr_get_offsite_status` (~34 tokens)

Get off-site sync status for an appliance.

Input parameters:

- `serialNumber` (string, required): Appliance serial number

### `datto_bcdr_list_alerts` (~94 tokens)

List partner portal alerts. If date range is omitted, the user will be prompted to choose a window.

Input parameters:

- `page` (number): Page number (default: 1)
- `perPage` (number): Results per page (default: 250)
- `since` (string): ISO 8601 start datetime (optional)
- `until` (string): ISO 8601 end datetime (optional)

### `datto_bcdr_list_activity` (~89 tokens)

List activity log entries. If date range is omitted, the user will be prompted.

Input parameters:

- `page` (number): Page number (default: 1)
- `perPage` (number): Results per page (default: 250)
- `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-datto-bcdr-mcp/ghcr-io-wyre-ai-datto-bcdr-mcp-v1-1-5#diagnostics

## Score history

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

## Common questions

### What is the Datto BCDR MCP server?

Datto BCDR is an MCP server listed in the public MCP registry as io.github.WYRE-AI/datto-bcdr-mcp. MCP server for Datto BCDR, appliances, agents, recovery points, screenshots, alerts. This page covers its container image (ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.5).

### Is the Datto BCDR MCP server safe to use?

Datto BCDR 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 Datto BCDR MCP server expose?

Datto BCDR exposes 10 tools: datto_bcdr_list_devices, datto_bcdr_get_device, datto_bcdr_list_assets, datto_bcdr_get_asset, datto_bcdr_list_backups, and 5 more. Their descriptions and schemas cost roughly 572 tokens of context every time the server is loaded.

### Is the Datto BCDR MCP server still maintained?

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

Datto BCDR 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/datto-bcdr-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-datto-bcdr-mcp/ghcr-io-wyre-ai-datto-bcdr-mcp-v1-1-5.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-datto-bcdr-mcp/ghcr-io-wyre-ai-datto-bcdr-mcp-v1-1-5.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-datto-bcdr-mcp/ghcr-io-wyre-ai-datto-bcdr-mcp-v1-1-5