VirusTotal MCP server

VirusTotal MCP

<!-- mcp-name: io.github.VirusTotal/virustotal-mcp -->

Give your agent VirusTotal intelligence before it opens a link, runs a downloaded file or investigates suspicious infrastructure. vt-mcp connects MCP clients to VTAI, with reports for files, URLs, domains and IP addresses, file and network analysis submission, and receipt recovery.

Use the free VTAI service with its current access limits. You need a VTAI token, available from connection setup; you do not need your own VirusTotal API key. Both local and remote connections use the same account rights and quotas.

Install for local stdio

For local stdio, install uv and run:

uv tool install --python 3.12 --default-index https://pypi.org/simple 'vt-mcp==0.9.1'
vt-mcp --version

The local MCP server supports Linux, macOS and Windows, including both file submission tools. Windows submission receipts require local NTFS storage; network shares and reparse points are rejected. The separate vt-mcp guard command remains Linux-only.

For automatic client configuration, use the setup guide and choose your operating system. It configures Agy, Claude Code or Codex and protects the token using owner-only POSIX permissions or a Windows user-only ACL.

The command installs the package from the official PyPI index in an isolated tool environment. Python 3.12 or newer is required. Keep vt-mcp on the MCP client's PATH, or use its absolute executable path. The package does not modify client configuration.

For a connection without a local Python process, use https://ai.virustotal.com/mcp with a supported HTTP client. Supply the VTAI token through either Authorization: Bearer or x-apikey, using the client's protected credential settings. Send only one authentication header. Compatible HTTP clients can instead use the hosted OAuth connection, with browser sign-in and per-application permissions.

Maintain an existing connection

Use the setup guide to check the configured transport and update a setup-managed installation without creating another token. Restart the client after an update. A configuration check does not exercise a tool or certify the model's behavior.

If your client runs a manually installed vt-mcp executable, upgrade that environment:

uv tool install --upgrade --python 3.12 --default-index https://pypi.org/simple 'vt-mcp==0.9.1'
vt-mcp --version

A client configured with uvx ... vt-mcp== uses that pinned version, independently of the installed executable. Update its pin or use the setup guide. Hosted HTTP connections use the deployed server; they do not need a local package upgrade. Keep existing tokens and submission receipts.

Missing-report, quota and temporary-service errors include nextsteps and a documentation link. Unknown files can be submitted when the agent has their actual bytes and authority to share them. An unknown URL can use submiturl; domain and IP analyses can be refreshed with reanalyzedomain and reanalyzeip. Retain a new UUIDv4 requestid before an intended network operation, then recover using that ID. VTAI report lookups do not explicitly submit an analysis request. On quota or temporary service failures, honor retryafter_seconds when present, retain credentials and avoid tight retry loops. Never automatically replay an uncertain submission or replace its request ID: recover its receipt first.

Connect your client

Shortened. The full README is on GitHub.