ClusterValidator

AI-invokable, runs locally, and focused. Not another always-on monitoring suite. ClusterValidator runs where your clusters run, returns a clear pass, warn, or fail verdict, and gets out of the way.

What it checks, across 16 read-only validation phases: Windows Server Failover Cluster (WSFC) quorum, witness, and node votes. SQL Server Failover Cluster Instance (FCI) configuration and readiness. Network configuration parity and heartbeat thresholds. Storage, MPIO, and SCSI-3 persistent reservations. Active Directory cluster identity. Cluster resource and dependency health. It never writes to your cluster.

Five callable tools: run_cluster_validation, get_validation_result, get_phase_findings, export_cluster_report, and get_phases.

Scope: Windows Server Failover Clustering and SQL Server FCI. It does not validate Always On availability groups or Kubernetes.

Who it is for: Windows and SQL Server platform teams who want validation on demand, not another dashboard to watch. Teams building AI-assisted operations who need a trustworthy, runs-in-place MCP tool.

How it works: Install the validator from NuGet (dotnet tool install --global DetentPoint.ClusterValidator.Mcp) and point your AI assistant or MCP client at it. Prefer PowerShell? Also install the ClusterValidator.MCP module from the PowerShell Gallery (Install-Module ClusterValidator.MCP) and call the cmdlets directly from PowerShell 7. The module is a thin client for the validator, not a replacement for it.

Requirements: Windows, .NET, and WinRM and CIM line of sight to your cluster nodes. The Failover Clustering feature must be present. The PowerShell client additionally needs PowerShell 7.0 or later.

Runs entirely on your workstation. Its only network traffic is WinRM and CIM to your cluster nodes and LDAP to your domain controller, all inside your environment. No cluster data, findings, or telemetry ever leave your network, and licenses validate offline.

Built by Detent Point, LLC. PowerShell and SQL Server tooling for the AI-agent era.