Kaseya BMS
OCI · GHCR.IO/WYRE-TECHNOLOGY/KASEYA-BMS-MCP:V1.1.4
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
Available components
Last scanned (6 minutes ago)
Scores higher than 82% of OCI servers
Category CRM and Sales
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 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 641 tokens (~58/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
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.
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
- Stability: pass → 0.83 functional
- 10 Oct 26 0
- Stability: 0.97 → pass security
- 9 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 80 to 97. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
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 17 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4
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_bms_add_ticket_note ~69
Append a note to an existing ticket. DESTRUCTIVE: requires user confirmation before submission.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Note body / text content |
| isInternal | boolean | – | Mark note as internal-only (default false) |
| ticketId | string | yes | Ticket identifier |
No output schema declared.
No examples provided.
kaseya_bms_create_ticket ~103
Create a new ticket in BMS. DESTRUCTIVE: requires user confirmation before submission.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | Account / client identifier |
| contactId | string | – | Contact identifier (optional) |
| description | string | yes | Ticket description body |
| priority | string | – | Priority (e.g. Low / Medium / High) |
| status | string | – | Initial status (optional) |
| subject | string | yes | Ticket subject / title |
No output schema declared.
No examples provided.
kaseya_bms_get_ticket ~32
Get details for a single ticket by ticket id.
| Name | Type | Req | Description |
|---|---|---|---|
| ticketId | string | yes | Ticket identifier |
No output schema declared.
No examples provided.
kaseya_bms_list_accounts ~50
List accounts (clients) in the BMS tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_bms_list_contacts ~47
List contacts in the BMS tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_bms_list_contracts ~48
List contracts in the BMS tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression (optional) |
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_bms_list_service_catalog ~35
List service catalog items configured in the tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| top | number | – | Max records (default 250) |
No output schema declared.
No examples provided.
kaseya_bms_list_tickets ~83
List BMS tickets. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a status 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_bms_list_time_entries ~94
List time entries by date range. If no range is given the user is prompted (24h / 7d / 30d / custom / all).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
kaseya_bms_search_knowledge_base ~57
Search the BMS knowledge base. If no query is provided the user is prompted for one.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Free-text search query |
| top | number | – | Max records (default 50) |
No output schema declared.
No examples provided.
How do I install the Kaseya BMS MCP server?
Kaseya BMS runs locally as a container image, launched with docker run --rm -i -e KASEYA_BMS_TENANT_SUBDOMAIN -e KASEYA_BMS_API_TOKEN -e KASEYA_BMS_K1_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4. 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-technology/kaseya-bms-mcp:v1.1.4
claude mcp add wyre-technology-kaseya-bms-mcp -- docker run --rm -i -e KASEYA_BMS_TENANT_SUBDOMAIN -e KASEYA_BMS_API_TOKEN -e KASEYA_BMS_K1_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4
This image reads KASEYA_BMS_TENANT_SUBDOMAIN, KASEYA_BMS_API_TOKEN, KASEYA_BMS_K1_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Kaseya BMS MCP server?
Kaseya BMS is an MCP server listed in the public MCP registry as io.github.wyre-technology/kaseya-bms-mcp. MCP server for Kaseya BMS PSA, tickets, accounts, time entries, contracts. This page covers its container image (ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4).
Is the Kaseya BMS MCP server safe to use?
Kaseya BMS scores 51 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 17 October 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.