osint-mcp-server
Related Servers
Alternatives to osint-mcp-server
- AlicenseAqualityBmaintenanceRomanian public data with no API keys: ANAF company status by CUI (VAT, fiscally inactive, deregistered), filed financial statements, Portal Just court cases and BNR exchange rates. Includes shop_check, which flags whether an online shop looks like a scam.6MIT
Related Servers
- AlicenseNot gradedqualityAmaintenancePassive external attack-surface mapping server that discovers subdomains, DNS records, TLS posture, HTTP headers, and registration data via public sources like CT logs, Shodan, and RDAP/WHOIS, enabling security reconnaissance without active scanning.82 npm1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables external reconnaissance activities including DNS enumeration, subdomain discovery, email security analysis, and SSL certificate inspection against a target domain.13-
- AlicenseAqualityFmaintenanceProvides comprehensive domain research tools including RDAP, WHOIS, and DNS lookup capabilities, with automatic fallback and support for 50+ TLDs.111 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform passive security scans on domains, checking email spoofing (DMARC/SPF/DKIM), TLS weaknesses, security headers, exposed files, and subdomain-takeover risk without needing an API key.762 npmMIT
- 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
- AlicenseNot gradedqualityBmaintenanceProvides DNS and network-reconnaissance tools that let agents run lookups for records, reverse DNS, ping, passive subdomain discovery, shared nameservers, geolocation, reverse IP, ASN, HTTP headers, subnet arithmetic and page links, plus key-gated WHOIS, MTR and traceroute. Responses are parsed into structured JSON with verbatim raw text, and it runs either through a hosted gateway or as a local stdio server.20 npmMIT
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes, but the aggregate recon_domain and investigate_site overlap in scope with several single-purpose tools. Descriptions explicitly guide the agent on when to use each, but the boundary between passive domain overview and active site investigation could still cause misselection.
Names mix noun_noun (domain_whois, dns_lookup), verb_noun (compare_domains, investigate_site), recon_ prefixes (recon_domain, recon_batch), and single words (subdomains, wayback). The set remains readable, but no single predictable convention governs all tools.
15 tools is well within a reasonable range for a domain OSINT server and each tool targets a distinct data source or operation (WHOIS, DNS, TLS, CT logs, Wayback, Shodan, ASN, etc.). No tool feels redundant or like padding.
The surface covers core domain OSINT needs: registration, DNS, email security, TLS, HTTP headers, certificate transparency, Wayback, IP ownership/routing, and Shodan ports. Minor gaps include no historical DNS lookup, no registrant-to-domain pivoting, and no active port scanning, but agents can largely work around these.