MCP Victoriatraces

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

MCP Servers Go Grade D Listed Apache-2.0
49.3/100
Rank #782 of 1320
Compare MCP Victoriatraces

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-09-01 · 3d ago
Recent change
Scorecard +9

Is MCP Victoriatraces safe? MCP Victoriatraces scores 49.3/100 (Grade D), ranked #782 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 4.5/10; 100% of recent commits are signed; last pushed 2026-09-01. 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
Scorecard Added
OSSF Scorecard: 4.5/10
2026-09-04
Rank Moved
Rank rose 500 spots (#1282 → #782)
2026-09-04
HVTrust Changed
HVTrust up 28.8pts (20.5 → 49.3)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
35.4
Activity sub-score · out of 100
#413

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 →

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
14
Forks
5
Last Push
2026-09-01
3 days ago
Commits (4 wk)
0?
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▲500
was #1282

Analysis

HVTrust Dimensions vs MCP Servers

49.3 / 100 · 100.0% confidence

MCP Victoriatraces MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.6 / 25
1.1 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
12.3 / 17
0.5 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
11.8 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
2.8 / 20
3.4 below avg 6.2

Activity Inputs

35.4 / 100
StarsRepository reach
7.1 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 0
Branch-Protection 6
CI-Tests 0
CII-Best-Practices 0
Code-Review 10
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 6

Is MCP Victoriatraces safe?

Public trust evidence for MCP Victoriatraces 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 Victoriatraces publish package provenance?
No published build provenance is currently detected for MCP Victoriatraces. 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 Victoriatraces have an OpenSSF Scorecard?
MCP Victoriatraces has an OpenSSF Scorecard score of 4.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 Victoriatraces actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does MCP Victoriatraces use?
MCP Victoriatraces ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Victoriatraces's commits signed?
100% of the last 100 commits to MCP Victoriatraces 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
medium confidence
Implemented
MCP Victoriatraces 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 Victoriatraces?

For maintainers

HVTrust scores MCP Victoriatraces 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 16Listed 1HVTrust 1Scorecard 1
2026-09-04
Scorecard Added
OSSF Scorecard: 4.5/10
2026-09-04
Rank Moved
Rank rose 500 spots (#1282 → #782)
2026-09-04
HVTrust Changed
HVTrust up 28.8pts (20.5 → 49.3)
2026-09-03
Rank Moved
Rank dropped 16 spots (#1266 → #1282)
2026-09-02
Rank Moved
Rank dropped 24 spots (#1242 → #1266)
2026-09-01
Rank Moved
Rank dropped 17 spots (#1225 → #1242)
2026-08-31
Rank Moved
Rank dropped 26 spots (#1199 → #1225)
2026-08-30
Rank Moved
Rank dropped 21 spots (#1178 → #1199)
2026-08-29
Rank Moved
Rank dropped 26 spots (#1152 → #1178)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1127 → #1152)
2026-08-27
Rank Moved
Rank dropped 15 spots (#1112 → #1127)
2026-08-26
Rank Moved
Rank dropped 64 spots (#1048 → #1112)
2026-08-25
Rank Moved
Rank rose 11 spots (#1059 → #1048)
2026-08-24
Rank Moved
Rank dropped 13 spots (#1046 → #1059)
2026-08-18
Rank Moved
Rank rose 33 spots (#1080 → #1047)
2026-08-17
Rank Moved
Rank rose 15 spots (#1095 → #1080)
2026-08-16
Rank Moved
Rank dropped 31 spots (#1064 → #1095)
2026-08-10
Rank Moved
Rank dropped 57 spots (#1002 → #1059)
2026-08-08
Newly Listed
First tracked at rank #991

Embed Badge Badge guide for maintainers →

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