pbs-mcp@0.3.0
VERIFIED· not startedPublisher claims: "MCP server for Proxmox Backup Server (datastore, snapshot, GC, verify, prune)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
PBS_TOKEN_IDPBS_TOKEN_SECRETConfiguration, not credentials: PBS_ALLOW_WRITE, PBS_CA_BUNDLE, PBS_DEFAULT_DATASTORE, PBS_HOST, PBS_HTTP_TIMEOUT, PBS_NODE, PBS_VERIFY_TLS- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- 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. It asks for PBS_TOKEN_ID, PBS_TOKEN_SECRET and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
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-14 and scored it 86/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 deviationsStatic findings
# Load .env from the package's parent directory at import time.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Configuration: load .env once, expose typed accessors.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Configuration is loaded from environment variables (typically via .env):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose._ENV_PATH = Path(__file__).resolve().parent.parent / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"Copy .env.example to .env and fill in values."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Minimal .env loader — no python-dotenv dependency."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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
No advisories in OSV for pbs-mcp@0.3.0 as of 34 min ago. This is the package itself, not its dependencies.