# com.detentpoint/cluster-validator (nuget · DetentPoint.ClusterValidator.Mcp)

Read-only health validation for Windows Server failover clusters running SQL Server FCI.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- nuget · `DetentPoint.ClusterValidator.Mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp.md), [page](https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp)

## Channel facts

- Registry: `nuget`
- Package: `DetentPoint.ClusterValidator.Mcp`
- Version: `1.13.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 24 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.detentpoint/cluster-validator MCP server?

com.detentpoint/cluster-validator runs locally as a NuGet package, launched with dnx DetentPoint.ClusterValidator.Mcp@1.13.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-detentpoint-cluster-validator -- dnx DetentPoint.ClusterValidator.Mcp@1.13.1 --yes
```

### Cursor

```json
{
  "mcpServers": {
    "com-detentpoint-cluster-validator": {
      "command": "dnx",
      "args": [
        "DetentPoint.ClusterValidator.Mcp@1.13.1",
        "--yes"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-detentpoint-cluster-validator": {
      "command": "dnx",
      "args": [
        "DetentPoint.ClusterValidator.Mcp@1.13.1",
        "--yes"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-detentpoint-cluster-validator -- dnx DetentPoint.ClusterValidator.Mcp@1.13.1 --yes
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-detentpoint-cluster-validator": {
      "type": "local",
      "command": [
        "dnx",
        "DetentPoint.ClusterValidator.Mcp@1.13.1",
        "--yes"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  com-detentpoint-cluster-validator:
    command: "dnx"
    args: ["DetentPoint.ClusterValidator.Mcp@1.13.1", "--yes"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-detentpoint-cluster-validator": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "DetentPoint.ClusterValidator.Mcp@1.13.1",
        "--yes"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "com-detentpoint-cluster-validator": {
      "command": "dnx",
      "args": [
        "DetentPoint.ClusterValidator.Mcp@1.13.1",
        "--yes"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `run_cluster_validation` (~389 tokens)

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.

Input parameters:

- `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, required): 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.

### `get_phases` (~82 tokens)

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.

### `export_cluster_report` (~54 tokens)

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.

Input parameters:

- `runId` (string, required): The runId.

### `get_validation_result` (~154 tokens)

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.

Input parameters:

- `runId` (string, required): The runId returned by run_cluster_validation.

### `get_phase_findings` (~102 tokens)

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').

Input parameters:

- `category` (string|null): Optional category filter (e.g. StorageTopologyError).
- `phase` (string|null): Optional phase name filter (e.g. Storage, Quorum, Identity).
- `runId` (string, required): The runId.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 66
- 2026-09-02: 62
- 2026-09-01: 62
- 2026-08-31: 62
- 2026-08-30: 62
- 2026-08-29: 62
- 2026-08-28: 62
- 2026-08-27: 62
- 2026-08-26: 47

## Common questions

### What is the com.detentpoint/cluster-validator MCP server?

com.detentpoint/cluster-validator 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 com.detentpoint/cluster-validator MCP server safe to use?

com.detentpoint/cluster-validator scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 com.detentpoint/cluster-validator MCP server expose?

com.detentpoint/cluster-validator 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 com.detentpoint/cluster-validator MCP server still maintained?

com.detentpoint/cluster-validator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- NuGet package: https://www.nuget.org/packages/DetentPoint.ClusterValidator.Mcp
- Socket report: https://socket.dev/nuget/package/DetentPoint.ClusterValidator.Mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-detentpoint-cluster-validator/detentpoint-clustervalidator-mcp