Google Threat Intelligence MCP Server
Related Servers
Alternatives to Google Threat Intelligence MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables LLM agents to access Google Threat Intelligence data, including IOC search, file/domain/IP/URL analysis, and threat hunting rulesets, for security investigations.36Apache 2.0
- AlicenseDqualityDmaintenanceEnables AI assistants to access real-time threat intelligence, malware sample metadata, and security analysis tools via integration with MalwareBazaar, VirusTotal, and Telegram.29MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-powered threat intelligence analysis of IPs, domains, URLs, and file hashes across multiple threat intelligence platforms (VirusTotal, AlienVault OTX, AbuseIPDB, IPinfo) with APT attribution and interactive reporting through natural language queries.17 PyPI39Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and manage OpenCTI threat intelligence data, including indicators, observables, reports, malware, and more, with read-only and optional write operations.MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time threat intelligence for AI agents, enabling checks on IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill/MCP-tool definitions against a free database of 890K+ IOCs.-

REMnux MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to execute malware analysis tools on a REMnux system via Docker, SSH, or local connections. It provides automated file-type analysis, structured tool discovery, and security guardrails for streamlined malware investigation.121,501 npm119GPL 3.0
TDQS
Scored across 36 tools
Tools like search_threats, search_campaigns, search_threat_actors, search_malware_families, search_software_toolkits, search_threat_reports, and search_vulnerabilities overlap heavily; the latter six are essentially wrappers around the first with a collection_type filter. While descriptions clarify the differences, the generic search_threats can also do the same, which may lead to confusion about which to use for a specific request.
The naming pattern is mostly consistent: 'get_*_report', 'get_entities_related_to_*', 'search_*'. However, there are slight deviations like 'analyse_file' (British spelling) versus 'analyze' elsewhere, and 'create_collection' vs 'update_collection_attributes' but these are minor and the overall convention is clear.
With 36 tools, the server is on the heavier side, reflecting a broad threat intelligence API. The many search_* wrapper tools (7 variants) contribute bloat; they could be consolidated into a single search with a type parameter. The get_entities_related_* tools also repeat the same pattern for each entity type, adding to the count. While the scope is large, the number feels excessive and could be trimmed.
The tool surface covers major threat intelligence capabilities: searching and retrieving collections, entities, reports, timelines, MITRE attribution, collection management (CRUD), and IOC pivoting. However, there are gaps like no direct creation/update for IOCs beyond collections, and no functions for managing threat profiles (only retrieval). Overall, the domain is well covered, but some advanced operational features are missing.