Is Proxmox VE MCP Server safe to use?

Proxmox VE MCP Server has an HVTrust score of 71.3/100 (Grade B), ranked #310 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Proxmox VE MCP Server?

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

Proxmox VE MCP Server

Samik081/mcp-pve

Manage Proxmox VE through AI assistants

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.7 / 10

Provenance Attested

Signed commits 100%

Last push 24d ago

Compare Proxmox VE MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Proxmox VE MCP Server scores 71.3/100 (Grade B), ranked #310 of 1325 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; 100% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Proxmox VE MCP Server compares in MCP Servers

#184 FHIR MCP Server 71.3 ±0
#185 MCP Open Library 71.3 ±0
#186 Proxmox VE MCP Server 71.3 this agent
#187 Pubmed MCP Server 71.0 −0.3
#188 Octen MCP 71.0 −0.3

Bars show each HVTrust score; the tick marks Proxmox VE MCP Server’s 71.3.

Where the 71.3 comes from

HVTrust dimensions vs the MCP Servers average

71.3 / 100 · 100.0% confidence

Proxmox VE MCP Server MCP Servers average (775 agents)

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

17.1 / 25

6.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.3 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

6.3 / 20

0.9 below avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

Maintainer Checklist

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

Compare with another agent Get email alerts for Proxmox VE MCP Server View MCP Servers Report missing data

39.5

Activity sub-score · out of 100

#186

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 B 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-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-02

24 days ago

Commits (4 wk)

Downloads (7d)

152

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #311

Analysis

Activity Inputs

39.5 / 100

StarsRepository reach

8.4 / 30

FreshnessLast push recency

21.7 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

3.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 8

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Proxmox VE MCP Server

Proxmox VE MCP Server 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 Proxmox VE MCP Server publish package provenance?

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

Does Proxmox VE MCP Server have an OpenSSF Scorecard?

Proxmox VE MCP Server 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 Proxmox VE MCP Server actively maintained?

Maintained. Last push was 24 days ago.

What license does Proxmox VE MCP Server use?

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

Are Proxmox VE MCP Server's commits signed?

100% of the last 100 commits to Proxmox VE MCP Server 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

high confidence

Implemented

Proxmox VE MCP Server 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

high confidence

Match

Published package metadata matches the tracked repo

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 Proxmox VE MCP Server'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

Maintain Proxmox VE MCP Server?

For maintainers

HVTrust scores Proxmox VE MCP Server 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-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 770 spots (#1074 → #304)

2026-09-23

HVTrust Changed

HVTrust up 48.6pts (22.9 → 71.5)

2026-09-22

Newly Listed

First tracked at rank #1074

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 23 spots (#255 → #278)

2026-09-11

Rank Moved

Rank dropped 25 spots (#230 → #255)

2026-09-10

Rank Moved

Rank rose 28 spots (#258 → #230)

2026-09-08

Grade Changed

Trust grade D → B

2026-09-08

Rank Moved

Rank rose 687 spots (#942 → #255)

2026-09-08

HVTrust Changed

HVTrust up 24.5pts (48.2 → 72.7)

2026-09-07

Rank Moved

Rank dropped 41 spots (#901 → #942)

2026-09-06

Rank Moved

Rank dropped 15 spots (#886 → #901)

2026-09-05

Rank Moved

Rank dropped 50 spots (#836 → #886)

2026-09-04

Rank Moved

Rank dropped 34 spots (#802 → #836)

2026-09-03

Scorecard Added

OSSF Scorecard: 3.7/10

2026-09-03

Rank Moved

Rank rose 60 spots (#862 → #802)

2026-09-03

HVTrust Changed

HVTrust up 3.9pts (44.4 → 48.3)

2026-09-01

Rank Moved

Rank dropped 32 spots (#821 → #853)

2026-08-31

Rank Moved

Rank dropped 33 spots (#788 → #821)

2026-08-30

Rank Moved

Rank dropped 28 spots (#760 → #788)

2026-08-29

Rank Moved

Rank dropped 50 spots (#710 → #760)

2026-08-28

Rank Moved

Rank dropped 24 spots (#686 → #710)

2026-08-27

Rank Moved

Rank dropped 17 spots (#669 → #686)

2026-08-26

Rank Moved

Rank dropped 100 spots (#569 → #669)

2026-08-24

Rank Moved

Rank dropped 13 spots (#556 → #569)

2026-08-19

Rank Moved

Rank dropped 11 spots (#557 → #568)

2026-08-14

Rank Moved

Rank dropped 12 spots (#542 → #554)

2026-08-12

Rank Moved

Rank rose 33 spots (#582 → #549)

2026-08-12

Activity Score Changed

Activity score up 5pts (38 → 43)

2026-08-10

Rank Moved

Rank dropped 24 spots (#559 → #583)

2026-08-08

Newly Listed

First tracked at rank #557

GitHub → npm: @samik081/mcp-pve

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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