Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Datto RMM

OCI · GHCR.IO/WYRE-AI/DATTO-RMM-MCP

MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.

+42 this week 51 Trust /100

Last scanned (11 hours ago)

Scores higher than 79% of OCI servers

Category Monitoring and Observability

Trust breakdown (7 categories)

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
Schema Quality & AI Usability87
  • 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 1301 tokens (~68/item across 19 items; 18 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 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.

Changelog

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 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.

  • 16 Oct 26 +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.

  • 15 Oct 26 +40
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.47 ▲ functional
    • Package version: v1.9.0 → v1.10.1 functional
  • 14 Oct 26 0
    • Package version: v1.9.0 → v1.10.1 functional
  • 13 Oct 26 0
    • Package version: v1.9.0 → v1.10.0 functional
  • 10 Oct 26 0
    • Package version: v1.9.0 → v1.10.0 functional
  • 7 Oct 26 −34
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: v1.9.0 → v1.10.0 functional
  • 1 Oct 26 43

    First indexed and scored.

Diagnostics

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-rmm-mcp@v1.10.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 →

MCP tools · 18 exposed · ~1,280 tokens

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 →

Tool Tokens
datto_find_device ~132

Find a device by hostname and return its UID plus a lightweight summary. Use this before datto_get_device when the user provides a hostname instead of a UID.

NameTypeReqDescription
exactMatchboolean–Require an exact (case-insensitive) hostname match. Set to false for partial/substring matching. Defaults to true.
hostnamestringyesHostname to search for, for example APP-HV-HOST06
maxnumber–Maximum number of matching devices to return (default: 25)
siteUidstring–Optional site UID to narrow the hostname lookup to one site

No output schema declared.

No examples provided.

datto_get_alert ~31

Get details for a specific alert by its UID

NameTypeReqDescription
alertUidstringyesThe alert UID

No output schema declared.

No examples provided.

datto_get_device ~50

Get full details for a specific device by its UID. If you only have a hostname, call datto_find_device first to resolve the UID.

NameTypeReqDescription
deviceUidstringyesThe device UID

No output schema declared.

No examples provided.

datto_get_device_audit ~63

Get audit data for a device (hardware, software, OS information)

NameTypeReqDescription
auditTypestring–Type of audit: 'full' for complete audit or 'software' for software inventory only
deviceUidstringyesThe device UID

No output schema declared.

No examples provided.

datto_get_device_patches ~51

Get Windows patch installation status for a device - per-patch installed/missing/pending status, severity, reboot requirement, and KB article

NameTypeReqDescription
deviceUidstringyesThe device UID

No output schema declared.

No examples provided.

datto_get_job ~76

Get status and details for a quick job by its UID (e.g. queued/running/completed, device count, timestamps). Use this after datto_run_quickjob to check whether the job finished and how it went.

NameTypeReqDescription
jobUidstringyesThe job UID, returned by datto_run_quickjob

No output schema declared.

No examples provided.

datto_get_job_components ~39

Get the components (scripts/actions and their variables) that make up a quick job

NameTypeReqDescription
jobUidstringyesThe job UID

No output schema declared.

No examples provided.

datto_get_job_results ~83

Get the result of a quick job on one specific device — status, exit code, timing, and error message if it failed. Use datto_get_job first if you need to find which devices the job ran on.

NameTypeReqDescription
deviceUidstringyesThe device UID to get the job result for
jobUidstringyesThe job UID

No output schema declared.

No examples provided.

datto_get_job_stderr ~58

Get the captured stderr output of a quick job on a specific device. Use this to diagnose why a quick job failed.

NameTypeReqDescription
deviceUidstringyesThe device UID
jobUidstringyesThe job UID

No output schema declared.

No examples provided.

datto_get_job_stdout ~65

Get the captured stdout output of a quick job on a specific device. Use this to diagnose what a script actually printed when a quick job's outcome is unclear.

NameTypeReqDescription
deviceUidstringyesThe device UID
jobUidstringyesThe job UID

No output schema declared.

No examples provided.

datto_get_site ~31

Get details for a specific site by its UID

NameTypeReqDescription
siteUidstringyesThe site UID

No output schema declared.

No examples provided.

datto_get_site_patches ~35

Get Windows patch installation status across all devices in a site

NameTypeReqDescription
siteUidstringyesThe site UID

No output schema declared.

No examples provided.

datto_list_alerts ~59

List open alerts. Can filter by site.

NameTypeReqDescription
maxnumber–Maximum number of results (default: 50)
siteUidstring–Filter alerts by site UID (optional - if omitted, returns all account alerts)

No output schema declared.

No examples provided.

datto_list_components ~226

List components (the scripts/monitors available to run as quick jobs) in the account, optionally filtered by a case-insensitive substring of the name. Use this to find a componentUid for datto_run_quickjob — otherwise there's no way to get one short of the Datto RMM web UI. Each result's `variables` lists what datto_run_quickjob's `variables` map needs to be filled in with to run that component. A quickjob HTTP 500 usually means the API user's security role is below the component's Level (Datto returns 500 where 403 belongs). The API does not expose component Level; check it in the RMM web UI under the component's settings before blaming the payload.

NameTypeReqDescription
maxnumber–Maximum number of results (default: 50)
namestring–Case-insensitive substring filter on component name, e.g. "disk" or "cleanup". Applied across every page of the account's component catalogue before truncating to max, so a match on a later page isn'…

No output schema declared.

No examples provided.

datto_list_devices ~78

List all devices in Datto RMM. Can filter by site. To look up a single device by hostname, use datto_find_device instead.

NameTypeReqDescription
maxnumber–Maximum number of results (default: 50)
siteUidstring–Filter devices by site UID (optional - if omitted, returns all devices)

No output schema declared.

No examples provided.

datto_list_sites ~33

List all sites in the account

NameTypeReqDescription
maxnumber–Maximum number of results (default: 50)

No output schema declared.

No examples provided.

datto_resolve_alert ~31

Resolve an alert by its UID

NameTypeReqDescription
alertUidstringyesThe alert UID to resolve

No output schema declared.

No examples provided.

datto_run_quickjob ~139

Run a quick job on a device. Returns a job UID — pass it to datto_get_job, datto_get_job_components, datto_get_job_results, datto_get_job_stdout, and datto_get_job_stderr to check the job's status and retrieve its output, since this call itself is fire-and-forget.

NameTypeReqDescription
componentUidstringyesUID of the component to run
deviceUidstringyesThe device UID to run the job on
jobNamestringyesName for the quick job
variablesobject–Variables to pass to the job (key-value pairs)

No output schema declared.

No examples provided.

Install

How do I install the Datto RMM MCP server?

Datto RMM runs locally as a container image, launched with docker run --rm -i -e DATTO_API_KEY -e DATTO_API_SECRET -e DATTO_PLATFORM -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.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-rmm-mcp

# add to Claude Code
claude mcp add wyre-ai-datto-rmm-mcp -- docker run --rm -i -e DATTO_API_KEY -e DATTO_API_SECRET -e DATTO_PLATFORM -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, 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.

Common questions

What is the Datto RMM MCP server?

Datto RMM is an MCP server listed in the public MCP registry as io.github.WYRE-AI/datto-rmm-mcp. MCP server for Datto RMM, devices, alerts, sites, jobs, and audit data. This page covers its container image (ghcr.io/wyre-ai/datto-rmm-mcp).

Is the Datto RMM MCP server safe to use?

Datto RMM scores 51 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 RMM MCP server expose?

Datto RMM exposes 18 tools: datto_list_devices, datto_find_device, datto_get_device, datto_list_alerts, datto_get_alert, and 13 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.

Is the Datto RMM MCP server still maintained?

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

Datto RMM 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.