Is MCP Proxmox safe to use?

MCP Proxmox has an HVTrust score of 64.6/100 (Grade C), ranked #548 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Proxmox?

MCP Proxmox scores 64.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 18 GitHub stars and is categorized under MCP Servers.

MCP Proxmox

Repository

MCP server for managing Proxmox VE clusters through AI assistants

MCP Servers Python Listed MIT

Is MCP Proxmox safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10

Provenance Attested

Signed commits 25%

Last push 7d ago

Advisories None known

Compare MCP Proxmox

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Proxmox scores 64.6/100 (Grade C), ranked #548 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.7/10; 25% of recent commits are signed; no published advisory affects its latest release (mcp-proxmox); last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Proxmox could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 3.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +11.1 → 75.7 B · #149 of 779
Sign every commit25% signed today +3.7 → 68.3 B · #247 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Proxmox and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/antonio-mello-ai/mcp-proxmox, MIT, last pushed 2026-11-04. 25% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Partly attested
- PyPI mcp-proxmox Source link points to this repo's current name Build provenance attested
What you install today No known advisories

Latest release checked: mcp-proxmox 1.2.4. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-29 OSSF Scorecard: 3.3/10
2026-08-17 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Proxmox’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Proxmox compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Proxmox’s 64.6.

Where the 64.6 comes from

HVTrust dimensions vs the MCP Servers average

64.6 / 100 · 100.0% confidence

MCP Proxmox MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.4 / 25

2.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.7 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

12.9 / 20

0.6 above avg 12.3

AdoptionLog-scaled stars · package downloads

6.7 / 20

0.9 below avg 7.6

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-11-06

Rank Moved

Rank rose 23 spots (#556 → #533)

2026-11-05

Grade Changed

Trust grade B → C

2026-11-05

Rank Moved

Rank dropped 129 spots (#427 → #556)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

44.5

Activity sub-score · out of 100

#311

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-04

7 days ago

Commits (4 wk)

Downloads (7d)

485

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #549

Analysis

Activity Inputs

44.5 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

3.9 / 20

Common questions about MCP Proxmox

MCP Proxmox has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Proxmox publish package provenance?

Yes. MCP Proxmox's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Proxmox have an OpenSSF Scorecard?

MCP Proxmox has an OpenSSF Scorecard score of 3.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Proxmox actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does MCP Proxmox use?

MCP Proxmox ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Proxmox's commits signed?

25% of the last 100 commits to MCP Proxmox are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

MCP Proxmox appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to MCP Proxmox's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-17

Provenance Added

Package provenance attestation detected

Maintain MCP Proxmox?

For maintainers

HVTrust scores MCP Proxmox from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-06

Rank Moved

Rank rose 23 spots (#556 → #533)

2026-11-05

Grade Changed

Trust grade B → C

2026-11-05

Rank Moved

Rank dropped 129 spots (#427 → #556)

2026-11-05

HVTrust Changed

HVTrust down 3.8pts (68.0 → 64.2)

2026-11-04

Grade Changed

Trust grade C → B

2026-11-04

Rank Moved

Rank rose 163 spots (#590 → #427)

2026-11-04

HVTrust Changed

HVTrust up 4.7pts (63.3 → 68.0)

2026-11-04

Activity Score Changed

Activity score up 15pts (30 → 45)

2026-10-21

Grade Changed

Trust grade B → C

2026-10-21

Rank Moved

Rank dropped 99 spots (#449 → #548)

2026-10-21

Activity Score Changed

Activity score down 9pts (41 → 32)

2026-10-18

Rank Moved

Rank dropped 10 spots (#434 → #444)

2026-10-16

Rank Moved

Rank dropped 21 spots (#419 → #440)

2026-10-12

Rank Moved

Rank rose 27 spots (#435 → #408)

2026-10-09

Rank Moved

Rank dropped 15 spots (#414 → #429)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 659 spots (#1053 → #394)

2026-09-23

HVTrust Changed

HVTrust up 43.6pts (23.5 → 67.1)

2026-09-22

Newly Listed

First tracked at rank #1053

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 57 spots (#473 → #530)

2026-09-16

Activity Score Changed

Activity score down 6pts (38 → 32)

2026-09-12

Grade Changed

Trust grade B → C

2026-09-11

Rank Moved

Rank dropped 12 spots (#444 → #456)

2026-09-07

Rank Moved

Rank dropped 30 spots (#396 → #426)

2026-09-05

Rank Moved

Rank dropped 73 spots (#317 → #390)

2026-09-04

Rank Moved

Rank dropped 12 spots (#305 → #317)

2026-09-03

Rank Moved

Rank dropped 21 spots (#284 → #305)

2026-09-02

Rank Moved

Rank dropped 17 spots (#267 → #284)

2026-08-31

Rank Moved

Rank dropped 31 spots (#231 → #262)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.3/10

2026-08-29

Grade Changed

Trust grade C → B

2026-08-29

Rank Moved

Rank rose 140 spots (#378 → #238)

2026-08-29

HVTrust Changed

HVTrust up 6.7pts (59.9 → 66.6)

2026-08-27

Rank Moved

Rank dropped 14 spots (#363 → #377)

2026-08-26

Rank Moved

Rank dropped 38 spots (#325 → #363)

2026-08-25

Rank Moved

Rank rose 10 spots (#335 → #325)

2026-08-24

Rank Moved

Rank dropped 17 spots (#318 → #335)

2026-08-22

Rank Moved

Rank rose 18 spots (#335 → #317)

2026-08-19

Rank Moved

Rank dropped 15 spots (#320 → #335)

2026-08-18

Rank Moved

Rank rose 13 spots (#333 → #320)

2026-08-17

Provenance Added

Package provenance attestation detected

2026-08-17

Grade Changed

Trust grade D → C

2026-08-17

Rank Moved

Rank rose 469 spots (#802 → #333)

2026-08-17

HVTrust Changed

HVTrust up 31.3pts (28.2 → 59.5)

2026-08-17

Activity Score Changed

Activity score up 15pts (27 → 42)

2026-08-16

Rank Moved

Rank dropped 17 spots (#785 → #802)

GitHub → PyPI: mcp-proxmox

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-proxmox.svg)](https://hvtracker.net/agents/mcp-proxmox)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-proxmox"><img src="https://hvtracker.net/badge/mcp-proxmox.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

MCP Proxmox

How MCP Proxmox could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MCP Proxmox compares in MCP Servers

Where the 64.6 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP Proxmox

AI agent surface

Maintain MCP Proxmox?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers