io.github.jaimenbell/vllm-ops-mcp
PYPI · VLLM-OPS-MCP
Read-only ops/health MCP server for a local vLLM instance: health tiers, GPU/VRAM, service status.
Available components
Last scanned (23 hours ago)
Scores higher than 74% of PyPI servers
Category Monitoring and Observability
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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects fastmcp 3.4.2, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 102 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 523 tokens (~87/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 25 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 −3
- GHSA-7xgj-8392-5q4r affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 22 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
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 4 Nov 2026 · Analysed pypi/vllm-ops-mcp@0.1.0
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 | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7xgj-8392-5q4r | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 14 packages
| Packages resolved | 14 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_health ~121
Two-stage health probe for the local vLLM server, mirroring check-vllm.cmd. deep=False (default): GET /v1/models liveness check only. deep=True: additionally fires one minimal real /v1/chat/completions call to confirm the server actually generates text, not just reports a model loaded (rate-limited -- this consumes real GPU inference cycles on shared infra). Returns {ok, status: up|degraded|down, tier, model_id, latency_ms, completion_s, error}.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_gpu_status ~44
nvidia-smi wrapper: per-GPU VRAM used/total and utilization%, plus per-process VRAM usage (to catch VRAM-overshoot). Read-only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_serve_config ~114
Read-only introspection of the current vLLM launch flags. Prefers the LIVE process's real argv (/proc/<pid>/cmdline of the systemd unit's MainPID) as ground truth; falls back to the static exec script if the process isn't currently up. vLLM does not expose its own launch flags over the API, so this never queries the server itself. Any argv value following a flag matching a known-sensitive pattern (token/key/secret/password/credential) is redacted before being returned.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_service_status ~77
systemd unit status for the vLLM service (via `wsl -d <distro> -- systemctl show`, or native systemctl if this server runs inside WSL2/Linux). Returns load/active/sub state, restart count, main PID, and last-active timestamp. Read-only -- never starts/stops the unit.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_models ~25
GET /v1/models passthrough -- lists model IDs currently loaded/served.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_completion ~142
On-demand real /v1/chat/completions call with a caller-supplied prompt, for manual sanity-checking (same mechanism as check_health(deep=True) but user-controlled). Rate-limited -- consumes real GPU inference cycles on shared infra. max_tokens is clamped server-side to config.MAX_TEST_COMPLETION_TOKENS and the prompt is capped at config.MAX_TEST_COMPLETION_PROMPT_CHARS (oversized prompts are rejected) -- the rate limiter bounds call frequency, not the cost of a single call. Returns {ok, model_id, completion_s, text, error}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | – |
| prompt | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.jaimenbell/vllm-ops-mcp server?
io.github.jaimenbell/vllm-ops-mcp runs locally as a PyPI package, launched with uvx vllm-ops-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 · vllm-ops-mcp
claude mcp add jaimenbell-vllm-ops-mcp -- uvx vllm-ops-mcp
What is the io.github.jaimenbell/vllm-ops-mcp server?
io.github.jaimenbell/vllm-ops-mcp is listed in the public MCP registry as io.github.jaimenbell/vllm-ops-mcp. Read-only ops/health MCP server for a local vLLM instance: health tiers, GPU/VRAM, service status. This page covers its PyPI package (vllm-ops-mcp).
Is the io.github.jaimenbell/vllm-ops-mcp server safe to use?
io.github.jaimenbell/vllm-ops-mcp scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 io.github.jaimenbell/vllm-ops-mcp server expose?
io.github.jaimenbell/vllm-ops-mcp exposes 6 tools: check_health, list_models, test_completion, get_gpu_status, get_service_status, get_serve_config. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Is the io.github.jaimenbell/vllm-ops-mcp server still maintained?
io.github.jaimenbell/vllm-ops-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.