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

MCPcommunity
v1.1.4io.github.wyre-technologyUnknownUpdated 1mo agoGitHub

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

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Reads these credentials
  • KASEYA_BMS_API_TOKENAPI keyoptional

    BMS API token (omit if using Kaseya One token)

  • KASEYA_BMS_K1_TOKENAPI keyoptional

    Kaseya One SSO token (alternative to API token)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.wyre-technology
LicenseUnknown
Version1.1.4
Sourcemcp-registry
GitHubwyre-technology/kaseya-bms-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface10 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJul 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

kaseya_bms_list_ticketsNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_get_ticketNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_create_ticketNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_add_ticket_noteNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_list_time_entriesNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_list_accountsNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_list_contactsNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_list_contractsNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_list_service_catalogNo description published

This tool published no description. Forge does not invent one.

kaseya_bms_search_knowledge_baseNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.