D
Caution
52/100
2 months ago

Proxmox VE

Integrates with Proxmox VE API to provide complete virtualization management including VM and container lifecycle operations, cloud-init configuration, firewall management, snapshots, backups, and resource pool administration with safety features like confirmation prompts and dry-run modes.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bsahane

Source: PulseMCP

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: PROXMOX_DEFAULT_LXC_PASSWORD, JWT_SECRET, PROXMOX_TOKEN_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPYTHONPATH
🔐 secretPROXMOX_DEFAULT_LXC_PASSWORD
🔐 secretJWT_SECRET
configPROXMOX_API_URL"https://proxmox.example.com:8006"
configPROXMOX_TOKEN_ID"root@pam!mcp-proxmox"
🔐 secretPROXMOX_TOKEN_SECRET"<secret>"
configPROXMOX_VERIFY
configPROXMOX_DEFAULT_NODE
configPROXMOX_DEFAULT_STORAGE"local-lvm"
configPROXMOX_DEFAULT_BRIDGE
configPROXMOX_CLUSTERS
configPROXMOX_CLUSTER_PATTERNS
configPROXMOX_CLUSTER_VALIDATION
configPROXMOX_CLUSTER_CACHE_TTL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

121/121 tools missing one or more hints — proxmox_list_all_clusters (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); proxmox_list_all_nodes_from_all_clusters (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); proxmox_list_all_vms_from_all_clusters (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +118 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — proxmox_configure_cloudinit_advanced deletes at line 1268 (os.unlink(iso_path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

108/121 tool handlers declare input schemas (89%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 4/121 tool handlers wrap calls in try/catch (3%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/bsahane-mcp-proxmox-wg2t7g?variant=verified)](https://m8ven.ai/mcp/bsahane-mcp-proxmox-wg2t7g)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 15dc99aa43e482665d7df701e8fe7aa6998894ad
code hash: 35ece86ab5f77dec83922458b9c2df7aabfa0e11b9d303ae0ae93e0b693c893c
verified: 6/16/2026, 12:31:04 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client