Datto SaaS Protection
OCI · GHCR.IO/WYRE-AI/DATTO-SAAS-PROTECTION-MCP
MCP server for Datto SaaS Protection — customers, seats, backup status, bulk seat licensing.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of OCI servers
Category Cloud Infrastructure
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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 921 tokens (~131/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Capabilities: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 0
- Provenance: pass → unverified ▼ security
- 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 Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Capabilities: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: v3.0.0 → v3.0.1 functional
- 9 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-saas-protection-mcp@v3.0.1
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_saas_bulk_seat_change License / pause / unlicense seats ~227
WRITE. License, Pause or Unlicense up to 100 seats of one type for a customer subscription (Seat Management 2.0 tenants). Pause stops new backups; Unlicense stops protection; License starts protection and billing. Asks the user to confirm; on clients without confirmation prompts it requires confirm: true after explicit user approval. PUT /v1/saas/{saasCustomerId}/{externalSubscriptionId}/bulkSeatChange.
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | string | yes | Action (case-sensitive). |
| confirm | boolean | – | Only for clients without confirmation prompts: set true after the user explicitly approved this exact change. |
| externalSubscriptionId | string | yes | externalSubscriptionId from datto_saas_list_domains, e.g. Classic:Office365:123456. |
| ids | array | yes | remoteId values of the seats to change (from datto_saas_list_seats). |
| saasCustomerId | number|string | yes | saasCustomerId from datto_saas_list_domains. |
| seatType | string | yes | Seat type (case-sensitive). |
No output schema declared.
No examples provided.
datto_saas_get_backup_stats Detailed backup statistics ~102
Detailed backup statistics for a SaaS Protection customer (per-service last-7-day status, last backups, storage). GET /v1/saas/{saasCustomerId}/detailedBackupStats.
| Name | Type | Req | Description |
|---|---|---|---|
| saasCustomerId | number|string | – | SaaS Protection customer ID (saasCustomerId from datto_saas_list_domains). Optional on read tools — the user is prompted to pick one if omitted and the client supports it. |
No output schema declared.
No examples provided.
datto_saas_get_seat Get one seat ~130
Look up a single seat for a customer by its remoteId or mainId (email / site URL) and render the seat card. Reads GET /v1/saas/{saasCustomerId}/seats.
| Name | Type | Req | Description |
|---|---|---|---|
| saasCustomerId | number|string | – | SaaS Protection customer ID (saasCustomerId from datto_saas_list_domains). Optional on read tools — the user is prompted to pick one if omitted and the client supports it. |
| seatId | string | yes | remoteId or mainId of the seat (from datto_saas_list_seats). |
No output schema declared.
No examples provided.
datto_saas_list_applications Backup status per application ~159
Backup history per suite / application (Exchange, OneDrive, SharePoint, Teams, Gmail, Drive...) for a SaaS Protection customer, including per-window backup status. Optionally include remote IDs per seat type. GET /v1/saas/{saasCustomerId}/applications.
| Name | Type | Req | Description |
|---|---|---|---|
| daysUntil | number | – | Days of backup history to include (Datto returns up to ~30). |
| includeRemoteID | boolean | – | Include remote IDs per seat type in the response. |
| saasCustomerId | number|string | – | SaaS Protection customer ID (saasCustomerId from datto_saas_list_domains). Optional on read tools — the user is prompted to pick one if omitted and the client supports it. |
No output schema declared.
No examples provided.
datto_saas_list_domains List SaaS Protection customers / domains ~107
List every Datto SaaS Protection customer domain (M365 tenant or Google Workspace domain) visible to the API key: saasCustomerId, customer name, domain, productType, externalSubscriptionId, retention, seatsUsed and backup stats. Start here — the IDs it returns are required by every other tool. GET /v1/saas/domains.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional case-insensitive filter on customer name, domain, organization or subscription ID. |
No output schema declared.
No examples provided.
datto_saas_list_seats List protected seats for a customer ~174
List seats (users, shared mailboxes, shared drives, sites, team sites, teams) for a SaaS Protection customer with seatType, seatState (Active / Paused / Archived / Unprotected), billable flag and remoteId. GET /v1/saas/{saasCustomerId}/seats.
| Name | Type | Req | Description |
|---|---|---|---|
| saasCustomerId | number|string | – | SaaS Protection customer ID (saasCustomerId from datto_saas_list_domains). Optional on read tools — the user is prompted to pick one if omitted and the client supports it. |
| seatState | string | – | Optional state filter applied to the result, e.g. Active, Paused, Archived, Unprotected. |
| seatType | string | – | Optional seat type filter (case-sensitive, sent to Datto). |
No output schema declared.
No examples provided.
How do I install the Datto SaaS Protection MCP server?
Datto SaaS Protection runs locally as a container image, launched with docker run --rm -i -e DATTO_SAAS_PUBLIC_KEY -e DATTO_SAAS_SECRET_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-saas-protection-mcp:v3.0.1. 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-saas-protection-mcp
claude mcp add wyre-ai-datto-saas-protection-mcp -- docker run --rm -i -e DATTO_SAAS_PUBLIC_KEY -e DATTO_SAAS_SECRET_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-saas-protection-mcp:v3.0.1
This image reads DATTO_SAAS_PUBLIC_KEY, DATTO_SAAS_SECRET_KEY, 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 SaaS Protection MCP server?
Datto SaaS Protection is an MCP server listed in the public MCP registry as io.github.WYRE-AI/datto-saas-protection-mcp. MCP server for Datto SaaS Protection, customers, seats, backup status, bulk seat licensing. This page covers its container image (ghcr.io/wyre-ai/datto-saas-protection-mcp).
Is the Datto SaaS Protection MCP server safe to use?
Datto SaaS Protection 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 SaaS Protection MCP server expose?
Datto SaaS Protection exposes 6 tools: datto_saas_list_domains, datto_saas_list_seats, datto_saas_get_seat, datto_saas_list_applications, datto_saas_get_backup_stats, datto_saas_bulk_seat_change. Their descriptions and schemas cost roughly 899 tokens of context every time the server is loaded.
Is the Datto SaaS Protection MCP server still maintained?
Datto SaaS Protection 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 SaaS Protection MCP server under?
Datto SaaS Protection 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.