DetentPoint.ClusterValidator.Mcp 1.12.3

ClusterValidator

Read-only health validation for Windows Server Failover Clusters hosting SQL Server Failover Cluster Instances (FCI), run locally as a stdio MCP tool.

It runs 16 phases against your cluster nodes via CIM and Active Directory — PreFlight plus 15 validation phases spanning storage and MPIO topology, SCSI-3 reservations, quorum and witness, heartbeat thresholds, time skew, hotfix parity, pending reboots, service-account hygiene, network configuration drift, LUN hygiene, and the Active Directory identity of the node/CNO/VCO accounts, plus Microsoft's Test-Cluster suite. get_phases returns all 16; PreFlight is marked automatic because it always runs first and is not opt-in.

Prerequisites

• Windows only — the engine uses CIM/WMI and DirectoryServices.
• The .NET runtime — this is a .NET stdio MCP server.
• WinRM and CIM line-of-sight to the cluster nodes.
• The Failover Clustering feature present.

Not covered

• Kubernetes.
• SQL Server Always On Availability Groups — this validates FCI.

Install and configure

Point your MCP client at the tool:

{
  "mcpServers": {
    "cluster-validator": {
      "command": "dnx",
      "args": ["DetentPoint.ClusterValidator.Mcp", "--yes"]
    }
  }
}

Licensing

With no CV_LICENSE set, the tool runs in Free mode — 2 clusters per calendar month. To validate more, supply the license from your purchase as the CV_LICENSE environment variable (or point CLUSTERVALIDATOR_LICENSE_FILE at a .lic file). Licenses are verified offline — no network call.

Read-only, and your data stays local

Every check is read-only — no cluster state is changed. The tool runs on your machine and reads your cluster over your own network, so your cluster data and reports never leave your environment.

More at https://detentpoint.com/clustervalidator