Detent Point
ClusterValidator
Sixteen read-only checks across your Windows Server Failover Cluster — storage, quorum, heartbeat, patch parity, AD identity — built for clusters hosting SQL Server FCIs. Run it before the maintenance window, not after the incident.
ClusterValidator is a read-only health validator for Windows Server Failover Clusters hosting SQL Server FCIs, run in your own environment. It ships as a local MCP server — installed from NuGet, run from a machine that can reach your cluster nodes — and you can drive it two ways: point your AI assistant at it, or skip the assistant entirely and use the ClusterValidator.MCP PowerShell module. Either way, validation is a callable tool that returns structured findings — exit code 0 on a clean run, 1 on any failure.
For an AI assistant, add it to your MCP client’s configuration:
{
"mcpServers": {
"cluster-validator": {
"command": "dnx",
"args": ["DetentPoint.ClusterValidator.Mcp", "--yes"]
}
}
}For plain PowerShell, install the validator once (dotnet tool install --global DetentPoint.ClusterValidator.Mcp), then Install-Module ClusterValidator.MCP for the cmdlets — Connect-CvValidator, Invoke-CvValidation, Get-CvValidationResult, Export-CvValidationReport — no AI assistant involved. The module is a thin client for the same validator; it does nothing without it. PowerShell 7 or later, Windows only.
Every plan includes all sixteen validation phases. The only difference is how many distinct clusters you validate per month. Re-running a cluster you have already validated this month doesn’t count again.
| Tier | Clusters / month | Monthly |
|---|---|---|
| Free | 2 | Start free → |
| Starter | 5 | $79 / mo → |
| Professional | 20 | $499 / mo → |
| Enterprise | 100 | $1,999 / mo → |
| Enterprise Plus | Unlimited | $4,999 / mo → |
No credit card for Free. Upgrade, downgrade, or cancel anytime.
ClusterValidator sells on Microsoft Marketplace and AWS Marketplace — buy it inside the cloud agreement and portal you already use, through procurement that has already approved the vendor. If your organization has an Azure agreement, we can also invoice against it directly.
We can invoice ClusterValidator directly against your existing Microsoft agreement today. Tell us your seat count and how your procurement works, and we will send a quote with a PO number on it.
Talk to us →ClusterValidator is live on Microsoft Marketplace as a transactable offer: subscribe the same way you buy anything else in your Azure portal, on the same plans and prices as the table above.
View the listing →ClusterValidator is live on AWS Marketplace: subscribe from your AWS account, on the same plans and prices as the table above.
View the listing →Either route gets you the same software. ClusterValidator is self-hosted whichever way you buy it.
Every phase is a read. Nothing on your cluster is modified, so you can run it against production during business hours without a change window.
How it’s tested: every release is validated against a live Windows Server Failover Cluster — SQL Server FCI, shared storage, dynamic quorum — before it ships. If the real cluster doesn’t come back clean, the release doesn’t go out.
See a sample validation report — the tool’s own HTML output.
Your cluster data stays in your environment. ClusterValidator is self-hosted: it runs where your clusters run. Node names, configuration, and reports stay on your infrastructure — we never receive them. Licenses verify offline against a signed file, so the software never phones home. Everything it talks to is inside your network — your cluster nodes over WinRM and CIM, your domain controller over LDAP — and nothing leaves it. After install and activation, ClusterValidator requires no internet access to run. Our privacy policy says the same thing in writing, for the security review.
ClusterValidator validates SQL Server Failover Cluster Instances on Windows Server Failover Clustering, with SAN or VMware storage. It is Windows-only. It does not validate Kubernetes clusters or SQL Server Always On Availability Groups. It needs WinRM and CIM reachability to your cluster nodes, and the Failover Clustering feature installed. Windows Server 2016, 2019, and 2022.
DetentShell · MCPatrol · PesterForge · GitEasy · SqlCertForge · WikiMint · All products →
Several are available as MCP servers. Same idea: run them where your work already is.