# Kaseya BMS (oci · ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5)

MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.

- Trust score: 54/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5`: 54/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5.md), [page](https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 641 tokens (~58/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

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

## Install

### How do I install the Kaseya BMS MCP server?

Kaseya BMS runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/kaseya-bms-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.

### Claude

```bash
claude mcp add wyre-ai-kaseya-bms-mcp -- docker run --rm -i ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-kaseya-bms-mcp -- docker run --rm -i ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-kaseya-bms-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-kaseya-bms-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-kaseya-bms-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 54, +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.

### 2026-09-17 (score 53, +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.

### 2026-09-15 (score 52, +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.

### 2026-09-13 (score 51, +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.

### 2026-09-11 (score 50, +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.

### 2026-09-09 (score 49, +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.

### 2026-09-07 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 47, +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.

## MCP tools (10)

### `kaseya_bms_list_tickets` (~83 tokens)

List BMS tickets. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a status scope.

Input parameters:

- `filter` (string): OData $filter expression (optional)
- `skip` (number): Records to skip
- `top` (number): Max records (default 100)

### `kaseya_bms_get_ticket` (~32 tokens)

Get details for a single ticket by ticket id.

Input parameters:

- `ticketId` (string, required): Ticket identifier

### `kaseya_bms_create_ticket` (~103 tokens)

Create a new ticket in BMS. DESTRUCTIVE: requires user confirmation before submission.

Input parameters:

- `accountId` (string): Account / client identifier
- `contactId` (string): Contact identifier (optional)
- `description` (string, required): Ticket description body
- `priority` (string): Priority (e.g. Low / Medium / High)
- `status` (string): Initial status (optional)
- `subject` (string, required): Ticket subject / title

### `kaseya_bms_add_ticket_note` (~69 tokens)

Append a note to an existing ticket. DESTRUCTIVE: requires user confirmation before submission.

Input parameters:

- `body` (string, required): Note body / text content
- `isInternal` (boolean): Mark note as internal-only (default false)
- `ticketId` (string, required): Ticket identifier

### `kaseya_bms_list_time_entries` (~94 tokens)

List time entries by date range. If no range is given the user is prompted (24h / 7d / 30d / custom / all).

Input parameters:

- `endDate` (string): ISO date (YYYY-MM-DD) end of range
- `startDate` (string): ISO date (YYYY-MM-DD) start of range
- `top` (number): Max records (default 100)

### `kaseya_bms_list_accounts` (~50 tokens)

List accounts (clients) in the BMS tenant.

Input parameters:

- `filter` (string): OData $filter expression (optional)
- `top` (number): Max records (default 250)

### `kaseya_bms_list_contacts` (~47 tokens)

List contacts in the BMS tenant.

Input parameters:

- `filter` (string): OData $filter expression (optional)
- `top` (number): Max records (default 250)

### `kaseya_bms_list_contracts` (~48 tokens)

List contracts in the BMS tenant.

Input parameters:

- `filter` (string): OData $filter expression (optional)
- `top` (number): Max records (default 250)

### `kaseya_bms_list_service_catalog` (~35 tokens)

List service catalog items configured in the tenant.

Input parameters:

- `top` (number): Max records (default 250)

### `kaseya_bms_search_knowledge_base` (~57 tokens)

Search the BMS knowledge base. If no query is provided the user is prompted for one.

Input parameters:

- `query` (string): Free-text search query
- `top` (number): Max records (default 50)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 54
- 2026-09-18: 53
- 2026-09-17: 53
- 2026-09-16: 52
- 2026-09-15: 52
- 2026-09-14: 51
- 2026-09-13: 51
- 2026-09-12: 50
- 2026-09-11: 50
- 2026-09-10: 49
- 2026-09-09: 49
- 2026-09-08: 48
- 2026-09-07: 48
- 2026-09-06: 47
- 2026-09-05: 47
- 2026-09-04: 47
- 2026-09-03: 46
- 2026-09-02: 46
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42
- 2026-08-27: 42
- 2026-08-26: 42

## Common questions

### What is the Kaseya BMS MCP server?

Kaseya BMS is an MCP server listed in the public MCP registry as io.github.WYRE-AI/kaseya-bms-mcp. MCP server for Kaseya BMS PSA, tickets, accounts, time entries, contracts. This page covers its container image (ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5).

### Is the Kaseya BMS MCP server safe to use?

Kaseya BMS scores 54 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 BMS MCP server expose?

Kaseya BMS exposes 10 tools: kaseya_bms_list_tickets, kaseya_bms_get_ticket, kaseya_bms_create_ticket, kaseya_bms_add_ticket_note, kaseya_bms_list_time_entries, and 5 more. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.

### Is the Kaseya BMS MCP server still maintained?

Kaseya BMS 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 BMS MCP server under?

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

## Links

- Repository: https://github.com/WYRE-AI/kaseya-bms-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-kaseya-bms-mcp/ghcr-io-wyre-ai-kaseya-bms-mcp-v1-1-5