Darknet MCP
Related Servers
Alternatives to Darknet MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides AI agents with 37 OSINT tools and 12 data sources to perform unified reconnaissance, domain analysis, and attack surface mapping. It enables agents to query, correlate, and reason across platforms like Shodan, VirusTotal, and Censys in parallel.37364 npm60MIT
- AlicenseAqualityAmaintenanceEnables AI-driven open-source intelligence investigations by exposing 30 tools for scanning emails, usernames, domains, IPs, and more, with real subprocess execution.3155 PyPI9MIT
- FlicenseNot gradedqualityDmaintenanceProvides a unified interface for security analysts to gather threat intelligence from multiple sources including VirusTotal, Shodan, NVD, AnyRun, AlienVault OTX, and GitHub.6 npm-
- AlicenseAqualityCmaintenanceA comprehensive reconnaissance toolset that provides AI agents with 37 tools across 12 data sources like Shodan and VirusTotal for automated intelligence gathering. It enables agents to perform domain reconnaissance, attack surface mapping, and cross-platform data correlation within a single conversational interface.37364 npm2MIT
- AlicenseBqualityBmaintenanceEnables AI agents to perform general-purpose open-source intelligence lookups across domains, infrastructure, identity, social media, and threat/breach sources through a unified MCP interface, with most tools free and no API keys required.32MIT
- -licenseNot gradedqualityNot gradedmaintenanceExposes popular OSINT and reconnaissance tools like Sherlock, SpiderFoot, and Holehe through MCP and HTTP APIs for AI assistants. Runs security research tools in sandboxed environments and returns normalized JSON results for investigation and analysis.1-
TDQS
Scored across 68 tools
Many tools are clearly scoped by provider+artifact, but there is significant overlap within families: abuseipdb_check vs abuseipdb_reports vs abuseipdb_check_block, greynoise_ip vs greynoise_check, ransomwareGroups vs ransomwareGroup vs ransomlookGroups, and ransomwareRecent vs ransomlookRecent are easy to confuse. Descriptions help, but an agent must carefully pick between near-duplicate providers offering the same lookup.
Naming mixes snake_case (vulners_search, btc_address, otx_ip, tor_fetch_onion) with camelCase (threatfoxSearch, breachPassword, ransomwareGroup, urlhausLookup, bazaarHash) and provider prefixes are inconsistent (threatfox_ vs threatfox, breach_ vs breach, abuseipdb_ vs abuseipdb). This is a fairly chaotic surface with no single predictable pattern.
68 tools is far beyond a well-scoped set and reflects the sheer breadth of aggregated providers rather than a curated surface. The volume drives heavy redundancy (multiple tools per provider for essentially the same lookup), making the set unwieldy.
Coverage is broad and genuinely deep across the threat-intel domain: CVE/vuln, IP, domain, hash, URL, onion, Bitcoin, breaches, stealer logs, and ransomware are all represented, with a cross-source darknet_investigate aggregator and a readiness check. Minor gaps like no generic domain/WHOIS lookup or grouped risk scoring, but agents can work around them.