vmware-harden
A read-only VMware compliance scanning toolkit: discover baselines, scan vCenter targets, and report violations, drift, coverage gaps and advisory remediation from a local twin database.
Discover compliance baselines (CIS ESXi 8.0, vSphere SCG, PCI-DSS 4.0, DengBao 2.0, EU NIS2, BSI ITGS, plus user-imported YAML) with
list_baselines, and preview their rules withget_baseline_rules.Run read-only compliance scans of a configured vCenter target against a chosen baseline with
scan_target, persisting a snapshot, violations and drift events locally.Review findings with
list_violations, including severity filtering, paging, and coverage metadata that flags undetermined rules so empty results are not mistaken for compliance.Track configuration changes between scans with
list_drift_events(requires at least two scans of the same target).Fetch persisted, LLM-generated remediation suggestions (advisory only, never executed) for a violation via
get_remediation.Inspect the built-in vSphere/VCF 9 STIG-aligned controls with
list_stig_controls, and learn how STIG content is synced (and why no compliance API exists) viadescribe_stig_content_sync.Every tool is marked read-only: no infrastructure modifications, no remote remediation, only local YAML/DuckDB reads plus read-only vCenter inventory calls during
scan_target.
Enforces compliance baselines on VMware vSphere environments, including ESXi hosts and NSX DFW rules, with built-in baselines such as CIS, PCI-DSS, and 等保 2.0.
VMware-Harden
Turn VMware compliance checks into findings with visible coverage gaps.
English · 简体中文
Community-maintained · MIT · Not an official VMware/Broadcom product.

