
OSINT Toolbox
io.github.renkagodPublished by GitHub account renkagodv1.1.0Updated Oct 24, 2026
Run Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more OSINT tools locally
The publisher's own server: osint.foundation
Overview
Runs classic OSINT tools locally — Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more — so an assistant can look up usernames, emails, domains,
- What you can do
- Search usernames and emails across sites with Sherlock, Maigret, Blackbird and Holehe, and pull public Google account data with GHunt (logged in). Gather domain intelligence with theHarvester, SpiderFoot, subfinder, dnstwist and dnsrecon. Look up WHOIS/RDAP, DNS records, certificate transparency hosts and Wayback snapshots with built-in tools. Scan phone numbers with PhoneInfoga and read local file metadata, including GPS, with ExifTool. Check which tools are installed and how to install missing ones.
- When to use it
- Useful for authorized security assessments, research on your own accounts or domains, and investigations that need many OSINT tools behind one assistant interface. Only installed tools are offered, so it adapts to what you have set up.
- Requirements
- Runs locally over stdio via uvx (Python, uv) or a Docker image. Individual tools must be installed, either with the built-in install command or by hand; SpiderFoot and Blackbird need git checkouts pointed to by OSINT_SPIDERFOOT_DIR and OSINT_BLACKBIRD_DIR, and ExifTool can be set with OSINT_EXIFTOOL. GHunt needs a one-time login. Network access is required; proxies can be set via HTTP_PROXY and related variables.
Installation
In SourceWeft
- Open OSINT Toolbox in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
osint-toolbox-mcp
[License: MIT] [CI] [PyPI] [Donate]
An MCP server that lets AI agents run classic OSINT tools on your own machine: Sherlock, Maigret, Blackbird, Holehe, GHunt, theHarvester, SpiderFoot, subfinder, dnstwist, dnsrecon, PhoneInfoga and ExifTool, plus built-in WHOIS, DNS, certificate transparency and Wayback Machine lookups. No API keys and no cloud service in between: the tools run locally and query public sources directly.
Ask your assistant "which sites have an account for [email protected]?" or "what can you find about example.com?", and it picks the tools, runs them and reads the results for you.
Features
Only installed tools are offered to the agent. Runs take from seconds to half an hour (a full SpiderFoot scan); requests run in parallel and can be cancelled.
Quick start
Pick one:
- Docker: every tool but Blackbird in one image, nothing else to install.
- uvx: one command installs the tools on your machine, without admin rights.
Docker
The image is large, so pull it once before adding the server; otherwise the first start can take longer than your client waits:
Add the server to your client:
Files for ExifTool, the GHunt login, API keys and proxies are covered in Docker details.
uvx
Install uv, then install the tools. This installs everything that is missing and checks that each tool starts; see Install the tools for what it does:
Add the server to your client:
To run the latest code from main instead of a release, use uvx --from git+https://github.com/renkagod/osint-toolbox-mcp osint-toolbox-mcp.
Connect your client
One-click install:
Claude Desktop: download osint-toolbox-mcp-<version>.mcpb from the latest release and open it. Claude Desktop installs it as an extension and asks for the optional SpiderFoot, Blackbird and ExifTool locations; the other tools are found on PATH. You can also paste the JSON above into Settings → Developer → Edit Config.
Claude Code:
Clients that read the mcpServers JSON above (paste it into the file):
Clients with their own format (shown with uvx; for Docker, use docker with the arguments run -i --rm ghcr.io/renkagod/osint-toolbox-mcp):
VS Code
Or in .vscode/mcp.json:
Codex CLI
Or in ~/.codex/config.toml, with a longer timeout for slow scans:
Zed
In settings.json:
Goose
In ~/.config/goose/config.yaml:
opencode
In opencode.json:
Continue
In .continue/mcpServers/osint-toolbox.yaml:
Install the tools
Skip this if you use Docker, unless you want Blackbird.
installs every tool that is missing, without admin rights, then checks that each one starts. uvx osint-toolbox-mcp --install sherlock maigret installs only the tools named. It needs uv and:
- puts each Python tool (Sherlock, Holehe, Maigret, GHunt, theHarvester, dnstwist, dnsrecon) in its own environment with
uv tool install, on Python 3.12: their dependencies conflict with each other, and some have no builds for newer Pythons. theHarvester and dnsrecon come from their latest GitHub releases; - downloads SpiderFoot and Blackbird from GitHub, each with its own virtual environment;
- downloads PhoneInfoga, subfinder and ExifTool and checks them against the checksums their authors publish. On macOS and Linux, ExifTool needs Perl, which those systems usually have.
Checkouts and downloads go to %LOCALAPPDATA%\osint-toolbox-mcp on Windows, ~/Library/Application Support/osint-toolbox-mcp on macOS and ~/.local/share/osint-toolbox-mcp on Linux; set OSINT_TOOLBOX_HOME to use another folder. The server looks there by itself. GHunt still needs a one-time ghunt login afterwards.
uvx osint-toolbox-mcp --check shows, at any time, every tool as ok, missing (with how to install it) or broken (found but fails to start). The agent can ask the same through the osint_toolbox_status tool.
Installing by hand
If a Python tool fails to build on your default Python, add --python 3.12 to its uv tool install.
SpiderFoot and Blackbird run from git checkouts. Give each its own .venv, which the server picks up automatically, and tell the server where the checkout is:
Then set OSINT_SPIDERFOOT_DIR to that folder in your client's config (env). Blackbird is the same with https://github.com/antoniaci/blackbird and OSINT_BLACKBIRD_DIR. SpiderFoot pins lxml<5, which has no builds for Python 3.13 and newer; to use a newer Python, apply patches/spiderfoot-requirements.patch first.
Configuration
All settings are environment variables, set in the env block of your client's config:
Besides PATH, the server looks in the --install folder and in the folders uv tool and pipx install into (~/.local/bin by default), which desktop apps often leave out of PATH.
Docker details
-
Blackbird is not in the image: it has no license that allows redistributing it. Install it yourself to use it.
-
ExifTool: the container sees only mounted files. Add
-v /path/to/files:/data:roto the arguments and ask about/data/photo.jpg. -
GHunt: log in once into a named volume, then mount it:
GHunt's listening mode (option 1) doesn't work in a container; pick option 2 (paste from the GHunt Companion extension) or 3 (an
oauth_token, see GHunt's README). -
API keys: theHarvester reads
/home/osint/.theHarvester/api-keys.yaml(mount your file there), PhoneInfoga reads its keys from environment variables (-e NAME=value). -
Proxy:
-e HTTPS_PROXY=http://host.docker.internal:8080, for example. -
Tags:
latestand version tags such as1.0.0for releases,edgefor the currentmain. Built for linux/amd64 and linux/arm64.
A full configuration:
Example requests
- "Which sites have an account registered to [email protected]?"
- "Search for the username jdoe_1987 with Sherlock and Maigret and compare what they find."
- "What subdomains and email addresses are public for example.com?"
- "Which lookalike domains of example.com are registered, and do any of them have mail servers?"
- "Who owns example.com and when does it expire? Show me how its homepage looked in 2015."
- "Read the metadata of /home/me/photo.jpg and tell me where and with what it was taken."
- "Run a passive SpiderFoot scan of example.com and summarize the findings."
Troubleshooting
- A tool is missing. Run
uvx osint-toolbox-mcp --install, or--checkto see why a tool isn't found (docker run --rm ghcr.io/renkagod/osint-toolbox-mcp --checkfor the image). After installing, restart your client so it lists the new tools. Desktop apps often start servers with a shorter PATH than your terminal; set the tool'sOSINT_*variable to its full path. - Long scans time out. Many clients stop waiting for a tool after a minute or so. Raise the limit where your client allows it:
MCP_TOOL_TIMEOUTin milliseconds for Claude Code,tool_timeout_secfor Codex CLI,timeoutin milliseconds on the server entry for Gemini CLI,timeoutin seconds for Goose. Otherwise ask for faster runs: apassiveSpiderFoot scan, Maigret withoutall_sites. - GHunt fails. It needs a valid login: run
ghunt login. When the saved session has been revoked,ghunt loginitself fails; runghunt login --cleanto delete it, thenghunt login. - Empty results, errors or captchas. Sites rate-limit and change their pages; retry later, lower the load, or go through a proxy. If a tool fails the same way outside the server, report it to that tool's project.
- Windows and
.bator.cmdwrappers. Arguments to such wrappers pass throughcmd.exe, so the server refuses inputs with characters like&or|; point theOSINT_*variable at the real executable instead.
Responsible use
These tools collect information about real people and organizations. Use them only where you have a lawful basis and authorization: your own accounts, security assessments within scope, research that respects privacy law (GDPR, CCPA and local equivalents) and the sites' terms of service. Don't use them to stalk, harass, dox or otherwise harm anyone. You are responsible for what you run and for what you do with the results.
Contributing
Issues and pull requests are welcome; see CONTRIBUTING.md. Report vulnerabilities privately as described in SECURITY.md. Changes are listed in the changelog.
Credits
The tools belong to their authors and keep their own licenses: Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot, Blackbird, PhoneInfoga, ExifTool. The server starts them as separate programs; the Docker image contains them unmodified.
This project started from frishtik/osint-tools-mcp-server (MIT).
Support
If this project is useful to you, you can support it with crypto: donation addresses.
License
Source: README.md at commit eb4eeb3
Tools
0Version history
1- v1.1.0LatestSep 23, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Osint integrations
osint.foundation
foundation.osintOfficial publisher
osint.foundation's hosted MCP server, published by osint.foundation; credential required; Streamable HTTP; 51 tools.

OSINT.SX
Published by GitHub account osintsx
Runs OSINT.SX people and account lookups from an assistant: one search across all sources, plus Google, Microsoft, Epic, X, Steam, Instagram and TikTok tools.

Domain Osint Mcp
Published by GitHub account robertoyanguas-ops
A remote MCP server that lets an assistant run domain OSINT checks: live DNS resolution, TLS certificate details and an HTTP security grade.

OSINT
Published by GitHub account robyroro
Local MCP server for OSINT-style domain and website investigations: recon, WHOIS/RDAP, DNS, certificates, archive and infrastructure comparison from public…

Robin: AI-Powered Dark Web OSINT
Published by GitHub account apurvsinghgautam
Robin runs dark web OSINT investigations over Tor, letting an assistant search onion search engines, scrape pages and save reports using the agent's own model.