rustproxmoxmcpCAUTION
One Rust MCP server for many Proxmox VE clusters — a mechub project
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
rustproxmoxmcp
One Rust MCP server for many Proxmox VE clusters a mechub project — sovereign network-security automation
Unofficial / community project. This is an independent community project and does not claim affiliation with or endorsement by Proxmox Server Solutions GmbH. Product names and trademarks are used only to identify the systems with which the software interoperates.
Status: 0.11.0 — the tool surface is complete but for one gap
50 callable tools: 31 read, 18 low, and apply_proxmox_change_set as the single destructive entry point. Seven further names --- delete_vm, delete_container, delete_snapshot, delete_backup, delete_iso, restore_backup, rollback_snapshot --- are authorization scopes, not tools: a token grants them by name and reaches them through plan_proxmox_destroy. KNOWN_TOOLS therefore holds 57 entries.
What is still missing
- `execute_vm_command`. Deliberate. The design spec makes it conditional on
mecmcp-policy compiling an allow/deny rule set over the command subject, and that is not wired. Arbitrary command execution inside every guest is remote code execution as a tool call; it ships with a policy engine or not at all.
The remaining gap is tracked in #57. Everything else the third-party proxmox-mcp offers has an equivalent here --- see docs/MIGRATING-FROM-PROXMOX-MCP.md, which also lists the arguments that changed shape.
Change control
Destructive work goes through plan → approve → apply. The plan renders a server-generated preview and records the action; the approval binds the plan digest over (owner, device, expected fingerprint, actions); the apply re-checks the guest's
3ded086c32c5OBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add rustproxmoxmcp:0.11.1 -- docker run -i --rm ghcr.io/mechubsec/rustproxmoxmcp:0.11.1:None stdio /var/lib/proxmoxmcp/changeset-state.json
Trust audit
CAUTIONgrade B · trust 83/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (6 observation(s))
- Network
- declared (4 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- found
Findings (14)
"endpoint": "https://127.0.0.1:8006",
vec!["http://0.0.0.0".to_owned()],
cli.common.otel_endpoint = Some("http://127.0.0.1:4318".to_owned());endpoint: "https://127.0.0.1:1".to_owned(),
const PEM_PRIVATE_KEY_BLOCK: &str = "-----BEGIN RSA PRIVATE KEY-----\nFAKEbase64PemBodyNotARealKey1234567890abcdef\n-----END RSA PRIVATE KEY-----"; // gitleaks:allow -- fabricated PEM fixture, not a r
.gitleaks-vendor.toml
.gitleaks.toml
.gitleaksignore
&[("node", "pve2/../../access/users")],&[("node", "pve2/../../cluster"), ("vmid", "905")],for bad in ["", "local:../../etc/passwd", "no-colon/path"] {"endpoint": "https://198.51.100.10:8006",
git commit -m "feat(core): cluster inventory with hardened load and separated credentials"
Gates applied: no_behavioural_pass.
3ded086c32c5full audit observations/trust-audit/mcp-server/mechubsec__rustproxmoxmcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 3ded086c32c5 | CAUTION | B | 83 | first audit |
Questions
What is the rustproxmoxmcp MCP server?
One Rust MCP server for many Proxmox VE clusters — a mechub project
Is rustproxmoxmcp safe to connect to an agent?
With care. The audit graded it B (83/100) and found 14 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does rustproxmoxmcp need?
No credential environment variables were found in its source, so it appears to need none.
How does rustproxmoxmcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts.
How current is this page?
The grade is for one exact copy of the source (3ded086c32c5), read on 2026-10-11. The repository is watched and re-audited when it changes.