OhSINT MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OhSINT MCP ServerRun full passive OSINT scan on example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| subfinder + crt.sh → dnsx CNAME → provider filter → subzy + nuclei → cross-validate |
Historical URL Harvest |
| gau + waybackurls + waymore → dedupe → gf pattern match → robots.txt history |
Secret Surface |
| GitHub / Docker Hub / Postman search → TruffleHog + Gitleaks → cross-validate |
JS Analysis |
| subjs + katana → download → beautify → LinkFinder + SecretFinder → source maps → Swagger |
Full Passive |
| chains all 4 above with cross-pipeline data flow |
Related MCP server: BugBounty MCP Server
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
Tool reference: docs/tools.md
MCP setup & Kali install: docs/mcp-setup.md
Deployment gotchas: tasks/lessons.md
Usage guidelines & tool chaining: CLAUDE.md
API Keys
Configure in configs/api_keys.yaml (copy from configs/api_keys.yaml.example). Check status: ohsint api-keys.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GetSomeKelso/OhSINT'
If you have feedback or need assistance with the MCP directory API, please join our Discord server