Is MCP Uptime Kuma safe to use?

MCP Uptime Kuma has an HVTrust score of 65.3/100 (Grade B), ranked #315 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Uptime Kuma?

MCP Uptime Kuma scores 65.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 48 GitHub stars and is categorized under MCP Servers.

MCP Uptime Kuma

DavidFuchs/mcp-uptime-kuma

A Model Context Protocol (MCP) server for Uptime Kuma version 2.

MCP Servers TypeScript Grade B Listed MIT

65.3/100

Rank #315 of 1320

Compare MCP Uptime Kuma

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Grade Changed +9

Is MCP Uptime Kuma safe? MCP Uptime Kuma scores 65.3/100 (Grade B), ranked #315 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.5/10; 68% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#150 Upstash MCP Server — 65.6 (B) → #151 MCP Proxmox — 65.5 (B) → #153 Google Workspace MCP — 65.2 (B) → #154 Growthbook MCP — 65.0 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 29 spots (#338 → #309)

2026-09-02

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.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.

Compare with another agent Get email alerts for MCP Uptime Kuma View MCP Servers Report missing data

55.2

Activity sub-score · out of 100

#152

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-04

Activity & Reach

Stars

Forks

Last Push

2026-09-03

yesterday

Commits (4 wk)

Downloads (7d)

480

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #309

Analysis

HVTrust Dimensions vs MCP Servers

65.3 / 100 · 100.0% confidence

MCP Uptime Kuma MCP Servers average (778 agents)

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

11.5 / 25

2.0 above avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.0 / 17

2.2 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.4 / 20

4.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.6 / 20

1.4 above avg 6.2

Activity Inputs

55.2 / 100

StarsRepository reach

10.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

13.9 / 25

CommunityFork signal

6.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.5 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

68%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 8

CII-Best-Practices 0

Code-Review 4

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 5

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 9

Is MCP Uptime Kuma safe?

MCP Uptime Kuma 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 Uptime Kuma publish package provenance?

No published build provenance is currently detected for MCP Uptime Kuma. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Uptime Kuma have an OpenSSF Scorecard?

MCP Uptime Kuma has an OpenSSF Scorecard score of 6.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 MCP Uptime Kuma actively maintained?

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

What license does MCP Uptime Kuma use?

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

Are MCP Uptime Kuma's commits signed?

67% of the last 100 commits to MCP Uptime Kuma 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

MCP Uptime Kuma appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 MCP Uptime Kuma?

For maintainers

HVTrust scores MCP Uptime Kuma 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-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 29 spots (#338 → #309)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 548 spots (#886 → #338)

2026-09-02

HVTrust Changed

HVTrust up 22.1pts (41.7 → 63.8)

2026-09-01

Rank Moved

Rank dropped 42 spots (#844 → #886)

2026-08-31

Rank Moved

Rank dropped 38 spots (#806 → #844)

2026-08-30

Rank Moved

Rank dropped 30 spots (#776 → #806)

2026-08-29

Rank Moved

Rank dropped 46 spots (#730 → #776)

2026-08-28

Rank Moved

Rank dropped 27 spots (#703 → #730)

2026-08-27

Rank Moved

Rank dropped 20 spots (#683 → #703)

2026-08-26

Scorecard Added

OSSF Scorecard: 6.5/10

2026-08-26

Rank Moved

Rank rose 283 spots (#966 → #683)

2026-08-26

HVTrust Changed

HVTrust up 20.5pts (22.3 → 42.8)

2026-08-24

Rank Moved

Rank dropped 12 spots (#956 → #968)

2026-08-21

Rank Moved

Rank rose 12 spots (#973 → #961)

2026-08-16

Rank Moved

Rank dropped 23 spots (#947 → #970)

2026-08-14

Rank Moved

Rank rose 12 spots (#965 → #953)

2026-08-12

Rank Moved

Rank rose 16 spots (#974 → #958)

2026-08-10

Rank Moved

Rank dropped 60 spots (#907 → #967)

2026-08-08

Newly Listed

First tracked at rank #896

GitHub → npm: @davidfuchs/mcp-uptime-kuma

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-uptime-kuma.svg)](https://hvtracker.net/agents/mcp-uptime-kuma)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-uptime-kuma"><img src="https://hvtracker.net/badge/mcp-uptime-kuma.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