Kaseya VSA
OCI · GHCR.IO/WYRE-AI/KASEYA-VSA-MCP:V1.1.5 · SCANNED SEP 20
MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 25 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
- Tool/resource definitions use about 577 tokens (~44/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kaseya_vsa_deploy_patches_now" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 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.
How do I install the Kaseya VSA MCP server?
Kaseya VSA runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5. 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/kaseya-vsa-mcp:v1.1.5
claude mcp add wyre-ai-kaseya-vsa-mcp -- docker run --rm -i ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5
{
"mcpServers": {
"wyre-ai-kaseya-vsa-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"
]
}
}
} {
"servers": {
"wyre-ai-kaseya-vsa-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"
]
}
}
} codex mcp add wyre-ai-kaseya-vsa-mcp -- docker run --rm -i ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wyre-ai-kaseya-vsa-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"
],
"enabled": true
}
}
} mcp_servers:
wyre-ai-kaseya-vsa-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"] {
"McpServers": {
"wyre-ai-kaseya-vsa-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"
]
}
}
} {
"mcpServers": {
"wyre-ai-kaseya-vsa-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5
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 →
kaseya_vsa_deploy_patches_now ~42
Force a patch deploy on an endpoint immediately. DESTRUCTIVE: requires user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
No output schema declared.
No examples provided.
kaseya_vsa_get_agent ~35
Get details for a managed endpoint by agent ID.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier (AgentGuid) |
No output schema declared.
No examples provided.
kaseya_vsa_get_hardware_inventory ~32
Get hardware audit data for an endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
No output schema declared.
No examples provided.
kaseya_vsa_get_patch_status ~35
Get patch status (pending and installed) for an endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
No output schema declared.
No examples provided.
kaseya_vsa_get_software_inventory ~34
Get installed software for an endpoint (audit data).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
No output schema declared.
No examples provided.
kaseya_vsa_list_agents ~91
List managed endpoints (agents) in the Kaseya VSA tenant. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a scope.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| skip | number | – | Records to skip |
| top | number | – | Max records (default 100) |
No output schema declared.
No examples provided.
kaseya_vsa_list_alarms ~72
List alarms. Accepts optional OData $filter (e.g. "State eq 'open'"); if omitted the user is prompted for a state.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| top | number | – | Max records (default 100) |
No output schema declared.
No examples provided.
kaseya_vsa_list_machine_groups ~35
List machine groups (organization → group hierarchy).
| Name | Type | Req | Description |
|---|---|---|---|
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_vsa_list_organizations ~33
List organizations defined in the tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_vsa_list_procedures ~34
List agent procedures available to run on an endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
No output schema declared.
No examples provided.
kaseya_vsa_list_tickets ~61
List Service Desk tickets. Returns a friendly message if the Service Desk module is not enabled on the tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| top | number | – | Max records (default 100) |
No output schema declared.
No examples provided.
kaseya_vsa_run_procedure ~49
Execute an agent procedure on an endpoint. DESTRUCTIVE: requires user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent identifier |
| procedureId | string | yes | Procedure identifier |
No output schema declared.
No examples provided.
What is the Kaseya VSA MCP server?
Kaseya VSA is an MCP server listed in the public MCP registry as io.github.WYRE-AI/kaseya-vsa-mcp. MCP server for Kaseya VSA RMM, agents, patches, procedures, alarms, tickets. This page covers its container image (ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.5).
Is the Kaseya VSA MCP server safe to use?
Kaseya VSA scores 52 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 Kaseya VSA MCP server expose?
Kaseya VSA exposes 12 tools: kaseya_vsa_list_agents, kaseya_vsa_get_agent, kaseya_vsa_get_software_inventory, kaseya_vsa_get_hardware_inventory, kaseya_vsa_get_patch_status, and 7 more. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.
Is the Kaseya VSA MCP server still maintained?
Kaseya VSA is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Kaseya VSA MCP server under?
Kaseya VSA 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.