About theHarvester MCP
theHarvester MCP wraps theHarvester to let AI agents collect publicly available domain-related OSINT. It is intended for prospecting, asset inventory, and authorized security research, with asynchronous harvests and retrievable results.
Key features
- 01Harvest public emails and hostnames
- 02Collect subdomains and IP addresses
- 03Run harvests across configurable sources
- 04Retrieve results by harvest ID
- 05List sources and active harvests
Use cases
- 01Find public business contacts for prospecting
- 02Inventory domains and related assets
- 03Research a domain for an authorized security assessment
MCP support
The MCP server exposes tools to run a domain harvest, retrieve past results, inspect active harvests, and list sources. It uses stdio transport and can run through the provided Docker image.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e THEHARVESTER_TIMEOUT -e THEHARVESTER_MAX_CONCURRENT docker.io/devkind/theharvester-mcp:1.0.0THEHARVESTER_TIMEOUTPer-harvest timeout in seconds (default 120)THEHARVESTER_MAX_CONCURRENTMaximum concurrent harvests (default 2)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEtheHarvester MCP Server: OSINT email and subdomain discovery for AI agents
theHarvester MCP Server wraps theHarvester in a Model Context Protocol server so Claude Code, Cursor, or any MCP client can harvest public emails, subdomains, hostnames, IPs, and LinkedIn profiles for a domain on demand. Multi-arch Docker image, stdio transport, no API keys for the default free sources.
It is built for lead generation and prospecting: ask your agent "find public contacts for
example.com" and it calls the harvest tool, which fans out to sources like crtsh,
hackertarget, urlscan, and DuckDuckGo, then returns structured JSON. Harvests run asynchronously
with configurable concurrency and timeouts, and results stay retrievable by harvest ID.
Quick start
docker pull devkind/theharvester-mcp
Add to .mcp.json (Claude Code) or your MCP client config:
{
"mcpServers": {
"theharvester": {
"command": "docker",
"args": ["run", "--rm", "-i", "devkind/theharvester-mcp"]
}
}
}
Then ask your agent: "Harvest example.com using free sources."
Install in your client
Requirements:
- Docker
- Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, or any other MCP client
- No API keys for the default free sources
Standard config works in most MCP clients:
{
"mcpServers": {
"theharvester": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"devkind/theharvester-mcp"
]
}
}
}
Claude Desktop
Follow the MCP install guide and add the standard config above to your claude_desktop_config.json.
Claude Code
Run:
claude mcp add theharvester -- docker run --rm -i devkind/theharvester-mcp
Or add the standard config above to .mcp.json in your project root.
Cursor
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> Add new MCP Server. Name it "theHarvester MCP", use command type with the command docker run --rm -i devkind/theharvester-mcp.
VS Code
Follow the MCP install guide and use the standard config above. You can also install with the VS Code CLI:
code --add-mcp '{"name":"theharvester","command":"docker","args":["run","--rm","-i","devkind/theharvester-mcp"]}'
Windsurf
Follow the Windsurf MCP documentation and use the standard config above.
Goose
Go to Advanced settings -> Extensions -> Add custom extension. Name it "theHarvester MCP", use type STDIO, and set the command to docker run --rm -i devkind/theharvester-mcp. Click "Add Extension".
LM Studio
Go to Program in the right sidebar -> Install -> Edit mcp.json. Use the standard config above.
Warp
Go to Settings -> AI -> Manage MCP Servers -> + Add to add an MCP Server. Use the standard config above, or use the slash command /add-mcp in the Warp prompt and paste it.
Tools
| Tool | What it does |
|---|---|
harvest | Run an OSINT harvest on a domain (sources: free, all, or comma-separated) |
get_harvest_results | Fetch a previous harvest by ID |
list_active_harvests | Show currently running harvests |
list_sources | List all available sources and which need API keys |
Seven sources work with no API key: crtsh, hackertarget, dnsdumpster, rapiddns, urlscan, otx, and duckduckgo. Sources like shodan, censys, and virustotal need keys configured in the theHarvester install.
Example call and output
Tool call: harvest with {"domain": "example.com", "sources": "free"}
{
"harvest_id": "a1b2c3d4",
"domain": "example.com",
"status": "completed",
"duration_seconds": 42.5,
"sources_used": ["crtsh", "hackertarget", "urlscan"],
"summary": {"emails": 3, "hosts": 27, "ips": 12, "linkedin": 2},
"emails": ["[email protected]", "[email protected]", "[email protected]"],
"hosts": ["www.example.com", "api.example.com", "mail.example.com"]
}
Output is illustrative; real counts depend on the target domain and source availability. The
harvest tool accepts domain (required), sources (free, all, or a comma-separated
list), limit, and timeout; invalid domains are rejected before any network call.
Configuration
Environment variables: THEHARVESTER_TIMEOUT (default 120s), THEHARVESTER_MAX_CONCURRENT
(default 2), THEHARVESTER_OUTPUT_DIR (default /app/output).
Responsible use
theHarvester collects only publicly published information, but OSINT tooling attracts scrutiny. Use this server only on domains you own or have written permission to research, and for lawful purposes such as security assessment, asset inventory, and business prospecting against public business contact data. Respect each source's terms of service and applicable privacy and anti-spam law (GDPR, CAN-SPAM, PECA) when acting on harvested contacts. The maintainers are not responsible for misuse.
Roadmap
- Official MCP Registry listing (
io.github.devkindhq/theharvester-mcp) - Docker MCP Registry, Smithery and Glama listings
- Pinned theHarvester version releases alongside
latest(devkind/theharvester-mcp:<version>is built with theHarvester 4.11.1,latesttracks the newest release) - CI workflow building and pushing the multi-arch image on tag (untested until the first tag)
License and contributing
MIT © Devkind. Issues and PRs welcome, see CONTRIBUTING.md and SECURITY.md.
Built by Devkind. Maintained by Kazim Ali.
Need OSINT and lead generation built into your stack?
Devkind builds custom MCP servers, AI agent workflows and commerce integrations. If you want this kind of harvesting wired into your CRM, enrichment or outreach tooling, talk to Devkind or email [email protected].
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.