GPU MCP Server

MCP server for NVIDIA GPU metrics give AI agents real-time access to GPU utilization, memory, temperature, and power

MCP Servers HCL Grade C Listed Apache-2.0
52.9/100
Rank #687 of 1320
Compare GPU 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-08-29 · 6d ago
Recent change
Rank +6

Is GPU MCP Server safe? GPU MCP Server scores 52.9/100 (Grade C), ranked #687 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 78% of recent commits are signed; last pushed 2026-08-29. 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
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 17 spots (#670 → #687)
2026-09-03
Rank Moved
Rank dropped 85 spots (#585 → #670)
2026-09-02
Rank Moved
Rank dropped 29 spots (#556 → #585)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
46.4
Activity sub-score · out of 100
#343

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 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-04 22:32 UTC · Repo last pushed 6 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
15
Forks
13
Last Push
2026-08-29
6 days ago
Commits (4 wk)
5?
Downloads (7d)
HN mentions (30d)
Open Issues
11
Rank Change
▼17
was #670

Analysis

HVTrust Dimensions vs MCP Servers

52.9 / 100 · 100.0% confidence

GPU MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
1.2 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.4 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
1.0 above avg 12.2
AdoptionLog-scaled stars · package downloads
2.9 / 20
3.4 below avg 6.3

Activity Inputs

46.4 / 100
StarsRepository reach
7.2 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
5.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Sep 3, 2026
Signed Commits
78%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 1
SAST 10
Security-Policy 4
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 7

Is GPU MCP Server safe?

Public trust evidence for GPU 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 GPU MCP Server publish package provenance?
No published build provenance is currently detected for GPU MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GPU MCP Server have an OpenSSF Scorecard?
GPU MCP Server has an OpenSSF Scorecard score of 5.5/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 GPU MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does GPU MCP Server use?
GPU MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GPU MCP Server's commits signed?
77% of the last 100 commits to GPU 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
GPU 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
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain GPU MCP Server?

For maintainers

HVTrust scores GPU 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 1
2026-09-04
Rank Moved
Rank dropped 17 spots (#670 → #687)
2026-09-03
Rank Moved
Rank dropped 85 spots (#585 → #670)
2026-09-02
Rank Moved
Rank dropped 29 spots (#556 → #585)
2026-09-01
Rank Moved
Rank dropped 17 spots (#539 → #556)
2026-08-31
Rank Moved
Rank dropped 30 spots (#509 → #539)
2026-08-30
Rank Moved
Rank rose 11 spots (#520 → #509)
2026-08-29
Rank Moved
Rank dropped 17 spots (#503 → #520)
2026-08-27
Rank Moved
Rank dropped 11 spots (#488 → #499)
2026-08-26
Rank Moved
Rank dropped 56 spots (#432 → #488)
2026-08-25
Rank Moved
Rank dropped 22 spots (#410 → #432)
2026-08-24
Rank Moved
Rank dropped 16 spots (#394 → #410)
2026-08-22
Rank Moved
Rank rose 29 spots (#423 → #394)
2026-08-20
Rank Moved
Rank dropped 12 spots (#413 → #425)
2026-08-19
Rank Moved
Rank dropped 13 spots (#400 → #413)
2026-08-17
Rank Moved
Rank rose 11 spots (#413 → #402)
2026-08-16
Rank Moved
Rank dropped 10 spots (#403 → #413)
2026-08-13
Rank Moved
Rank dropped 19 spots (#383 → #402)
2026-08-10
Rank Moved
Rank dropped 12 spots (#375 → #387)
2026-08-08
Newly Listed
First tracked at rank #374

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/gpu-mcp-server.svg)](https://hvtracker.net/agents/gpu-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/gpu-mcp-server"><img src="https://hvtracker.net/badge/gpu-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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