MCP.Market

Vllm Ops MCP server

by jaimenbell·io.github.jaimenbell/vllm-ops-mcp·v0.1.0
No reviews yet

Read-only ops/health MCP server for a local vLLM instance: health tiers, GPU/VRAM, service status.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars15 downloads/wk

Reviews

Write one

Nobody has reviewed Vllm Ops yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vllm Ops tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_health
  • get_gpu_status
  • get_serve_config
  • get_service_status
  • list_models

    GET /v1/models passthrough -- lists model IDs currently loaded/served.

  • test_completion

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 43 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vllm Ops compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,273 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
15
more than 4% of 11,915 servers with a package

What its tools let an agent do: 6 read

Install Vllm Ops in Claude Code, Cursor or VS Code

claude mcp add vllm-ops-mcp -- uvx vllm-ops-mcp
Add to Cursor

What the publisher says

From the Vllm Ops repository's README, as published. We do not edit it. Read it on GitHub

vllm-ops-mcp

Read-only ops/health MCP server for a local, WSL2/systemd-managed vLLM server -- liveness vs. real-completion health tiers, GPU/VRAM status, systemd service status, and live serve-flag introspection. Built to the same standard as mcp-factory and desktop-mcp, and other local tooling in this operator's portfolio: own pyproject, own fastmcp server, honest README, real test suite, no product code before a spec was confirmed.

This is not a container-lifecycle manager. It assumes vLLM already runs as a bare-metal systemd unit inside WSL2 (this operator's actual setup -- see vllm-autostart), not inside Docker/Podman.

Quickstart

// ~/.claude.json (or any MCP-host stdio client config)
{
  "mcpServers": {
    "vllm-ops-mcp": {
      "type": "stdio",
      "command": "C:\\Users\\<you>\\projects\\vllm-ops-mcp\\.venv\\Scripts\\python.exe",
      "args": ["C:\\Users\\<you>\\projects\\vllm-ops-mcp\\run_server.py"]
    }
  }
}

Tools (Phase 1 -- all read-only, no gating required beyond a throughput cap)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vllm Ops: common questions

Is Vllm Ops MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Vllm Ops safety report
How do I install Vllm Ops?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vllm Ops need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vllm Ops maintained?
The last commit was 82 days ago (2026-08-12). The latest release is v0.1.0.
How does Vllm Ops compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,273 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from jaimenbell →