Security & OSINT MCP Server
Related Servers
Alternatives to Security & OSINT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes read-only local analysis tools for source auditing, web traffic review, binary reverse engineering, exploit scaffolding, OSINT, and reporting via JSON-RPC over stdio, enabling LLMs to orchestrate evidence-based security workflows without executing targets or sending network requests.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search internet-connected devices, perform IP and hostname reconnaissance (open ports, banners, TLS certificates, DNS records), and retrieve CVE/CPE vulnerability intelligence including CVSS, EPSS, and KEV status. Supports both stdio and HTTP streaming transports and works with Claude Code, Codex, Gemini CLI, and Claude Desktop.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides safe, controlled access to network and system diagnostic tools including ping, nmap, dig, traceroute, curl, and whois for troubleshooting connectivity, scanning ports, and performing DNS lookups through whitelisted commands with security validation.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real network diagnostics on the local machine, including ping, traceroute, DNS lookups, TLS checks, and more.MIT
- 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.122 npmMIT
- FlicenseNot gradedqualityBmaintenanceExposes 21 tools over stdio that let any MCP-capable AI agent run real Kali-container security tools (nmap, nuclei, sqlmap, Metasploit), search a local 59,000+ CVE vulnerability database, and browse a 5,266-entry GitHub security tool index. Built-in guardrails refuse government, education, and military domains, and only whitelisted in-container executables can be invoked.3-
TDQS
Scored across 4 tools
Each tool targets a clearly distinct data source: DNS records, HTTP response headers, TLS certificates, and WHOIS registration data. There is no plausible scenario where an agent could confuse these four operations, and the argument names (domain/url/target) roughly mirror what each tool needs.
All names are snake_case with a subject-first convention (dns_, whois_, http_header_, ssl_cert_), which is predictable. The only minor deviation is the suffix style: 'lookup' (verb) vs 'inspector' (agent noun), though the intent is still obvious.
Four tools is a lean but coherent scope for a passive recon server, and each earns its place. It sits slightly on the thin side for a server branded 'Security & OSINT', which suggests a broader mandate than four lookups.
The core passive recon surface is covered: DNS, whois, TLS, and HTTP header auditing, which form a natural lifecycle for domain triage. Gaps exist for common recon needs such as subdomain enumeration, IP/ASN geolocation, or CVE/vulnerability lookup, but the essentials are present with no dead ends.