Domotz Agents — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Domotz Agents (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Domotz agents (also called collectors or probes) are software or hardware appliances deployed at customer sites that perform network discovery, device monitoring, and data collection. Each agent represents a monitored site/location and is the entry point for all device and network operations.
never an AI subagent definition under agents/*.md.
one per site, not one per endpoint. RMM endpoint agents are atera or ncentral; the Huntress endpoint sensor is huntress-agents.
health, licensing, and connectivity; the devices it discovered are domotz-devices.
Agents are deployed at customer sites and maintain a persistent connection to the Domotz cloud. Each agent:
cannot trigger one
| Status | Meaning |
|---|---|
ONLINE | Agent is connected and reporting |
OFFLINE | Agent is not connected to the cloud |
| Tool | Description | Arguments |
|---|---|---|
domotz_agents_list | Every agent on the account, with status, IP, and location | (none) |
domotz_agents_get | Detail for one collector | agent_id |
These two are the only account-wide entry point. Every other Domotz tool requires an agent_id, so a fleet answer always starts here and then fans out one call per agent.
Do not confuse domotz_status with agent status: domotz_status reports whether the MCP server can reach Domotz at all. A collector's own state is the status field on these two tools.
domotz_agents_listReturns all agents associated with your account. Takes no arguments.
Example response:
[
{
"id": 12345,
"display_name": "Acme Corp - Main Office",
"status": {
"value": "ONLINE"
},
"license": {
"bound_devices": 47
},
"location": {
"latitude": 40.7128,
"longitude": -74.0060
},
"last_seen": "2026-03-27T15:30:00Z"
}
]domotz_agents_getParameters:
agent_id -- The specific agent ID (required, number)Example response:
{
"id": 12345,
"display_name": "Acme Corp - Main Office",
"status": {
"value": "ONLINE"
},
"license": {
"bound_devices": 47,
"allowed_devices": 100
},
"access_right": {
"api_enabled": true
},
"creation_time": "2025-01-15T10:00:00Z",
"last_seen": "2026-03-27T15:30:00Z"
}domotz_agents_list to get all agentslicense.bound_devices vs license.allowed_devices for capacityThis is the check that gates every other Domotz report. An offline collector keeps serving its last-known device and metric data, so any downstream read from that site is stale in a way the payload does not advertise. Do it first, not last.
domotz_agents_list to get all sitesdisplay_name, status, and bound device countbound_devices to allowed_devices for eachCause: Invalid agent ID or agent has been deleted Solution: Verify the agent ID; check if the site was decommissioned
Cause: Network connectivity issue, agent service stopped, or hardware failure Solution: Check site connectivity; verify agent service is running; contact site contact
Cause: No agents deployed or API key has limited scope Solution: Verify API key permissions; check Domotz Portal for agent list
last_seen timestamps to detect offline agents earlybound_devices vs allowed_devices for license planningdisplay_name consistently with client site names in your PSAintegration reads alert configuration but cannot create it
domotz_agents_get returns site location coordinates and licencecounts; treat it as customer data, not just an operational read
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.