Rösti Threat Intel vs io.github.BurtTheCoder/virustotal
Rösti Threat Intel is an MCP server published by rosti.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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)). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  io.github.BurtTheCoder/virustotal | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 No figure published Not marked · First seen |
Listed Version: 1.0.17 Downloads/month (npm): 3 103 Downloads/week (npm): 333 Forks (GitHub): 24 Stars (GitHub): 155 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.38 Downloads/month (npm): 3 103 Downloads/week (npm): 333 Forks (GitHub): 24 Stars (GitHub): 155 Not marked · First seen |
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
| Fact | Rösti Threat Intel | io.github.BurtTheCoder/virustotal |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 155 |
| Forks (GitHub) (differs) | No figure on GitHub | 24 |
| Last release (differs) | 2026-11-05 (better) | 2026-11-05 (worse) |
| Where it runs (differs) | Remote server (mcp.rosti.dev/mcp) | On your machine (@burtthecoder/mcp-virustotal) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/burtthecoder/mcp-virustotal |
| Changes in the last 7 days (differs) | 3 | 4 |
| First seen (differs) | 2026-11-04 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 15 h ago | no remote endpoint we check |
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
Rösti Threat Intel
Look up IOCs and search threat-intel reports, YARA rules, MITRE ATT&CK ids and CVEs from rosti.dev
io.github.BurtTheCoder/virustotal
MCP server for querying VirusTotal API with comprehensive security analysis tools.
How to run each
Rösti Threat Intel As a remote MCP server
claude mcp add --transport http rosti https://mcp.rosti.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
io.github.BurtTheCoder/virustotal As a local MCP server: npm package
claude mcp add --env "VIRUSTOTAL_API_KEY=<YOUR_VIRUSTOTAL_API_KEY>" --transport stdio virustotal -- npx -y @burtthecoder/mcp-virustotalRequires: VIRUSTOTAL_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rösti Threat Intel 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
The marketplaces of Rösti Threat Intel publish no settings it asks for, so we do not compare settings.
What it can do: Rösti Threat Intel · What it can do: io.github.BurtTheCoder/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.