Is MCP Victorialogs safe to use?

MCP Victorialogs has an HVTrust score of 43.6/100 (Grade D), ranked #1093 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Victorialogs?

MCP Victorialogs scores 43.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 98 GitHub stars and is categorized under MCP Servers.

MCP Victorialogs

VictoriaMetrics/mcp-victorialogs

The implementation of Model Context Protocol (MCP) server for VictoriaLogs.

MCP Servers Go Listed Apache-2.0

Is MCP Victorialogs safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 99%

Last push 73d ago

Compare MCP Victorialogs

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Victorialogs scores 43.6/100 (Grade D), ranked #1093 of 1325 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 3.1/10; 99% of recent commits are signed; last pushed 2026-07-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Victorialogs compares in MCP Servers

#639 Google Health Fitbit MCP 43.8 +0.2
#640 Kolada MCP Server 43.6 ±0
#641 MCP Victorialogs 43.6 this agent
#642 Power Automate MCP Server by Flow Studio 43.6 ±0
#643 Seo Crawler MCP 43.5 −0.1

Bars show each HVTrust score; the tick marks MCP Victorialogs’s 43.6.

Where the 43.6 comes from

HVTrust dimensions vs the MCP Servers average

43.6 / 100 · 100.0% confidence

MCP Victorialogs MCP Servers average (775 agents)

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

8.8 / 25

1.5 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

7.1 / 20

5.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

4.8 / 20

2.4 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 98 spots (#1184 → #1086)

2026-09-23

HVTrust Changed

HVTrust up 24.1pts (19.7 → 43.8)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 73 days ago. Fresh activity helps separate stable projects from stale ones.

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

33.9

Activity sub-score · out of 100

#641

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-07-15

73 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #1093

Analysis

Activity Inputs

33.9 / 100

StarsRepository reach

12.0 / 30

FreshnessLast push recency

14.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

99%

of last 100 commits verified

Binary-Artifacts 0

Branch-Protection 3

CI-Tests 3

CII-Best-Practices 0

Code-Review 4

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Victorialogs

Public trust evidence for MCP Victorialogs 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 MCP Victorialogs publish package provenance?

No published build provenance is currently detected for MCP Victorialogs. 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 Victorialogs have an OpenSSF Scorecard?

MCP Victorialogs has an OpenSSF Scorecard score of 3.1/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 Victorialogs actively maintained?

Slowing down. Last push was 73 days ago — keep an eye on whether activity resumes.

What license does MCP Victorialogs use?

MCP Victorialogs ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Victorialogs's commits signed?

99% of the last 100 commits to MCP Victorialogs 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 Victorialogs 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

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

How this surface has changed

Detected changes to MCP Victorialogs'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 Victorialogs?

For maintainers

HVTrust scores MCP Victorialogs 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

Rank Moved

Rank rose 98 spots (#1184 → #1086)

2026-09-23

HVTrust Changed

HVTrust up 24.1pts (19.7 → 43.8)

2026-09-22

Newly Listed

First tracked at rank #1184

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 219 spots (#1290 → #1071)

2026-09-17

HVTrust Changed

HVTrust up 14.3pts (29.9 → 44.2)

2026-09-16

Rank Moved

Rank dropped 216 spots (#1074 → #1290)

2026-09-16

HVTrust Changed

HVTrust down 14.5pts (44.4 → 29.9)

2026-09-12

Rank Moved

Rank rose 217 spots (#1283 → #1066)

2026-09-12

HVTrust Changed

HVTrust up 14.5pts (30.1 → 44.6)

2026-09-11

Rank Moved

Rank dropped 236 spots (#1047 → #1283)

2026-09-11

HVTrust Changed

HVTrust down 14.6pts (44.7 → 30.1)

2026-09-09

Rank Moved

Rank dropped 18 spots (#1029 → #1047)

2026-09-08

Rank Moved

Rank rose 236 spots (#1265 → #1029)

2026-09-08

HVTrust Changed

HVTrust up 14.5pts (30.3 → 44.8)

2026-09-07

Rank Moved

Rank dropped 281 spots (#984 → #1265)

2026-09-07

HVTrust Changed

HVTrust down 14.7pts (45.0 → 30.3)

2026-09-06

Rank Moved

Rank dropped 12 spots (#972 → #984)

2026-09-05

Rank Moved

Rank dropped 47 spots (#925 → #972)

2026-09-04

Rank Moved

Rank dropped 33 spots (#892 → #925)

2026-09-03

Rank Moved

Rank dropped 50 spots (#842 → #892)

2026-09-02

Rank Moved

Rank dropped 47 spots (#795 → #842)

2026-09-01

Rank Moved

Rank dropped 33 spots (#762 → #795)

2026-08-31

Rank Moved

Rank dropped 33 spots (#729 → #762)

2026-08-30

Rank Moved

Rank dropped 27 spots (#702 → #729)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.1/10

2026-08-29

Rank Moved

Rank rose 463 spots (#1165 → #702)

2026-08-29

HVTrust Changed

HVTrust up 25.4pts (20.1 → 45.5)

2026-08-28

Rank Moved

Rank dropped 22 spots (#1143 → #1165)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1130 → #1143)

2026-08-26

Rank Moved

Rank dropped 67 spots (#1063 → #1130)

2026-08-17

Rank Moved

Rank rose 10 spots (#1065 → #1055)

2026-08-16

Rank Moved

Rank dropped 35 spots (#1030 → #1065)

2026-08-12

Rank Moved

Rank rose 16 spots (#1037 → #1021)

2026-08-10

Rank Moved

Rank dropped 59 spots (#970 → #1029)

2026-08-08

Newly Listed

First tracked at rank #966

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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