# Proxmox VE (Mojood Connect) (pypi · mojood-proxmox-mcp)

Proxmox VE in Claude: VMs, storage, backups; start, stop, snapshot after a yes.

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `mojood-proxmox-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp.md), [page](https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp)

## Channel facts

- Registry: `pypi`
- Package: `mojood-proxmox-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to askmojood/proxmox-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 693 tokens (~115/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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 --stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add askmojood-proxmox-mcp -- uvx mojood-proxmox-mcp --stdio
```

### Cursor

```json
{
  "mcpServers": {
    "askmojood-proxmox-mcp": {
      "command": "uvx",
      "args": [
        "mojood-proxmox-mcp",
        "--stdio"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "askmojood-proxmox-mcp": {
      "command": "uvx",
      "args": [
        "mojood-proxmox-mcp",
        "--stdio"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add askmojood-proxmox-mcp -- uvx mojood-proxmox-mcp --stdio
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "askmojood-proxmox-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "mojood-proxmox-mcp",
        "--stdio"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  askmojood-proxmox-mcp:
    command: "uvx"
    args: ["mojood-proxmox-mcp", "--stdio"]
```

### Netclaw

```json
{
  "McpServers": {
    "askmojood-proxmox-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mojood-proxmox-mcp",
        "--stdio"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "askmojood-proxmox-mcp": {
      "command": "uvx",
      "args": [
        "mojood-proxmox-mcp",
        "--stdio"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65)

First indexed and scored.

## MCP tools (6)

### `overview` (~31 tokens)

Overview

Nodes (CPU, memory, uptime), storage use, how many guests run or are stopped, and the backup jobs.

Output parameters:

- `backup_jobs` (array)
- `containers` (integer)
- `nodes` (array)
- `running` (integer)
- `stopped` (integer)
- `storage` (array)
- `vms` (integer)

### `find_guests` (~88 tokens)

Find guests

VMs and containers with status, tags, CPU and memory in use now, and uptime.

Input parameters:

- `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"

Output parameters:

- `guests` (array)
- `total` (integer)

### `guest_details` (~76 tokens)

A guest in detail

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).

Input parameters:

- `guest` (string, required): a name or id, e.g. "erp-db" or "101"

Output parameters:

- `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`

### `needs_attention` (~56 tokens)

What needs attention

Guests no backup job covers, overdue backups, production guests that are stopped, old snapshots, storage
filling up, and guests short of memory.

Input parameters:

- `backup_days` (integer): a backup older than this many days counts as overdue

Output parameters:

- `backups_overdue` (array): in a backup job, but no backup newer than the limit
- `memory_high` (array)
- `not_in_any_backup_job` (array): guests no backup job covers
- `old_snapshots` (array)
- `production_stopped` (array): tagged "prod" and not running
- `storage_filling` (array)

### `power_guest` (~106 tokens)

Start, shut down or reboot a guest

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.

Input parameters:

- `action` (string, required): shutdown and reboot go through the guest OS
- `confirmation`: leave empty first; pass the code only after the user confirms
- `guest` (string, required): a name or id, e.g. "mail-relay"

Output parameters:

- `confirmation`: when done is false: the code to pass back, only after the user says yes
- `done` (boolean): 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)

### `snapshot_guest` (~128 tokens)

Take a snapshot

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.

Input parameters:

- `confirmation`: leave empty first; pass the code only after the user confirms
- `description`: why, in a few words
- `guest` (string, required): a name or id, e.g. "erp-db"
- `name` (string, required): letters, digits, "-" or "_", starting with a letter, e.g. "before-update"

Output parameters:

- `confirmation`: when done is false: the code to pass back, only after the user says yes
- `done` (boolean): 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)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65

## Common questions

### 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.

### What did VerifyMCP test on the Proxmox VE (Mojood Connect) MCP server?

VerifyMCP ran 15 checks on Proxmox VE (Mojood Connect), covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Proxmox VE (Mojood Connect): Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/mojood-proxmox-mcp/
- Socket report: https://socket.dev/pypi/package/mojood-proxmox-mcp
- Repository: https://github.com/askmojood/proxmox-mcp
- Website: https://mojood.app/connect
- Changelog RSS feed: https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp.json
- HTML version of this page: https://verifymcp.io/servers/askmojood-proxmox-mcp/mojood-proxmox-mcp