Tour
What you can do
Six things, each one command. Install ot first with the quick start; Docker Desktop or Podman has to be running.
01 · Tools
Run one tool against one value
Paste what you have on the home page, pick a tool, copy its command. The first run installs it after asking once; every run is saved under ./results/ as the same JSON envelope.
ot run osintverse-community/holehe e:ada@example.com --format table02 · Guides
Follow an investigation playbook
Guides are step-by-step methods written by investigators, versioned like tools, with every tool they use installable in one command. Read them here or in your terminal.
ot guide tools osintverse-community/email-investigation03 · Playbooks
Run a set of tools at once
A playbook is a named list of tools run against the same value, a few at a time, with one summary table. Two are bundled; put your own under ./playbooks/.
ot playbook domain-recon d:example.com -y04 · Auto
Run everything that takes what you have
ot auto guesses the type of a value (email, domain, IP, phone, URL, else username) and runs every installed tool that takes it. ot extract then lists the indicators found across the runs.
ot auto example.com05 · Agents
Let an AI agent run the tools, with your consent
ot mcp is a Model Context Protocol server built into ot. Claude, Cursor, VS Code and others can search the registry, install tools and run them; anything that goes online or touches a target asks you first, and every run is in a local audit log.
ot mcp install claude06 · Publish
List your own tool or guide
Import a repository: the registry drafts the manifest and opens a pull request. Push a tag to release; the registry validates, scans, reviews new publishers once, and backs up every release.
ot import https://github.com/you/your-tool
What keeps it safe
- Pinned and signed. Every image is pulled by digest and its signature checked before it runs; a wheel is checked against its hash.
- Scanned and reviewed. Every release is scanned for vulnerabilities, secrets and malware and run once in the sandbox; a person reviews each new publisher's first release.
- Sandboxed. Tools run read-only, as a non-root user, with no host folders, no capabilities, a memory cap, and no network unless the manifest declares it.
- Backed up. The registry keeps a copy of every published image, wheel and repository, so a takedown elsewhere does not break your installs.