
MCP server exposing VirusTotal threat intelligence to AI agents: file, URL, domain and IP reports, analysis submission, and receipt recovery via VTAI.
The official VirusTotal MCP server gives your agent threat 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 do not need your own VirusTotal API key.
Use https://ai.virustotal.com/mcp in a compatible remote MCP client. Sign in
with your VTAI account and approve the connection's permissions; no local Python
installation, static token or personal VirusTotal API key is required.
The official plugin includes the OAuth connection, a threat-intelligence skill and existing reports for file hashes, URLs, domains and IP addresses. It includes no hooks or bundled scripts; local files are checked by hash.
claude plugin marketplace add VirusTotal/virustotal-mcp
claude plugin install virustotal@virustotal
Requires Claude Code 2.1.283 or later. The plugin needs no separate Node.js installation and runs no hooks or bundled scripts. The plugin includes https://ai.virustotal.com/mcp.
If you are replacing an existing manual connection with the plugin, read the migration and recovery guide before removing anything. Recover uncertain submissions through the original connection first; keep a working manual connection if you choose that alternative.
Start a new session or use /reload-plugins, then /mcp to complete browser
sign-in when needed. The plugin already supplies the MCP connection; do not add
a duplicate. See plugin setup, file checks and submission options.
For the remote connection without the plugin skill, use:
claude mcp add --transport http virustotal https://ai.virustotal.com/mcp
Open Claude Code, run /mcp, select virustotal and complete browser sign-in.
See the Claude Code OAuth instructions
and the VirusTotal connection guide.
Choose this alternative or the plugin. Adding a server configures it; complete authentication and a tool call to check
that your connection works.
OAuth connections share the signed-in VTAI account's free quota and use the
permissions approved for each connection. Existing Agent Tokens keep their rights
and quotas. If your client needs configurable HTTP headers, use one protected
Authorization: Bearer or x-apikey credential instead of OAuth. Other local
clients can use the stdio installation below.
~/.config/vt-mcp/token. Set the MCP server's environment variable VTAI_TOKEN_FILE to that path and its command to vt-mcp. The file contains only the token; never put the token itself in chat, command arguments or project files.| Client | Setup |
|---|---|
Antigravity CLI (agy) | Marketplace plugin with MCP and skill, local stdio or native OAuth recipe |
| Claude Code | OAuth plugin with threat-intelligence skill, HTTP or local stdio |
| Codex | HTTP or local stdio |
| ChatGPT | Install the published VirusTotal plugin · Connection guide |
| Cursor | HTTP recipe |
| VS Code with GitHub Copilot | HTTP recipe |
| GitHub Copilot CLI | HTTP OAuth recipe or local stdio |
| Devin CLI | HTTP OAuth recipe or local stdio |
| Windsurf / Devin Desktop | Cascade HTTP recipe |
| Antigravity IDE | Local stdio configuration or native OAuth recipe |
| Gemini CLI | Install the OAuth extension |
| Gemini Apps | Custom MCP connection and optional importable skill, subject to Google's account and regional availability; complete hosted workflow validation pending |
| Grok Build | Manual plugin installation; OAuth, reports and renewal verified |
| Kimi Code | Manual plugin installation; OAuth, reports and proactive renewal verified with an external model |
Remote OAuth configuration for GitHub Copilot CLI and Devin CLI follows their official documentation; an OAuth-authenticated VirusTotal tool workflow has not yet been verified in either client.
See additional remote client recipes for Qwen Code, Mistral Vibe Work, Grok web and the xAI Responses API, with their validation limits. Qwen Code 0.25.1 has a known OAuth credential-storage incompatibility with VTAI; browser consent alone does not complete its connection.