Is MCP Victoriametrics safe to use?

MCP Victoriametrics has an HVTrust score of 49.8/100 (Grade D), ranked #769 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 Victoriametrics?

MCP Victoriametrics scores 49.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 229 GitHub stars and is categorized under MCP Servers.

MCP Victoriametrics

VictoriaMetrics/mcp-victoriametrics

The implementation of Model Context Protocol (MCP) server for VictoriaMetrics

MCP Servers Go Grade D Listed Apache-2.0

49.8/100

Rank #769 of 1320

Compare MCP Victoriametrics

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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-23 · 12d ago

Recent change

Rank +11

Is MCP Victoriametrics safe? MCP Victoriametrics scores 49.8/100 (Grade D), ranked #769 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 3.6/10; 100% of recent commits are signed; last pushed 2026-08-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#401 Tugcantopaloglu Godot MCP — 49.9 (D) → #402 Markdownify MCP — 49.9 (D) → #404 MCP After Effects — 49.8 (D) → #405 MTG MCP Server — 49.7 (D) →

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 15 spots (#754 → #769)

2026-09-03

Rank Moved

Rank dropped 43 spots (#711 → #754)

2026-09-02

Rank Moved

Rank dropped 37 spots (#674 → #711)

Maintainer Checklist

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

44.3

Activity sub-score · out of 100

#403

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

Activity & Reach

Stars

229

Forks

Last Push

2026-08-23

12 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #754

Analysis

HVTrust Dimensions vs MCP Servers

49.8 / 100 · 100.0% confidence

MCP Victoriametrics MCP Servers average (778 agents)

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

9.5 / 25

in line with 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

11.6 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

11.2 / 20

1.0 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.7 / 20

0.5 below avg 6.2

Activity Inputs

44.3 / 100

StarsRepository reach

14.2 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Aug 30, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 0

Branch-Protection 1

CI-Tests 9

CII-Best-Practices 0

Code-Review 5

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 3

Packaging 10

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is MCP Victoriametrics safe?

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

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

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

Maintained. Last push was 12 days ago.

What license does MCP Victoriametrics use?

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

Are MCP Victoriametrics's commits signed?

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

Maintain MCP Victoriametrics?

For maintainers

HVTrust scores MCP Victoriametrics 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-04

Rank Moved

Rank dropped 15 spots (#754 → #769)

2026-09-03

Rank Moved

Rank dropped 43 spots (#711 → #754)

2026-09-02

Rank Moved

Rank dropped 37 spots (#674 → #711)

2026-09-01

Grade Changed

Trust grade C → D

2026-09-01

Rank Moved

Rank dropped 25 spots (#649 → #674)

2026-08-31

Rank Moved

Rank dropped 35 spots (#614 → #649)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.6/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 525 spots (#1139 → #614)

2026-08-30

HVTrust Changed

HVTrust up 28.2pts (21.8 → 50.0)

2026-08-29

Rank Moved

Rank dropped 31 spots (#1108 → #1139)

2026-08-28

Rank Moved

Rank dropped 24 spots (#1084 → #1108)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1061 → #1084)

2026-08-26

Rank Moved

Rank dropped 74 spots (#987 → #1061)

2026-08-24

Rank Moved

Rank dropped 11 spots (#973 → #984)

2026-08-23

Rank Moved

Rank rose 58 spots (#1031 → #973)

2026-08-17

Rank Moved

Rank rose 12 spots (#1038 → #1026)

2026-08-16

Rank Moved

Rank dropped 37 spots (#1001 → #1038)

2026-08-13

Rank Moved

Rank dropped 12 spots (#993 → #1005)

2026-08-12

Rank Moved

Rank rose 13 spots (#1006 → #993)

2026-08-10

Rank Moved

Rank dropped 57 spots (#947 → #1004)

2026-08-08

Newly Listed

First tracked at rank #933

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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