Skills/PyPI/vibops-mcp

vibops-mcp@0.72.5

VERIFIED· not started

Publisher claims: "VibOps MCP server — control your GPU infrastructure from any MCP-compatible client" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher vibopsai · publishing for 215 daysInstalls 6,006Last detonated 40 min ago
$claude mcp add vibops-mcp -- uvx vibops-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
VIBOPS_TOKENConfiguration, not credentials: VIBOPS_URL
Where it talks to
no vendor host named in the codeAlso acme.com, corp.local — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names acme.com, corp.local as well as its own vendor. The guard injects VIBOPS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx vibops-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.67.0

vet-skills diff vibops-mcp 0.67.0 0.72.5

This version reaches for something 0.67.0 did not: 2 new hosts (acme.com, corp.local) · 1 new credential variable (VIBOPS_TOKEN). Compared from the two recorded runs, not from source.

New hosts
acme.com, corp.local
New credential variables
VIBOPS_TOKEN

0.67.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Collects environment variables by secret-like namestests/test_client.py:38 · Collects environment variables by secret-like namesenv = {k: v for k, v in os.environ.items() if k != "VIBOPS_TOKEN"}Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
HIGH
Access to sensitive file pathsvibops_mcp/tools/actions.py:460 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesr"/etc/passwd|/etc/shadow|chmod\s+[0-7]*777)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈56 tok
1 file · 30 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.