VSPC MCP server
Related Servers
Alternatives to VSPC MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis server provides a full API interface for the Splunk On-Call (VictorOps) platform, allowing comprehensive interaction with incident management tools. It enables users to manage incidents, configure organizational structures, and view on-call schedules.MIT
- AlicenseAqualityAmaintenanceAI-powered Veeam Backup & Replication operations MCP server with tools for managing jobs, restores, sessions, and repositories, featuring built-in governance, audit logging, and safety controls.27MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.21Apache 2.0
- AlicenseAqualityBmaintenanceEnables managing and monitoring MSP360's Managed Backup Service, covering companies, computers, backup plans, monitoring, and licenses.14Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes the Cove Data Protection (N-able Backup) Management Service JSON-RPC API as 247 tools for managing backup, recovery, and partner/account operations.-
- AlicenseNot gradedqualityCmaintenanceExtends Veeam Intelligence to MCP-compatible clients, enabling secure, real-time operational insight across Veeam Backup & Replication, Veeam ONE, and VSPC via natural language or AI workflows.22MIT
TDQS
Scored across 17 tools
Tools map cleanly to distinct resources (companies, backup servers, VBR jobs, agent jobs, alarms, licenses, protected VMs, policies), and the descriptions actively disambiguate the trickiest pairs (vspc_list_jobs vs vspc_list_failed_jobs vs vspc_failed_jobs_summary) with explicit "use X instead" guidance. The only residual overlap is between list_jobs/list_failed_jobs/failed_jobs_summary, which is an intentional layering but still requires the agent to read descriptions carefully.
Almost everything follows vspc_<verb>_<noun> in snake_case (list_companies, get_company, start_job, retry_job, resolve_alarm). Two deviations stand out: vspc_failed_jobs_summary uses a noun-only lead instead of a verb, and vspc_about is a bare verbless noun, breaking the otherwise predictable pattern.
17 tools is on the heavier side of the ideal band, but each maps to a real object in an enterprise backup console (companies, servers, jobs, agents, alarms, licensing, VMs, policies), so most earn their place. A couple of the read variants (console license vs license usage, failed jobs vs summary) could arguably be merged or made flag-based.
Read coverage is strong, and the action surface (start/retry job, acknowledge/resolve alarm) covers the core triage workflow. However, there is no stop/cancel job, no session-history or per-job detail tool, no repository/agent inventory, and no create/update for policies or companies, leaving obvious dead ends such as 'a job is stuck and I can't stop it.'