Is MCP Uptime Kuma safe to use?

MCP Uptime Kuma has an HVTrust score of 62.5/100 (Grade C), ranked #626 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 Uptime Kuma?

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

MCP Uptime Kuma

Repository

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

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 5.9 / 10

Provenance None

Signed commits 77%

Last push yesterday

Advisories None known

Compare MCP Uptime Kuma

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Uptime Kuma scores 62.5/100 (Grade C), ranked #626 of 1387 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 5.9/10; 77% of recent commits are signed; no published advisory affects its latest release (@davidfuchs/mcp-uptime-kuma); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Uptime Kuma 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 77.2 B · #133 of 779
Raise the OSSF Scorecard from 5.9 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Token-Permissions 0 +6.5 → 69.0 B · #230 of 779
Sign every commit77% signed today +1.2 → 63.7 C · #329 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 Uptime Kuma 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/DavidFuchs/mcp-uptime-kuma, MIT, last pushed 2026-11-10. 77% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies3
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 3

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 7

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- npm @davidfuchs/mcp-uptime-kuma Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: @davidfuchs/mcp-uptime-kuma 0.12.1. No published advisory affects it (OSV, checked 2026-11-11).

Changes to this chain

2026-08-26 OSSF Scorecard: 6.5/10

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 Uptime Kuma’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 Uptime Kuma compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Uptime Kuma’s 62.5.

Where the 62.5 comes from

HVTrust dimensions vs the MCP Servers average

62.5 / 100 · 100.0% confidence

MCP Uptime Kuma MCP Servers average (779 agents)

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

11.2 / 25

in line with avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.5 / 17

1.2 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.7 / 20

1.4 above avg 12.3

AdoptionLog-scaled stars · package downloads

8.3 / 20

0.7 above avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-11

Rank Moved

Rank rose 19 spots (#645 → #626)

2026-11-11

Activity Score Changed

Activity score up 6pts (48 → 54)

2026-11-05

Rank Moved

Rank dropped 47 spots (#590 → #637)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.9/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 View MCP Servers Report missing data

54.0

Activity sub-score · out of 100

#344

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

yesterday

Commits (4 wk)

Downloads (7d)

735

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲19

was #645

Analysis

Activity Inputs

54.0 / 100

StarsRepository reach

11.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

6.6 / 20

Common questions about MCP Uptime Kuma

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 5.9/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?

77% 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

How this surface has changed

Detected changes to MCP Uptime Kuma'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

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

Rank Moved

Rank rose 19 spots (#645 → #626)

2026-11-11

Activity Score Changed

Activity score up 6pts (48 → 54)

2026-11-05

Rank Moved

Rank dropped 47 spots (#590 → #637)

2026-11-04

Rank Moved

Rank rose 66 spots (#656 → #590)

2026-10-27

Rank Moved

Rank rose 10 spots (#647 → #637)

2026-10-23

Rank Moved

Rank dropped 40 spots (#590 → #630)

2026-10-20

Rank Moved

Rank rose 27 spots (#615 → #588)

2026-10-19

Rank Moved

Rank dropped 21 spots (#594 → #615)

2026-10-15

Rank Moved

Rank rose 17 spots (#598 → #581)

2026-10-10

Rank Moved

Rank rose 19 spots (#603 → #584)

2026-10-09

Rank Moved

Rank dropped 99 spots (#504 → #603)

2026-10-07

Grade Changed

Trust grade B → C

2026-10-07

Rank Moved

Rank dropped 36 spots (#466 → #502)

2026-10-06

Grade Changed

Trust grade C → B

2026-10-06

Rank Moved

Rank rose 92 spots (#558 → #466)

2026-10-06

Activity Score Changed

Activity score up 6pts (49 → 55)

2026-10-03

Rank Moved

Rank dropped 33 spots (#517 → #550)

2026-09-30

Rank Moved

Rank dropped 27 spots (#485 → #512)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 304 spots (#770 → #466)

2026-09-23

HVTrust Changed

HVTrust up 35.7pts (29.6 → 65.3)

2026-09-22

Newly Listed

First tracked at rank #770

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank dropped 40 spots (#457 → #497)

2026-09-16

Grade Changed

Trust grade B → C

2026-09-14

Rank Moved

Rank dropped 17 spots (#433 → #450)

2026-09-08

Grade Changed

Trust grade C → B

2026-09-07

Rank Moved

Rank dropped 38 spots (#406 → #444)

2026-09-06

Rank Moved

Rank dropped 10 spots (#396 → #406)

2026-09-05

Grade Changed

Trust grade B → C

2026-09-05

Rank Moved

Rank dropped 77 spots (#319 → #396)

2026-09-04

Rank Moved

Rank dropped 10 spots (#309 → #319)

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)

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.4 · Raw JSON

MCP Uptime Kuma

How MCP Uptime Kuma could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked, not 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 Uptime Kuma compares in MCP Servers

Where the 62.5 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP Uptime Kuma

AI agent surface

Maintain MCP Uptime Kuma?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers