Proxmox VE (Mojood Connect)
PYPI · MOJOOD-PROXMOX-MCP
Proxmox VE in Claude: VMs, storage, backups; start, stop, snapshot after a yes.
Available components
Last scanned (5 hours ago)
Scores higher than 80% of PyPI servers
Category Cloud Infrastructure
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to askmojood/proxmox-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 693 tokens (~115/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 65
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/mojood-proxmox-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | askmojood/proxmox-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/askmojood/proxmox-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3647268110 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:454edefd71e045a6fe223d3635a327af17936f6ab57c1df17d9bd2ecf5c1c083 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 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 →
find_guests Find guests ~88
VMs and containers with status, tags, CPU and memory in use now, and uptime.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | VMs, LXC containers or both |
| query | – | – | part of a name, or an id, e.g. "erp" |
| status | string | – | filter by state |
| tag | – | – | a Proxmox tag, e.g. "prod" |
| Name | Type | Req | Description |
|---|---|---|---|
| guests | array | yes | – |
| total | integer | yes | – |
No examples provided.
guest_details A guest in detail ~76
One guest: status and use, cores and disks, notes, its snapshots, its last backup and whether a backup job covers it, and its recent tasks from Proxmox's task log (who did what, when).
| Name | Type | Req | Description |
|---|---|---|---|
| guest | string | yes | a name or id, e.g. "erp-db" or "101" |
| Name | Type | Req | Description |
|---|---|---|---|
| cores | – | – | – |
| disks | array | – | – |
| guest | – | – | – |
| in_backup_job | – | – | – |
| last_backup | – | – | – |
| notes | – | – | – |
| problem | – | – | – |
| recent_tasks | array | – | newest first, from Proxmox's task log |
| snapshots | array | – | – |
| starts_at_boot | – | – | – |
No examples provided.
needs_attention What needs attention ~56
Guests no backup job covers, overdue backups, production guests that are stopped, old snapshots, storage filling up, and guests short of memory.
| Name | Type | Req | Description |
|---|---|---|---|
| backup_days | integer | – | a backup older than this many days counts as overdue |
| Name | Type | Req | Description |
|---|---|---|---|
| backups_overdue | array | yes | in a backup job, but no backup newer than the limit |
| memory_high | array | yes | – |
| not_in_any_backup_job | array | yes | guests no backup job covers |
| old_snapshots | array | yes | – |
| production_stopped | array | yes | tagged "prod" and not running |
| storage_filling | array | yes | – |
No examples provided.
overview Overview ~31
Nodes (CPU, memory, uptime), storage use, how many guests run or are stopped, and the backup jobs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| backup_jobs | array | yes | – |
| containers | integer | yes | – |
| nodes | array | yes | – |
| running | integer | yes | – |
| stopped | integer | yes | – |
| storage | array | yes | – |
| vms | integer | yes | – |
No examples provided.
power_guest Start, shut down or reboot a guest ~106
Start, cleanly shut down, or reboot a VM or container. The first call changes nothing and returns a summary and a confirmation code; it happens only on a second call with the code, after the user has said yes.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | shutdown and reboot go through the guest OS |
| confirmation | – | – | leave empty first; pass the code only after the user confirms |
| guest | string | yes | a name or id, e.g. "mail-relay" |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | – | – | when done is false: the code to pass back, only after the user says yes |
| done | boolean | yes | false: nothing has changed yet; true: Proxmox has done it |
| expires_in_minutes | – | – | – |
| guest | – | – | – |
| problem | – | – | why it can't be done; nothing was changed |
| summary | string | yes | – |
No examples provided.
snapshot_guest Take a snapshot ~128
Take a snapshot of a VM or container (it keeps running). The first call changes nothing and returns a summary and a confirmation code; the snapshot is taken only on a second call with the code, after the user has said yes.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | – | – | leave empty first; pass the code only after the user confirms |
| description | – | – | why, in a few words |
| guest | string | yes | a name or id, e.g. "erp-db" |
| name | string | yes | letters, digits, "-" or "_", starting with a letter, e.g. "before-update" |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | – | – | when done is false: the code to pass back, only after the user says yes |
| done | boolean | yes | false: nothing has changed yet; true: Proxmox has done it |
| expires_in_minutes | – | – | – |
| guest | – | – | – |
| problem | – | – | why it can't be done; nothing was changed |
| summary | string | yes | – |
No examples provided.
How do I install the Proxmox VE (Mojood Connect) MCP server?
Proxmox VE (Mojood Connect) runs locally as a PyPI package, launched with uvx mojood-proxmox-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 · mojood-proxmox-mcp
claude mcp add askmojood-proxmox-mcp -- uvx mojood-proxmox-mcp
What is the Proxmox VE (Mojood Connect) MCP server?
Proxmox VE (Mojood Connect) is an MCP server listed in the public MCP registry as io.github.askmojood/proxmox-mcp. Proxmox VE in Claude: VMs, storage, backups; start, stop, snapshot after a yes. This page covers its PyPI package (mojood-proxmox-mcp).
Is the Proxmox VE (Mojood Connect) MCP server safe to use?
Proxmox VE (Mojood Connect) scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Proxmox VE (Mojood Connect) MCP server expose?
Proxmox VE (Mojood Connect) exposes 6 tools: overview, find_guests, guest_details, needs_attention, power_guest, snapshot_guest. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the Proxmox VE (Mojood Connect) MCP server still maintained?
Proxmox VE (Mojood Connect) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Proxmox VE (Mojood Connect) MCP server under?
Proxmox VE (Mojood Connect) declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.