updated 2026-09-26 06:32 UTC

MCP Virustotal

w0h1v/mcp-virustotal

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

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 26%
Last push 18d ago
Compare MCP Virustotal

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Virustotal scores 50.6/100 (Grade C), ranked #922 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 4.4/10; 26% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Virustotal compares in MCP Servers

  1. #523 ASP.NET Core Debugger — MCP Server for AI Agents 50.7 +0.1
  2. #524 MCP Shodan 50.7 +0.1
  3. #525 MCP Virustotal 50.6 this agent
  4. #526 Ros2 MCP 50.6 ±0
  5. #527 JADX MCP Server 50.6 ±0

Bars show each HVTrust score; the tick marks MCP Virustotal’s 50.6.

Where the 50.6 comes from

HVTrust dimensions vs the MCP Servers average

50.6 / 100 · 100.0% confidence

MCP Virustotal MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
3.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
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
14.6 / 20
2.5 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.0 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-25
Rank Moved
Rank dropped 12 spots (#912 → #924)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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.
Compare with another agent Get email alerts for MCP Virustotal View MCP Servers Report missing data
54.0
Activity sub-score · out of 100
#525
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 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-26 06:32 UTC · Repo last pushed 18 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
149
Forks
23
Last Push
2026-09-08
18 days ago
Commits (4 wk)
8
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▲2
was #924

Analysis

Activity Inputs

54.0 / 100
StarsRepository reach
13.1 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
6.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.4 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
26%
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 6
Packaging -1
Pinned-Dependencies 1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 10

Common questions about MCP Virustotal

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 4.4/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?
Maintained. Last push was 18 days ago.
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?
25% 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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-08
Activity Resumed
Activity resumed
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
Rank 21HVTrust 3Listed 2Grade 2Stale 1Scorecard 1Score 1Fresh 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 12 spots (#912 → #924)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 391 spots (#517 → #908)
2026-09-23
HVTrust Changed
HVTrust up 10.7pts (40.1 → 50.8)
2026-09-22
Newly Listed
First tracked at rank #517
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 12 spots (#892 → #904)
2026-09-16
Grade Changed
Trust grade D → C
2026-09-16
Rank Moved
Rank rose 51 spots (#933 → #882)
2026-09-13
Rank Moved
Rank rose 80 spots (#1005 → #925)
2026-09-12
Rank Moved
Rank dropped 12 spots (#993 → #1005)
2026-09-11
Rank Moved
Rank dropped 12 spots (#981 → #993)
2026-09-09
Rank Moved
Rank dropped 48 spots (#933 → #981)
2026-09-08
Activity Resumed
Activity resumed
2026-09-08
Rank Moved
Rank rose 222 spots (#1155 → #933)
2026-09-08
HVTrust Changed
HVTrust up 10.9pts (38.0 → 48.9)
2026-09-08
Activity Score Changed
Activity score up 27pts (30 → 56)
2026-09-07
Rank Moved
Rank dropped 18 spots (#1137 → #1155)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1123 → #1137)
2026-09-05
Rank Moved
Rank dropped 34 spots (#1089 → #1123)
2026-09-04
Rank Moved
Rank dropped 25 spots (#1064 → #1089)
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
HVTrust 50.6 Grade C
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