Synthetic-data GIF; video includes redacted historical screenshots. Download the AI-narrated family introduction (~3 min)
Why use it?
Scan supported baselines and vulnerability/build evidence.
Track configuration drift in a local Twin.
Separate remediation suggestions from remote execution.
Related MCP server: VMware-Monitor
Get started
Install the published CLI and inspect its commands:
uv tool install "vmware-harden[collectors]==1.20.1"
vmware-harden --helpRequires uv and Python >=3.10. Configure targets and credentials locally before remote queries. Setup guide.
One-click installs, after local setup: Claude Desktop extension (.mcpb) · Install in VS Code. Both run the same pinned 1.20.1 server.
For agent-host installation, use the setup guide and Cursor, Codex, Gemini CLI, Cline and local-model examples.
Choose a model with the shared model-fit workflow: compare the same tasks, review quality and safety, then select the smallest tested passing configuration per task group; this is not a production guarantee.
Know the boundaries
Incomplete or unknown checks are not passes. Optional AI remediation advice can send findings to an external provider; review that data flow. Remote remediation is separate.
Go deeper
Part of VMware Skills: 15 skills, 14 MCP servers and one shared Policy library. If it helps your work, star the family portal.
MCP result contract
Offset-capable listings expose next_offset; stop when it is null rather than looping on truncated. Failed calls provide structuredContent.vmware_error through Policy 1.26.0. Existing text, legacy flags, success values and confirmation checks remain unchanged. See the contract.
Available Tools
8 toolsdescribe_stig_content_syncARead-onlyIdempotent
[READ] Explain harden's vSphere STIG integration and route continuous enforcement. Takes no parameters. Returns {compliance_api_available (always false — VCF Operations ACC/SPM exposes no public compliance REST API), why_no_api, content_sources (the open-source MITRE InSpec/Cinc STIG repos harden syncs against), mechanism (how upstream controls become harden rules), routing_note (use VCF Operations SPM/ACC UI for fleet-wide continuous enforcement; harden is the API-scriptable point-in-time scanner), importer_status}. Read-only, local static content — no database, network, or API call. Call this before assuming a compliance endpoint exists; use list_stig_controls to see the actual controls.
Inputs: no named parameters.
get_baseline_rulesARead-onlyIdempotent
[READ] Return every rule in one compliance baseline. Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {id, title, severity, category}, where severity is one of 'critical', 'high', 'medium', 'low', 'info'. The whole baseline is returned, so truncated is always false and total is the exact rule count. Read-only — parses local baseline YAML only, no database or network access. Use after list_baselines to preview what scan_target will check; use list_violations for actual scan findings.
Inputs: baseline_id (required).
get_remediationARead-onlyIdempotent
[READ] Fetch the persisted LLM-generated remediation Suggestion for one violation. Returns {summary, execution_plan.steps, impact_prediction (workload impact, maintenance window, rollback plan), confidence (0.0-1.0), human_review_required}, or None when no advisor suggestion has been generated for that violation yet (generate one via the vmware-harden CLI advisor). Read-only lookup in the local twin DB (~/.vmware-harden/twin.duckdb); no network calls and nothing is executed — suggestions are advisory only.
Inputs: violation_id (required). Returns: result
list_baselinesARead-onlyIdempotent
[READ] List all available compliance baselines: built-in (CIS ESXi 8.0, vSphere SCG v8, PCI-DSS 4.0, DengBao 2.0 L3, EU NIS2, BSI ITGS) plus any user-imported YAML baselines from ~/.vmware-harden/baselines/. Takes no parameters. Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {id, name, version, applies_to (node types covered), rule_count}, and entries that fail to load carry an 'error' field instead. Every baseline is listed, so truncated is always false and total is exact — this is the complete set, not a page of it. Read-only — parses local baseline YAML only, no database or network access. Start here to discover valid baseline ids for get_baseline_rules and scan_target.
Inputs: no named parameters.
list_drift_eventsARead-onlyIdempotent
[READ] List configuration drift events from the most recent scan snapshot — fields whose values changed since the prior scan of the same target. Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {node_id, field, old_value, new_value, detected_at}. total is the snapshot's exact change-event count, so truncated tells you definitively whether rows were left behind — raise limit when it is true. Returns an empty envelope (total 0) when no snapshot exists or there was no prior snapshot to diff against (a target must be scanned at least twice). Read-only query of the local twin DB (~/.vmware-harden/twin.duckdb); no network calls. Use for change tracking; use list_violations for compliance failures.
Inputs: limit.
list_stig_controlsARead-onlyIdempotent
[READ] List the built-in vSphere 9 / VCF 9 STIG-aligned host baseline's controls (baseline id 'vsphere-stig-v9-subset'). Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {id, title, severity (one of critical/high/medium/low/info), category, advanced_setting} where advanced_setting names the ESXi advanced setting the control governs (e.g. 'Security.AccountLockFailures'). total is the exact catalog size, so truncated tells you definitively whether to raise offset. Read-only — parses local baseline YAML only, no database, network, or compliance API (VCF Operations ACC/SPM has none). Use scan_target with baseline 'vsphere-stig-v9-subset' to evaluate these controls against a target; use describe_stig_content_sync for how this catalog is kept in sync.
Inputs: limit, offset.
list_violationsARead-onlyIdempotent
[READ] List compliance violations recorded by the most recent scan
snapshot in the local twin DB (~/.vmware-harden/twin.duckdb).
Returns an envelope {violations: [...], total, limit, offset,
has_more, coverage, note}; each violation is {id, rule_id, node_id,
severity, baseline_id, evidence}, sorted severity-descending then rule_id.
total is the full matching count (unbounded by limit) so nothing is
hidden — page by raising offset while has_more is true. AN EMPTY LIST IS
NOT A COMPLIANCE VERDICT: rules whose data no collector gathers are not
executed and count as undetermined, never as passing. Read coverage
{evaluated, undetermined, total, tracked, complete, undetermined_rules}
before summarising — when complete is false, say how many rules were
evaluated out of how many and do not call the estate compliant or clean;
when tracked is false the snapshot predates coverage tracking, so re-scan
rather than assume. note states the same in one sentence, or null when
coverage is complete. Empty envelope (total 0) when no scan exists — run
scan_target first. Read-only local DB query, no network calls. Pass a
row's 'id' to get_remediation for a fix plan.
Inputs: limit, offset, severity.
scan_targetARead-onlyIdempotent
[READ] Run a compliance scan of a vCenter target against a baseline and
persist results locally. Makes read-only vCenter API calls (inventory collection only — never modifies
VMware infrastructure) and writes a new snapshot, violations, and drift
events (vs the prior scan of the same target) to the local twin DB
(~/.vmware-harden/twin.duckdb). Returns summary counts {snapshot_id,
target, baseline, hosts, violations, coverage, note}; inspect details via
list_violations and list_drift_events. violations is meaningful only
together with coverage: rules whose data no collector gathers are not
executed and count as undetermined, never as passing, so violations=0 is
not by itself evidence of compliance. When coverage.complete is false,
report how many rules were evaluated out of how many instead of calling
the estate compliant. May take minutes on large inventories.
Inputs: target (required), baseline.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: baselines, rules, scans, violations, drift, remediation, and STIG sync are separate concerns. The main ambiguity is between get_baseline_rules and list_stig_controls, since both can return rule/control lists for baselines, though the STIG-specific tool adds advanced_setting detail.
The naming pattern is mostly verb_noun and readable, with list_* for collections and get_* for specific lookups. Minor inconsistency exists between list_baselines and get_baseline_rules, plus scan_target and describe_stig_content_sync break the simple list/get prefix pattern, but the style is consistent enough to predict behavior.
Eight tools is well-scoped for a compliance scanning and remediation advisory server. Each tool covers a distinct part of the workflow from baseline discovery, rule preview, scanning, violation review, drift tracking, and remediation lookup without feeling padded or redundant.
The core lifecycle is covered: discover baselines, inspect rules, scan a target, list violations, inspect drift, and fetch remediation. Minor gaps exist—there is no tool to manage scan history, list targets, or generate remediation suggestions directly—but agents can work around these via the CLI or by treating this as a read-only reporting surface.
Maintenance
Related MCP Connectors
Compliance frameworks (SOC 2, ISO 27001, CMMC, NIST, more) delivered to AI agents as MCP tools.
Infrastructure context for any AI: VMware, Nutanix, Kubernetes and cloud. Read-only, off production.
Manage compliance controls, policies, and audit readiness for SOC 2, HIPAA, ISO 27001 and more.
CTEM for your Trusteed tenant: security summary, findings, compliance gaps, and scans via OAuth.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables secure management of VMware vCenter 8.0+ environments through controlled operations including VM lifecycle management, snapshots, and resource discovery with built-in RBAC authorization, audit logging, and rate limiting.6MIT
- AlicenseAqualityBmaintenanceRead-only VMware vCenter/ESXi monitoring. 8 MCP tools for VM inventory, host status, datastore capacity, cluster info, alarms, events, and VM details. Code-level enforced safety — no destructive operations exist in the codebase. Supports vSphere 6.5–8.0. Works with local models via Ollama/LM Studio.33506 PyPI20MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to perform automated compliance scanning of AWS infrastructure against PCI-DSS, CIS, and Well-Architected frameworks. It provides tools for scanning, remediation, and audit report generation.MIT
- FlicenseNot gradedqualityCmaintenanceEnables management of VMware vSphere/ESXi vCenters and standalone hosts across multiple named environments, covering read-only inventory introspection plus policy-gated destructive operations like VM deletion, snapshots, and power actions. Adds a guardrail layer with declarative policy, two-phase confirmation tokens, append-only audit logging, and optional human-in-the-loop web approval.-