OSINT MCP Server
Related Servers
Alternatives to OSINT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that exposes multiple OSINT tools to AI assistants like Claude, enabling sophisticated reconnaissance and information gathering tasks using industry-standard OSINT tools.241MIT
- FlicenseNot gradedqualityDmaintenanceMCP server to perform various OSINT tasks by leveraging common network reconnaissance tools.48-
- AlicenseNot gradedqualityCmaintenanceAn MCP server providing 15 OSINT tools over free, public sources for AI agents, enabling domain reconnaissance, subdomain discovery, DNS lookups, host profiling, CVE search, and more without API keys.MIT
- AlicenseAqualityBmaintenanceA local MCP server that gives AI clients OSINT tools to find public profiles, search the web, inspect pages, look up domains and Shodan services, and export sourced, timestamped findings without requiring API keys by default.8MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes a 60+ tool security and threat-intel stack to AI agents, enabling secret scanning, Sigma rule generation, ransomware lookup, OSINT, and deep research.1MIT
- FlicenseNot gradedqualityDmaintenanceAn OSINT tradecraft toolkit MCP server offering 31 tools for domain reconnaissance, email/identity research, threat intelligence, and web/social media analysis, plus 12 guided investigation prompt templates.-
TDQS
Scored across 56 tools
Most tools target distinct OSINT data sources or techniques, but there are clear overlaps like dns_lookup_direct/dns_lookup_passive/dns_enumeration and whois_lookup/whois_history that could cause confusion. The lack of descriptions exacerbates ambiguity, though many tools are clearly scoped to specific platforms or data types.
Naming follows a consistent snake_case pattern with mostly clear verb_noun or noun_verb structures. Minor inconsistencies exist like 'subdomain_enum' vs 'dns_enumeration' and 'quick_port_scan' vs 'shodan_host', but overall the convention is predictable and readable.
56 tools is excessive for a single server, creating cognitive overload and likely overlapping functionality. While OSINT is a broad domain, this count suggests poor scoping with many specialized tools that could have been consolidated into more general operations.
The toolset provides remarkably comprehensive coverage of OSINT techniques across domains, networks, social media, cryptocurrencies, and more. There are no obvious major gaps for an OSINT server, though the lack of descriptions makes it hard to confirm if all expected operations are truly covered.