Datto BCDR
OCI · GHCR.IO/WYRE-AI/DATTO-BCDR-MCP
MCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts.
Available components
Last scanned (12 hours ago)
Scores higher than 62% of OCI servers
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 598 tokens (~54/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 +34
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Capabilities: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 9
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/datto-bcdr-mcp@v1.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
datto_bcdr_get_asset ~44
Get details for a specific protected agent on an appliance.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
| serialNumber | string | yes | Appliance serial number |
No output schema declared.
No examples provided.
datto_bcdr_get_device ~37
Get details for a specific BCDR appliance by serial number.
| Name | Type | Req | Description |
|---|---|---|---|
| serialNumber | string | yes | The appliance serial number |
No output schema declared.
No examples provided.
datto_bcdr_get_offsite_status ~34
Get off-site sync status for an appliance.
| Name | Type | Req | Description |
|---|---|---|---|
| serialNumber | string | yes | Appliance serial number |
No output schema declared.
No examples provided.
datto_bcdr_get_screenshot ~63
Fetch a specific screenshot verification PNG. Returns base64-encoded image content.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
| epoch | number | yes | Epoch timestamp of the screenshot to retrieve |
| serialNumber | string | yes | Appliance serial number |
No output schema declared.
No examples provided.
datto_bcdr_list_activity ~89
List activity log entries. If date range is omitted, the user will be prompted.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
datto_bcdr_list_alerts ~94
List partner portal alerts. If date range is omitted, the user will be prompted to choose a window.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
datto_bcdr_list_assets ~61
List protected agents (assets) on a BCDR appliance. If serialNumber is omitted, the user will be prompted to choose or enter one.
| Name | Type | Req | Description |
|---|---|---|---|
| serialNumber | string | – | Appliance serial number (optional — will elicit if omitted) |
No output schema declared.
No examples provided.
datto_bcdr_list_backups ~47
List recovery points / backups for a protected agent on an appliance.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
| serialNumber | string | yes | Appliance serial number |
No output schema declared.
No examples provided.
datto_bcdr_list_devices ~59
List all SIRIS/Alto BCDR appliances in the partner portal.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (default: 1) |
| perPage | number | – | Results per page (default: 250) |
No output schema declared.
No examples provided.
datto_bcdr_list_screenshots ~44
List screenshot verifications for a protected agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
| serialNumber | string | yes | Appliance serial number |
No output schema declared.
No examples provided.
How do I install the Datto BCDR MCP server?
Datto BCDR runs locally as a container image, launched with docker run --rm -i -e DATTO_BCDR_PUBLIC_KEY -e DATTO_BCDR_PRIVATE_KEY -e DATTO_BCDR_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-ai/datto-bcdr-mcp
claude mcp add wyre-ai-datto-bcdr-mcp -- docker run --rm -i -e DATTO_BCDR_PUBLIC_KEY -e DATTO_BCDR_PRIVATE_KEY -e DATTO_BCDR_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.6
This image reads DATTO_BCDR_PUBLIC_KEY, DATTO_BCDR_PRIVATE_KEY, DATTO_BCDR_REGION, 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.
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).
Is the Datto BCDR MCP server safe to use?
Datto BCDR scores 44 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 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 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.