← Case index
Case file No.076 · pypi · stdio
VMware Monitor
io.github.vmware-skills/vmware-monitor · v2.4.2
Read-only VMware vCenter/ESXi monitoring, 33 MCP tools; vSphere calls allowlist-gated in tests.
Security score
96/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- v2.4.1 → v2.4.2Oct 19, 2026
versionchanged version bump"2.4.1" → "2.4.2"
packages.0.versionchanged package version bump"2.4.1" → "2.4.2"
- v2.4.0 → v2.4.1Oct 18, 2026
versionchanged version bump"2.4.0" → "2.4.1"
packages.0.versionchanged package version bump"2.4.0" → "2.4.1"
- First snapshot (v2.4.0)Oct 16, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs VMware Monitor safe?
MCPWatch gives VMware Monitor a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does VMware Monitor have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package vmware-monitor. That is not proof of safety.
When was VMware Monitor last updated?
The latest registry version is 2.4.2, published Oct 19, 2026. The last push to vmware-skills/VMware-Monitor was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.
What license does VMware Monitor use?
GitHub reports the license of vmware-skills/VMware-Monitor as MIT.