Cloud Audit vs MCP Virustotal
A side-by-side look at the Cloud Audit and MCP Virustotal MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloud Audit for security work as a local process; choose MCP Virustotal for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloud Audit when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose MCP Virustotal when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VIRUSTOTAL_API_KEY, MCP_TRANSPORT, MCP_PORT, MCP_ENDPOINT. - You want tools like
get_url_report, url, get_file_report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 52/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | VIRUSTOTAL_API_KEYMCP_TRANSPORTMCP_PORTMCP_ENDPOINT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 72 | 150 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 24 |
| Full listing | View Cloud Audit | View MCP Virustotal |
Tools & capabilities
Cloud Audit tools
No tool names declared yet. Check the project README from the listing page.
MCP Virustotal tools 24
get_url_reporturlget_file_reporthashget_ip_reportipget_domain_reportdomainrelationshipsget_url_relationshiprelationshiplimit- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cloud Audit
{
"mcpServers": {
"gebalamariusz-cloud-audit": {
"command": "uvx",
"args": [
"--from",
"cloud-audit",
"cloud-audit"
]
}
}
}
MCP Virustotal
{
"mcpServers": {
"burtthecoder-mcp-virustotal": {
"command": "npx",
"args": [
"-y",
"@burtthecoder/mcp-virustotal"
],
"env": {
"VIRUSTOTAL_API_KEY": "YOUR_VIRUSTOTAL_API_KEY_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_PORT": "YOUR_MCP_PORT_HERE",
"MCP_ENDPOINT": "YOUR_MCP_ENDPOINT_HERE"
}
}
}
}
Frequently asked questions
Cloud Audit is categorized under Security and uses a local stdio subprocess. MCP Virustotal belongs to Security and uses a local stdio subprocess. Pick Cloud Audit for security work and MCP Virustotal for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cloud Audit has no declared pricing — check the project's own site. MCP Virustotal is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gebalamariusz-cloud-audit and burtthecoder-mcp-virustotal as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloud Audit has a quality signal of 52/100 (Good) with 2 views, 0 installs and 72 GitHub stars. MCP Virustotal has 64/100 (Good) with 3 views, 0 installs and 150 GitHub stars.