VirusTotal MCP Server
Related Servers
Alternatives to VirusTotal MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for security analysis using VirusTotal API, enabling AI assistants to analyze URLs, files, IP addresses, and domains with automatic relationship fetching.81-
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to interact with the VirusTotal API for malware analysis, URL scanning, and threat intelligence.81MIT

VirusTotal MCPofficial
AlicenseAqualityAmaintenanceOfficial VirusTotal MCP server for AI agents: threat intelligence, file analysis, and recovery through VTAI.11249 PyPI17Apache 2.0- AlicenseDqualityDmaintenanceA comprehensive MCP server providing tools for IP, domain, email, and image-based open-source intelligence. It integrates services like Shodan, VirusTotal, and HaveIBeenPwned to facilitate advanced security research and data gathering.5681 npmISC
- FlicenseNot gradedqualityDmaintenanceMCP server that checks URLs against the URLhaus malware database to identify malicious URLs.-

fluidattacks-mcpofficial
FlicenseNot gradedqualityDmaintenanceMCP server that provides tools for interacting with the Fluidattacks API-
TDQS
Scored across 11 tools
Each tool targets a distinct resource and action: reports for comprehensive data, relationships for specific paginated queries, collection retrieval, and search. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_domain_report, get_file_relationship, search_vt). The slight deviation for get_file_behaviour_summary is still clear and does not break consistency.
With 11 tools covering four entity types (domain, file, IP, URL) plus collection and search, the count is well-scoped for a read-oriented threat intelligence API—not too few, not excessive.
The set provides comprehensive coverage: for each entity there is a report and a relationship query, plus search and collection retrieval. Missing create/update/delete are expected for a read-only API; optional submission for URLs is handled.