Proxmox VE MCP Server

Manage Proxmox VE through AI assistants

MCP Servers TypeScript Grade D Listed MIT
48.1/100
Rank #956 of 1328
Compare Proxmox VE MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-02 · 6d ago
Recent change
Rank +8

Is Proxmox VE MCP Server safe? Proxmox VE MCP Server scores 48.1/100 (Grade D), ranked #956 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 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 →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Expose more independent signals, such as package metadata, provenance, or public usage evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 14 spots (#942 → #956)
2026-09-07
Rank Moved
Rank dropped 41 spots (#901 → #942)
2026-09-06
Rank Moved
Rank dropped 15 spots (#886 → #901)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.
46.1
Activity sub-score · out of 100
#552

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

Signals refreshed 2026-09-08 16:17 UTC · Repo last pushed 6 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
21
Forks
4
Last Push
2026-09-02
6 days ago
Commits (4 wk)
6?
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼14
was #942

Analysis

HVTrust Dimensions vs MCP Servers

48.1 / 100 · 67.0% confidence

Proxmox VE MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.1 / 25
7.2 above avg 9.9
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
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.2 / 20
3.7 below avg 6.9

Activity Inputs

46.1 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Sep 4, 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

Is Proxmox VE MCP Server safe?

Public trust evidence for Proxmox VE MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
Actively maintained. The repository was pushed to within the last 6 day(s).
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

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.

Reputation Timeline

Signal history
Rank 18Listed 1Score 1HVTrust 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 14 spots (#942 → #956)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.1 Grade D
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