Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ESXi Read-Only Diagnostics

PYPI · ESXI-READONLY-MCP

Read-only VMware ESXi diagnostics: CPU Ready, disk latency, snapshots, real space, hardware health.

Available components

−18 this week 64 Trust /100

Last scanned (4 hours ago)

Scores higher than 60% of PyPI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 43 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 904 tokens (~69/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Changelog

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.

  • 5 Nov 26 −18
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.77 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 20 Oct 26 +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.

  • 18 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 5 Nov 2026 · Analysed pypi/esxi-readonly-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 43 packages
Packages resolved 43
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~863 tokens

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 →

Tool Tokens
config_host ~75

Configuracion del host: licencia (clave enmascarada) y vencimiento, NTP y desfase del reloj, SSH/Shell, servicios activos, perfil de imagen y VIBs/drivers de terceros, syslog, placas de red (velocidad de enlace), vSwitches, portgroups y VMkernel.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

datastores ~40

Datastores: capacidad, usado, libre, % de uso, % provisionado (thin), disco fisico donde esta cada uno y VMs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

diagnostico_completo ~62

Ejecuta todo junto: permisos, host, salud de hardware, configuracion, datastores, VMs, snapshots, performance realtime, eventos (warning/error 7 dias), top archivos y overcommit.

NameTypeReqDescription
dias_alerta_snapshotinteger––

No output schema declared.

No examples provided.

eventos ~93

Eventos de ESXi (errores de disco, reinicios de VMs, alarmas, tareas, logins fallidos). nivel: todos | warning (warning y error) | error. Fechas corregidas por el desfase del reloj de ESXi.

NameTypeReqDescription
diasinteger––
incluir_sesionesboolean––
max_eventosinteger––
nivelstring––

No output schema declared.

No examples provided.

historial_perf ~97

Resumen de las metricas guardadas localmente por 'server.py --collect' (semanas de historia, aunque ESXi solo guarde 1 h). Filtra por horario laboral (lunes a viernes, hora local).

NameTypeReqDescription
diasinteger––
entidad–––
hora_fininteger––
hora_iniciointeger––
solo_horario_laboralboolean––

No output schema declared.

No examples provided.

host_info ~46

Host: fabricante, modelo, CPU (cores/hilos/HT), RAM total y usada, version y build de ESXi, uptime, politica de energia y controladoras de storage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

overcommit ~33

Suma de vCPU vs cores/hilos fisicos y RAM asignada vs fisica (ratios de overcommit).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

performance ~176

Metricas de host y VMs: CPU uso, CPU Ready %, Co-Stop %, memoria activa/ballooning/swap, latencia de disco (total, por disco virtual y por datastore) e IOPS. Devuelve promedio, p95 y maximo con su momento. intervalo: realtime (20 s, ~1 h en ESXi standalone), dia, semana, mes, anio (estos requieren vCenter). max_muestras: 180 = 1 h en realtime. dias: rango hacia atras (alternativa a max_muestras).

NameTypeReqDescription
dias–––
hora_fininteger––
hora_iniciointeger––
intervalostring––
max_muestrasinteger––
solo_horario_laboralboolean––
vm–––

No output schema declared.

No examples provided.

salud_hardware ~53

Salud del hardware segun ESXi: estado de la RAID y discos fisicos (PERC), sensores de temperatura, ventiladores, fuentes, memoria y CPU. Lista primero los elementos que no estan en verde.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

snapshots ~41

Todos los snapshots con fecha, antiguedad, tamano aproximado y marca de los que superan dias_alerta.

NameTypeReqDescription
dias_alertainteger––

No output schema declared.

No examples provided.

top_archivos ~50

Archivos mas grandes de cada datastore (o de uno), con la VM a la que pertenecen y marca de posibles huerfanos.

NameTypeReqDescription
datastore–––
topinteger––

No output schema declared.

No examples provided.

verificar_permisos ~30

Muestra con que usuario se conecta y si ese usuario tiene privilegios de escritura en ESXi.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vms ~67

Todas las VMs: estado, vCPU, RAM asignada/activa/consumida, ballooning, swap, reservas/limites, VMware Tools, discos (provisionado vs usado, thin/thick, datastore, controladora) y espacio libre dentro del guest.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ESXi Read-Only Diagnostics MCP server?

ESXi Read-Only Diagnostics runs locally as a PyPI package, launched with uvx esxi-readonly-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · esxi-readonly-mcp

# add to Claude Code
claude mcp add nicolasboattini-esxi-readonly-mcp -- uvx esxi-readonly-mcp
Common questions

What is the ESXi Read-Only Diagnostics MCP server?

ESXi Read-Only Diagnostics is an MCP server listed in the public MCP registry as io.github.nicolasboattini/esxi-readonly-mcp. Read-only VMware ESXi diagnostics: CPU Ready, disk latency, snapshots, real space, hardware health. This page covers its PyPI package (esxi-readonly-mcp).

Is the ESXi Read-Only Diagnostics MCP server safe to use?

ESXi Read-Only Diagnostics scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 ESXi Read-Only Diagnostics MCP server expose?

ESXi Read-Only Diagnostics exposes 13 tools: verificar_permisos, host_info, datastores, vms, snapshots, and 8 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

Is the ESXi Read-Only Diagnostics MCP server still maintained?

ESXi Read-Only Diagnostics is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ESXi Read-Only Diagnostics MCP server under?

ESXi Read-Only Diagnostics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.