VirusTotal

Created By
barvhaim8 months ago
Unofficial VirusTotal MCP Server
Overview

what is VirusTotal MCP Server?

VirusTotal MCP Server is an unofficial server that utilizes the VirusTotal API for comprehensive security analysis, enabling AI assistants to detect malware and gather threat intelligence.

how to use VirusTotal MCP Server?

To use the VirusTotal MCP Server, set up the server with your VirusTotal API key and run the main script. You can analyze URLs, files, IP addresses, and domains by sending requests to the server.

key features of VirusTotal MCP Server?

  • Comprehensive security analysis with automatic relationship fetching
  • URL analysis providing security reports and threat actor information
  • Detailed file hash analysis including behaviors and network connections
  • IP analysis with geolocation and reputation data
  • Domain analysis with DNS records and WHOIS data
  • Rate limit aware to respect VirusTotal API limitations
  • Supports multiple transport methods like SSE and STDIO

use cases of VirusTotal MCP Server?

  1. Analyzing suspicious URLs for potential threats
  2. Investigating malware behavior through file analysis
  3. Gathering threat intelligence on IP addresses and domains

FAQ from VirusTotal MCP Server?

  • Can I use VirusTotal MCP Server for free?

The server requires a valid VirusTotal API key, which may have associated costs depending on usage.

  • What types of data can I analyze?

You can analyze URLs, files, IP addresses, and domains for security insights.

  • Is the server easy to set up?

Yes, the server can be set up by following the provided command and configuration instructions.

Server Config

{
  "mcpServers": {
    "virustotal": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/virustotal-mcp-server",
        "run",
        "main.py"
      ],
      "env": {
        "VIRUSTOTAL_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
barvhaim
Star
-
Language
-
License
-

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

8 hours ago