io.github.OpenOSINT/openosint
Related Servers
Alternatives to io.github.OpenOSINT/openosint
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes 108+ omega-cli OSINT tools for reconnaissance, web analysis, threat intelligence, and reporting, enabling AI assistants to perform comprehensive open-source intelligence tasks.MIT
- 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.244MIT
- 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
- FlicenseNot gradedqualityCmaintenanceAn 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.-
- -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 20 tools
Several tools overlap in purpose: search_whois and search_rdap both return domain registration data, search_ip and search_ip2location both provide IP geolocation/ASN (the latter adding VPN/proxy detection), and generate_dorks vs search_dorks_live vs search_footprint all revolve around dork/search-engine queries. The detailed descriptions do help distinguish them (passive vs billable live SERP, entity-aware vs raw dorks), but an agent still faces real choices like 'which IP tool' or 'which registration lookup'. The graph_* tools and investigate_multi are cleanly separate.
Names are uniformly snake_case and mostly follow a search_<source> pattern (search_shodan, search_virustotal, search_censys) with a parallel graph_<action> family (graph_export, graph_neighbors, graph_review_candidates). Minor deviations exist: generate_dorks breaks the search_ prefix for a similar-purpose tool, and investigate_multi uses a different verb form, but overall the conventions are predictable.
At 20 tools this is on the heavy side, but each tool maps to a distinct external data source or graph operation, so the surface is mostly earned. The count is inflated slightly by near-duplicate integrations (ipinfo vs ip2location, whois vs rdap) that could be consolidated.
Coverage across IP reputation, breach, paste, WHOIS/RDAP, DNS, certificates, shodan/censys, GitHub, news geolocation, SERP footprint, plus a full graph export/traverse/human-review lifecycle and multi-target orchestration is broad and coherent. Gaps are minor: no dedicated social-media or phone-specific lookup tool (footprint only partially covers these), and no graph mutation/cleanup or report-export beyond NDJSON.