Help us improve
Share bugs, ideas, or general feedback.
From runzero
Manages RunZero sites: list/create/update sites, define scan scopes/exclusions, deploy explorers, organize assets by location or client.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin runzeroHow this skill is triggered — by the user, by Claude, or both
Slash command
/runzero:sitesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Sites are the primary organizational unit in RunZero. Each site represents a network boundary -- typically a client location, office, data center, or cloud environment. Sites contain assets, define scan targets, and have explorers assigned for discovery. For MSPs, each client typically maps to one or more sites.
Manages RunZero network discovery scan tasks: creates scans, schedules recurring ones, manages explorers, configures parameters, reviews results via API.
Lists, manages, and configures Datto RMM sites for client locations, covering structure, settings, proxy configuration, site variables, device assignment, and scoped operations.
Maps internet-facing assets, ranks by exploitability risk, identifies exposed ports/services, public storage, and vulnerabilities from an attacker's perspective. Use for attack surface analysis.
Share bugs, ideas, or general feedback.
Sites are the primary organizational unit in RunZero. Each site represents a network boundary -- typically a client location, office, data center, or cloud environment. Sites contain assets, define scan targets, and have explorers assigned for discovery. For MSPs, each client typically maps to one or more sites.
Organization (RunZero Account)
+-- Site: "ACME HQ"
| +-- Explorer: acme-hq-scanner
| +-- Assets: 342
| +-- Subnets: 192.168.0.0/16
|
+-- Site: "ACME Branch - Denver"
| +-- Explorer: acme-den-scanner
| +-- Assets: 58
| +-- Subnets: 10.10.0.0/24
|
+-- Site: "ACME Cloud - Azure"
+-- Explorer: hosted-explorer
+-- Assets: 127
+-- Subnets: (cloud connector)
Each site defines its network scope:
Each site needs at least one explorer to perform scans:
runzero_sites_list
Parameters:
count -- Results per pageoffset -- Pagination offsetExample response:
{
"sites": [
{
"id": "site-uuid-456",
"name": "ACME HQ",
"description": "ACME Corp headquarters - main office",
"scope": "192.168.0.0/16",
"excludes": "192.168.255.0/24",
"asset_count": 342,
"service_count": 1205,
"explorer_count": 1,
"created_at": "2025-06-01T00:00:00Z",
"updated_at": "2026-03-27T08:30:00Z"
}
]
}
runzero_sites_get
Parameters:
site_id -- The specific site UUIDReturns full site details including scope, exclusions, asset/service counts, and assigned explorers.
runzero_sites_create
Parameters:
name -- Site name (required)description -- Human-readable descriptionscope -- Network scope (CIDR ranges)excludes -- Excluded rangesrunzero_sites_update
Parameters:
site_id -- Site to update (required)name -- Updated namedescription -- Updated descriptionscope -- Updated network scopeexcludes -- Updated exclusionsrunzero_sites_createrunzero_sites_get for the target siterunzero_tasks_listrunzero_sites_list to get all sitesrunzero_sites_getrunzero_sites_updateCause: Invalid site UUID Solution: List all sites and verify the ID
Cause: Site has no explorer; scans cannot run Solution: Deploy a managed explorer or assign a hosted explorer
Cause: Two sites have overlapping subnets Solution: Review and adjust site scopes to avoid duplicate asset assignment