Provides tools for checking file, URL, domain, and IP reputation using VirusTotal's API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-virustotal Check the reputation of example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VirusTotal MCP — file / URL / domain / IP reputation. BYO API key.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
lookup_file(hash)
lookup_url(url)
lookup_domain(domain)
lookup_ip(ip)
Related MCP server: VirusTotal MCP Server
BYO only — free tier is 4 req/min and 500/day per key. Pass ?_apiKey=<key> on the gateway URL. Register at https://www.virustotal.com/gui/join-us.
https://www.virustotal.com/api/v3 — header x-apikey.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"virustotal": {
"url": "https://gateway.pipeworx.io/virustotal/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/virustotal/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/lookup_file. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"virustotal": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-virustotal"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-virustotalIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Virustotal data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Official VirusTotal MCP server: threat reports, file and URL submissions, and analysis recovery.
Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs.
Threat intel for AI agents: IOCs, CVEs (EPSS/KEV), wallet sanctions and age, domain and URL checks.
Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.
