io.github.WYRE-AI/kaseya-bms-mcp

Kaseya BMS

Is the Kaseya BMS MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-26.

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

alive probed 2026-11-15 · unchanged since 2026-10-26

10tools

1.5ktokens in Claude Opus 5.5

0.8 %of Claude's 200k window

0.6×the median server

491 msto initialize

4 msto list tools

Run it: docker run -i --rm ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6 (stdio, probed in a container with the network off)
Host: ghcr.io
Reports itself as: kaseya-bms-mcp 0.0.0
Capabilities: resources, tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 1.5k tokens in Claude Opus 5.5, exact, measured 2026-10-26. With the Claude Code prefix mcp__…__ on each tool name: 1.7k. The o200k_base estimate is 861. Counted again when the tool definitions change. Method.
Repository: https://github.com/WYRE-AI/kaseya-bms-mcp
Website: https://github.com/WYRE-AI/kaseya-bms-mcp
Registry: active, updated 2026-10-14 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.79×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
kaseya_bms_create_ticket	252	141	16 %
kaseya_bms_list_time_entries	213	119	14 %
kaseya_bms_list_tickets	191	107	12 %
kaseya_bms_add_ticket_note	181	101	12 %
kaseya_bms_search_knowledge_base	140	78	9 %

These registry entries have the same tool names and the same schema sizes.

Other registry entries on ghcr.io, the ones next to this name; all of them.

Servers that mention kaseya.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.