Ext Ops Panel
Open dashboard
Comparison

io.github.BurtTheCoder/virustotal vs Virustotal

io.github.BurtTheCoder/virustotal is an MCP server published by BurtTheCoder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Virustotal is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.BurtTheCoder/virustotalVirustotal
Official MCP Registry Listed
Version: 1.0.17
Downloads/month (npm): 3 103
Downloads/week (npm): 333
Forks (GitHub): 24
Stars (GitHub): 152
Not marked · First seen
Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.0.35
Downloads/month (npm): 3 103
Downloads/week (npm): 333
Forks (GitHub): 24
Stars (GitHub): 152
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.BurtTheCoder/virustotal vs Virustotal
Factio.github.BurtTheCoder/virustotalVirustotal
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)152 (better)0 (worse)
Forks (GitHub) (differs)24 (better)0 (worse)
Last release (differs)2026-10-14 (worse)2026-10-29 (better)
Where it runs (differs)On your machine (@burtthecoder/mcp-virustotal)Remote server (gateway.pipeworx.io/virustotal/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/burtthecoder/mcp-virustotalgithub.com/pipeworx-io/mcp-virustotal
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.BurtTheCoder/virustotal

In its own words, on Official MCP Registry:

MCP server for querying VirusTotal API with comprehensive security analysis tools.

Virustotal

In its own words, on Official MCP Registry:

VirusTotal MCP — file / URL / domain / IP reputation (BYO key)

How to run each

io.github.BurtTheCoder/virustotal As a local MCP server: npm package

Claude Code
claude mcp add --env "VIRUSTOTAL_API_KEY=<YOUR_VIRUSTOTAL_API_KEY>" --transport stdio virustotal -- npx -y @burtthecoder/mcp-virustotal

Requires: VIRUSTOTAL_API_KEY (secret)

Virustotal As a remote MCP server

Claude Code
claude mcp add --transport http virustotal https://gateway.pipeworx.io/virustotal/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Virustotal has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.BurtTheCoder/virustotal asks for

  • VIRUSTOTAL_API_KEY (secret)

Only Virustotal asks for

  • PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.BurtTheCoder/virustotal · What it can do: Virustotal · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built