Is MCP Virustotal safe to use?

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

MCP Virustotal scores 38.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 149 GitHub stars and is categorized under MCP Servers.

MCP Virustotal

w0h1v/mcp-virustotal

MCP server for VirusTotal API — analyze URLs, files, IPs, and domains with comprehensive security reports, relationship

MCP Servers TypeScript Grade D Listed MIT

38.2/100

Rank #1079 of 1320

Compare MCP Virustotal

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-05-24 · 103d ago

Recent change

Rank +7

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

Ranked neighbours in MCP Servers

#610 Openwebninja MCP — 38.5 (D) → #611 Studio MCP — 38.3 (D) → #613 MCP Server for Binge-watch — 38.2 (D) → #614 Akshare One MCP — 38.1 (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 (#1064 → #1079)

2026-09-03

Rank Moved

Rank dropped 54 spots (#1010 → #1064)

2026-09-02

Rank Moved

Rank dropped 47 spots (#963 → #1010)

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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

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

29.9

Activity sub-score · out of 100

#612

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

149

Forks

Last Push

2026-05-24

103 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #1064

Analysis

HVTrust Dimensions vs MCP Servers

38.2 / 100 · 100.0% confidence

MCP Virustotal MCP Servers average (778 agents)

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

5.0 / 25

4.5 below 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.1 / 17

0.7 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

5.1 / 20

7.1 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.2 / 20

1.0 below avg 6.2

Activity Inputs

29.9 / 100

StarsRepository reach

13.1 / 30

FreshnessLast push recency

10.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

23%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Is MCP Virustotal safe?

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

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

MCP Virustotal 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 Virustotal actively maintained?

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

What license does MCP Virustotal use?

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

Are MCP Virustotal's commits signed?

23% of the last 100 commits to MCP Virustotal 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 Virustotal 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 Virustotal'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-08-22

Activity Went Stale

No commits for 90 days

Maintain MCP Virustotal?

For maintainers

HVTrust scores MCP Virustotal 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 (#1064 → #1079)

2026-09-03

Rank Moved

Rank dropped 54 spots (#1010 → #1064)

2026-09-02

Rank Moved

Rank dropped 47 spots (#963 → #1010)

2026-09-01

Rank Moved

Rank dropped 41 spots (#922 → #963)

2026-08-31

Scorecard Added

OSSF Scorecard: 3.1/10

2026-08-31

Rank Moved

Rank rose 358 spots (#1280 → #922)

2026-08-31

HVTrust Changed

HVTrust up 21.9pts (16.6 → 38.5)

2026-08-29

Rank Moved

Rank dropped 13 spots (#1259 → #1272)

2026-08-26

Rank Moved

Rank dropped 31 spots (#1211 → #1242)

2026-08-22

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 26 spots (#1183 → #1209)

2026-08-10

Rank Moved

Rank dropped 73 spots (#1108 → #1181)

2026-08-08

Newly Listed

First tracked at rank #1104

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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