io.github.vmware-skills/vmware-privateai
VMware Private AI (GPU & Model Serving)
VMware Private AI (NVIDIA): GPU inventory, vGPU profiles, utilization, model serving — 18 tools
alive probed 2026-10-19
18tools
≈ 4.7ktokens, estimate
≈ 2.4 %of Claude's 200k window
3.3×the median server
4.0 sto initialize
11 msto list tools
- Run it
- uvx vmware-privateai==2.4.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- vmware-privateai 2.4.2
- Capabilities
- experimental, prompts, resources, tools
- Instructions
- 1 012 characters
- Of a 1M window
- ≈ 0.5 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/vmware-skills/VMware-PrivateAI
- Registry
- active, updated 2026-10-19 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| advise_pais_sizing | 366 | 8 % |
| assign_vgpu | 359 | 8 % |
| get_access_info | 324 | 7 % |
| list_vgpu_profiles | 312 | 7 % |
| check_gpu_host_readiness | 298 | 6 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.