OhSINT MCP Server logo

OhSINT MCP Server

GetSomeKelso/OhSINT
0 starsUpdated 2026-05-31Community

Is this your server?

Add your score badge to your README and get your server in front of 45k+ builders a month.

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Enables AI assistants to orchestrate OSINT reconnaissance pipelines, including subdomain takeover detection, URL harvesting, secret scanning, and JS analysis, by chaining 73 tools with smart target detection and deduplication.

README.md

OhSINT — OSINT Reconnaissance Orchestrator

73 tools. 5 pipelines. One interface. CLI + MCP server.

Unified OSINT reconnaissance for authorized engagements. Wraps 73 tools behind smart target detection, parallel execution, deduplication, and multi-format reporting (JSON / Markdown / HTML). Runs on Kali Linux; connects to Claude Desktop/Code via an MCP server.

Pipelines

Five multi-stage pipelines chain tools with data flowing between stages:

| Pipeline | Command | What it does | |----------|---------|--------------| | Subdomain Takeover | ohsint takeover | subfinder + crt.sh → dnsx CNAME → provider filter → subzy + nuclei → cross-validate | | Historical URL Harvest | ohsint url-harvest | gau + waybackurls + waymore → dedupe → gf pattern match → robots.txt history | | Secret Surface | ohsint secret-surface | GitHub / Docker Hub / Postman search → TruffleHog + Gitleaks → cross-validate | | JS Analysis | ohsint js-analysis | subjs + katana → download → beautify → LinkFinder + SecretFinder → source maps → Swagger | | Full Passive | ohsint passive-full | chains all 4 above with cross-pipeline data flow |

Quick Start

# Install the CLI + MCP entry points
pip install -e . --break-system-packages

# Install all tool binaries (Kali VM — handles every install gotcha)
bash scripts/setup-kali.sh

# Verify tools, API keys, OPSEC config
ohsint install-check
ohsint opsec-check

# Run a pipeline
ohsint takeover -t example.com
ohsint passive-full -t example.com

# Multi-target / scope file
ohsint takeover --scope-file hackerone_scope.txt
ohsint takeover -t a.com -t b.com -t c.com

# Start the MCP server (see docs/mcp-setup.md for binding/IP)
ohsint-mcp --host <vm-ip>

OPSEC / Analyst Protection

Optional protection layer, configured in configs/opsec.yaml:

  • Request hygiene — User-Agent rotation, per-host rate limiting, cookie suppression on all direct HTTP calls
  • Proxy egress — optional SOCKS5/HTTP/Tor routing for tool subprocesses
  • Session isolation — random-suffixed output dirs so concurrent scans don't collide

Verify with ohsint opsec-check. For container-based isolation, see docs/kasm-deployment.md.

Authorization

Passive tools run freely. Active tools (httpx, naabu, shuffledns, interactsh, spiderfoot, recon-ng, xray, linkedin2username, linkedint) require --authorization. FCRA-gated commercial identity tools require --fcra-permissible-purpose.

Docs

API Keys

Configure in configs/api_keys.yaml (copy from configs/api_keys.yaml.example). Check status: ohsint api-keys.

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use AI & ML servers.