Is io.github.wyre-technology/kaseya-vsa-mcp safe to use?

io.github.wyre-technology/kaseya-vsa-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.

How do I install io.github.wyre-technology/kaseya-vsa-mcp?

io.github.wyre-technology/kaseya-vsa-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.wyre-technology/kaseya-vsa-mcp do?

io.github.wyre-technology/kaseya-vsa-mcp provides 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. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.wyre-technology/kaseya-vsa-mcp?

io.github.wyre-technology/kaseya-vsa-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.wyre-technology/kaseya-vsa-mcp actively maintained?

io.github.wyre-technology/kaseya-vsa-mcp is actively maintained — last commit was 1 day ago.

io.github.wyre-technology/kaseya-vsa-mcp

npm

MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.

15.5M/wk 12 tools GitHub npm

No known CVEs

Apache-2.0 license

Actively maintained

Last commit 1d ago

Works with most clients

Transport: stdio

12 tools · ~565 tok

Grade B · 0.3% of 200K ctx

MCPpedia last refreshed this data 23h ago

Edit this pageView history

io.github.wyre-technology/kaseya-vsa-mcp is an MCP server that MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets. Its tool list has not been published yet over stdio, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-kaseya-vsa-mcp": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-kaseya-vsa-mcp)](https://mcppedia.org/s/io-github-wyre-technology-kaseya-vsa-mcp)

Read me

What io.github.wyre-technology/kaseya-vsa-mcp does

Model Context Protocol (MCP) server for the Kaseya VSA RMM API. Exposes managed endpoints, software / hardware inventory, patch state, agent procedures, alarms, Service Desk tickets, organizations, and machine groups

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (12)

Click any tool to inspect its schema.

~565 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/kaseya-vsa-mcp safe to use?: io.github.wyre-technology/kaseya-vsa-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.wyre-technology/kaseya-vsa-mcp?: io.github.wyre-technology/kaseya-vsa-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.wyre-technology/kaseya-vsa-mcp do?: io.github.wyre-technology/kaseya-vsa-mcp provides 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. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.wyre-technology/kaseya-vsa-mcp?: io.github.wyre-technology/kaseya-vsa-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.wyre-technology/kaseya-vsa-mcp actively maintained?: io.github.wyre-technology/kaseya-vsa-mcp is actively maintained — last commit was 1 day ago.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.5k 3

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

148 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

331 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.wyre-technology/kaseya-vsa-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-kaseya-vsa-mcp": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-kaseya-vsa-mcp)](https://mcppedia.org/s/io-github-wyre-technology-kaseya-vsa-mcp)

Read me

What io.github.wyre-technology/kaseya-vsa-mcp does

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Kaseya VSA MCP Server

Tools

Tool	Description
`kaseya_vsa_list_agents`	List managed endpoints (agents). Optional `$filter`.
`kaseya_vsa_get_agent`	Get an agent's details by ID (renders as an interactive card in MCP Apps hosts).
`kaseya_vsa_get_software_inventory`	Installed software for an agent.
`kaseya_vsa_get_hardware_inventory`	Hardware audit for an agent.
`kaseya_vsa_get_patch_status`	Pending and installed patches for an agent.
`kaseya_vsa_deploy_patches_now`	Force a patch deploy on an agent (destructive — confirmation required).
`kaseya_vsa_list_procedures`	Agent procedures available to run.
`kaseya_vsa_run_procedure`	Execute a procedure on an agent (destructive — confirmation required).
`kaseya_vsa_list_alarms`	Open alarms (optional state filter; date-window elicitation if missing).
`kaseya_vsa_list_tickets`	Service Desk tickets (returns a friendly message if SD module isn't enabled).
`kaseya_vsa_list_organizations`	Tenant organizations.
`kaseya_vsa_list_machine_groups`	Machine group hierarchy.

When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.

Interactive device card (MCP Apps)

kaseya_vsa_get_agent renders as a read-only interactive device card in MCP Apps hosts (Claude Desktop/web), showing the endpoint's name, online status, organization, machine group, OS, IP address, and last check-in. The card is neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) applied at serve time. Plain-JSON behavior is unchanged in other hosts. After editing ui/, regenerate the embedded bundle with npm run build:ui.

Configuration

Environment-variable mode (default)

Variable	Required	Description
`KASEYA_VSA_TENANT_URL`	yes	Full base URL incl. `/api/v1.0`
`KASEYA_VSA_USERNAME`	one of	Local-auth username
`KASEYA_VSA_PASSWORD`	one of	Local-auth password (secret)
`KASEYA_VSA_K1_TOKEN`	one of	Kaseya One SSO token (alternative to username + password)
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Either the username + password pair OR the KASEYA_VSA_K1_TOKEN is required.

Gateway mode

When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:

X-Kaseya-VSA-Tenant-Url (required)
X-Kaseya-VSA-Username (with password)
X-Kaseya-VSA-Password (with username)
X-Kaseya-VSA-K1-Token (alternative to username + password)

Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.

Local development

npm install
npm run build
KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
  KASEYA_VSA_USERNAME=... \
  KASEYA_VSA_PASSWORD=... \
  npm start

Run as HTTP for testing:

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

docker build -t kaseya-vsa-mcp .
docker run --rm -p 8080:8080 \
  -e KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 

... [View full README on GitHub](https://github.com/wyre-technology/kaseya-vsa-mcp#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (12)

Click any tool to inspect its schema.

~565 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/kaseya-vsa-mcp safe to use?: io.github.wyre-technology/kaseya-vsa-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.wyre-technology/kaseya-vsa-mcp?: io.github.wyre-technology/kaseya-vsa-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.wyre-technology/kaseya-vsa-mcp do?: io.github.wyre-technology/kaseya-vsa-mcp provides 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. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.wyre-technology/kaseya-vsa-mcp?: io.github.wyre-technology/kaseya-vsa-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.wyre-technology/kaseya-vsa-mcp actively maintained?: io.github.wyre-technology/kaseya-vsa-mcp is actively maintained — last commit was 1 day ago.