mcp-osint

The mcp-osint server provides a centralized set of OSINT utilities that can be invoked as part of the MCP ecosystem. It exposes tools to perform WHOIS lookups, Nmap scans, DNS reconnaissance (dnsrecon, dig, and host), and domain permutation checks using dnstwist. In addition, there is a consolidated OSINT Overview tool that runs all of these tasks in parallel to give a quick, comprehensive snapshot for a target domain or host. You can trigger individual tools or the combined overview depending on your investigative needs, allowing for fast, repeatable OSINT workflows within the MCP framework.

Prerequisites:

• Node.js and npm installed on your system
• Access to install MCP servers via the Smithery CLI

Installation steps:

1. Ensure Node.js and npm are installed. You can verify with: node -v npm -v

2. Install the MCP OSINT server via the Smithery CLI (as shown in the README):

npx -y @smithery/cli install mcp-osint --client claude

3. Follow any additional prompts from Smithery CLI to complete the setup and connect with your MCP environment (Claude client in this example).
4. Start or configure your MCP runtime as required by your environment to load the mcp-osint server configuration.

Note: If you are deploying in a different environment (Docker, Python, etc.), adapt the commands to your platform using the recommended runtime for Smithery and the MCP server package name.

Tips and considerations:

• The server supports multiple OSINT tools; you can invoke individual tools (WHOIS, Nmap, DNS recon, DNSTwist, Dig, Host) or use the OSINT Overview to run them concurrently.
• Ensure the execution environment has the required OSINT tooling installed (e.g., whois, nmap, dnsrecon, dnstwist, dig, host) or that the Smithery/CLI runtime provides these tools in the execution image.
• When running sensitive or rate-limited queries (such as WHOIS or DNS lookups), be mindful of rate limits and terms of service.
• For Claude integration, the README suggests using a dedicated client setup; verify the client name and configuration in your MCP environment if you use a different client.
• If you need to customize environment variables (e.g., API keys for external services or proxies), add them under the env section in your MCP server configuration as needed.