ClusterValidator
NUGET · DETENTPOINT.CLUSTERVALIDATOR.MCP
Read-only health validation for Windows Server failover clusters running SQL Server FCI.
Available components
Last scanned (21 hours ago)
Scores higher than 55% of NuGet servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Build provenance not yet verified. View diagnostics → Unverified
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 781 tokens (~156/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.13.1 → 1.13.2 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed nuget/DetentPoint.ClusterValidator.Mcp@1.13.2
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | Pointman |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository type | git |
|---|---|
| Commit | 5f261d1aadbfe2e0d0b9096907f55ad112c7fcba |
| Project URL | https://detentpoint.com/clustervalidator |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_cluster_report ~54
Return the path to the HTML report for a run, if Test-Cluster produced one (it exists only when the TestCluster phase ran and succeeded). Returns null otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | The runId. |
No output schema declared.
No examples provided.
get_phase_findings ~102
Return the subset of a run's findings filtered by phase and/or category. Useful to drill into one phase (e.g. 'Storage') or one error category (e.g. 'StorageTopologyError').
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | Optional category filter (e.g. StorageTopologyError). |
| phase | string|null | – | Optional phase name filter (e.g. Storage, Quorum, Identity). |
| runId | string | yes | The runId. |
No output schema declared.
No examples provided.
get_phases ~82
List all 16 phases and their cost profile (which require an existing cluster, which are long-running, which is automatic) BEFORE starting a run. PreFlight is marked automatic=true — it always runs first and is not opt-in; the other 15 are the validation phases. TestCluster is the long-running phase. Informational only; no runId needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_validation_result ~154
Poll a validation run by runId. Returns status (Queued/Running/Completed/Failed), phasesCompleted/phasesTotal (phasesTotal is 16; phasesCompleted counts phases that have reported at least one finding and reaches 16 on completion — skipped phases still report a skip note), currentPhase, the findings accumulated so far (they stream during the run), and exitCode on completion (0=clean, 1=any Fail). Returns null if the runId is unknown or evicted (24h retention). Validation completes within 15 minutes under normal conditions; stop polling after 20 calls and treat as failed if still Running.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | The runId returned by run_cluster_validation. |
No output schema declared.
No examples provided.
run_cluster_validation ~389
Start a read-only SQL FCI failover-cluster health validation. Returns a runId IMMEDIATELY and runs asynchronously — validation is long-running (minutes); Test-Cluster is the long pole. Poll get_validation_result with the runId for streamed, phase-by-phase findings. The validator never changes cluster state.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedDiskCount | integer | – | Expected shared-disk count per node. 0 (default) reports the count without pass/fail; a positive value Fails any node whose shared-disk count differs. |
| nodes | array | yes | Cluster node names (2 to 16). |
| remotingDomain | string | – | Domain for remote CIM/AD credentials (e.g. sqlspnlab). Leave blank on a domain-joined management host. |
| remotingPassword | string | – | Password for remote CIM/AD credentials. Lab/test use only — passed over local stdio. |
| remotingUser | string | – | Username for remote CIM/AD credentials. Lab/test use only — passed over local stdio. |
| reportPath | string | – | Directory for the HTML/JSON/transcript report triad. Optional. |
| stage | string | – | Lifecycle hint: Auto (default), Cluster, or PreCluster. |
| strict | array|null | – | Strict areas to promote Warn->Fail: any of Mpio, Heartbeat, Hotfix, ServiceAccount, Affinity, Network, LunHygiene, Identity. |
| vCenterCredentialSecretName | string | – | Optional SecretManagement secret NAME holding read-only vCenter credentials (resolved locally via Get-Secret). Leave blank to connect with the tool's current identity. |
| vCenterServer | string | – | Optional vCenter/ESXi server FQDN to enable the VMware DRS anti-affinity phase (Phase 11). Leave blank to skip it. Requires VMware PowerCLI installed on this host. |
No output schema declared.
No examples provided.
How do I install the ClusterValidator MCP server?
ClusterValidator runs locally as a NuGet package, launched with dnx DetentPoint.ClusterValidator.Mcp@1.13.2 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · DetentPoint.ClusterValidator.Mcp
claude mcp add com-detentpoint-cluster-validator -- dnx DetentPoint.ClusterValidator.Mcp@1.13.2 --yes
What is the ClusterValidator MCP server?
ClusterValidator is an MCP server listed in the public MCP registry as com.detentpoint/cluster-validator. Read-only health validation for Windows Server failover clusters running SQL Server FCI. This page covers its NuGet package (DetentPoint.ClusterValidator.Mcp).
Is the ClusterValidator MCP server safe to use?
ClusterValidator scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ClusterValidator MCP server expose?
ClusterValidator exposes 5 tools: run_cluster_validation, get_phases, export_cluster_report, get_validation_result, get_phase_findings. Their descriptions and schemas cost roughly 781 tokens of context every time the server is loaded.
Is the ClusterValidator MCP server still maintained?
ClusterValidator is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.