ProxmoxMCP-Plus (RekklesNA/ProxmoxMCP-Plus) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 56 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
7 days ago

ProxmoxMCP-Plus

Use MCP and OpenAPI to safely control Proxmox VE VMs, LXCs, backups, and snapshots from LLMs and AI agents.

→ RekklesNA/ProxmoxMCP-Plus· listed on github_topic

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

RekklesNA

Source: github_topic

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: MCP_API_KEY, PROXMOX_API_KEY, COMMAND_POLICY_APPROVAL_TOKEN, COMMAND_POLICY_HIGH_RISK_APPROVAL_TOKEN
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.
🔐 secretMCP_API_KEYSend Authorization: Bearer <> with every MCP HTTP request. MCP_API_KEY
configPROXMOX_MCP_CONFIG
configPROXMOX_ALLOW_NO_AUTHFor local unauthenticated development only, set =true.
configAPI_HOST
configAPI_PORT
🔐 secretPROXMOX_API_KEYis deliberately separate from the OpenAPI-only , so the two surfaces
configPROXMOX_STRICT_AUTH
configMCPO_CORS_ALLOW_ORIGINS
configMCPO_PATH_PREFIX
configMCPO_ROOT_PATH
configPROXMOX_RATE_LIMIT_RPM
configLOG_LEVEL
configCOMMAND_POLICY_MODE
🔐 secretCOMMAND_POLICY_APPROVAL_TOKEN
configCOMMAND_POLICY_HIGH_RISK_MODE
🔐 secretCOMMAND_POLICY_HIGH_RISK_APPROVAL_TOKEN
configPROXMOX_HOST
configPROXMOX_PORT
configPROXMOX_TIMEOUT
configPROXMOX_SERVICE
configPROXMOX_USER
configPROXMOX_TOKEN_NAME
configPROXMOX_TOKEN_VALUE
configPROXMOX_API_TUNNEL_SSH_HOST
configPROXMOX_API_TUNNEL_LOCAL_HOST
configPROXMOX_API_TUNNEL_LOCAL_PORT
configPROXMOX_API_TUNNEL_REMOTE_HOST
configPROXMOX_API_TUNNEL_REMOTE_PORT
configPROXMOX_API_TUNNEL_CONNECT_TIMEOUT
configMCP_HOST
configMCP_PORT
configMCP_TRANSPORT
configPROXMOX_JOBS_SQLITE_PATH
// 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

58/58 tools missing one or more hints — get_nodes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_node_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_storage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +55 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.

Tool test coverage

45/58 tools referenced in tests (78%)

Write tests that reference each tool by name so every tool has at least one test.

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 3 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 Score](https://m8ven.ai/badge/mcp/rekklesna/proxmoxmcp-plus)](https://m8ven.ai/mcp/rekklesna/proxmoxmcp-plus)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4c7fe6eda5ecd950eec8ff6ada74971b7165e540
code hash: d13ccc27a6faf809ea375f244453e43a99da4077aa20f4a698d030c5c605d7eb
verified: 9/4/2026, 3:21:05 AM
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