OTInstaller

com.otinstallerPublished by otinstaller.comv0.16.1Updated Oct 25, 2026

Install and run open-source OSINT tools in a local sandbox, asking before runs that touch a target.

The publisher's own server: OTInstaller Registry

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant install and run open-source OSINT tools in a local container sandbox, asking before any run that touches a target.

What you can do
  • Search the OTInstaller registry and install, update or remove OSINT tools
  • Run tools with typed inputs (username, email, domain, phone, IP, URL) and save each run's JSON results
  • Review past runs and get suggestions for what to run next on what a run found
  • Share a run's results as a link that works for 24 hours
  • Run bundled playbooks or auto-run every installed tool matching a target
  • Set up API keys for tools that need them, stored in the OS keychain
When to use it
Useful when an assistant should perform OSINT lookups on emails, usernames, domains, phone numbers, IPs or URLs using vetted open-source tools, without the user cloning repositories or managing Python environments.
Requirements
Runs as a local process on the user's desktop; the ot binary must be on PATH. Docker Desktop or Podman must be running, and cosign is optional for image signature verification. Some tools need API keys, set up via the CLI and kept in the OS keychain. Network access is needed for the registry and container images.
Before you install
Runs touch external targets and the assistant asks before such runs, but results are saved under ./results and can be shared via a 24-hour link. Telemetry counts installs and runs (tool, version, outcome, duration, engine, OS, architecture) and can be disabled with OT_NO_TELEMETRY or DO_NOT_TRACK. API keys are stored in the OS keychain. OSINT activity may have legal or ethical limits depending on the target.

Installation

In SourceWeft

  1. Open OTInstaller in the dashboard and add it to a workspace.
  2. 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

ot

ot is the OSINT package manager. One command installs, runs, updates or removes any tool in the OTInstaller registry, the largest registry built only for OSINT tools (over 130 of them). No more cloning repositories, fixing Python versions and learning each tool's flags: every tool takes the same typed inputs, runs in a container that can't read your files, and saves its result in the same JSON shape.

Get started

Put ot (or ot.exe) somewhere on your PATH. Tools run in containers, so Docker Desktop or Podman must be running; with cosign installed, ot also verifies each image's signature. Then set it up:

sh
ot start      # pick starter packs and tools, AI agents and settings, then installot doctor     # check Docker, cosign, the keychain and the registry

ot start asks at a terminal; ot start --tools <ns/name> --yes does the same from a script, and https://otinstaller.com/start builds the command for you.

Run tools

sh
ot search email                                        # tools that take an email addressot run osintverse-community/holehe e:[email protected]ot runs                                                # every run is saved under ./results; `ot runs <run-id>` shows oneot pivot <run-id>                                      # what to run next on what a run foundot share <run-id>                                      # a link to the run's results that works for 24 hours

Typed inputs fill the matching input of any tool: u: username, e: email, d: domain, p: phone, ip: IP address and url: URL. Or let ot pick: ot auto [email protected] runs every installed tool that takes an email address, and on a fresh machine offers to install a bundled playbook's tools first. ot playbook --list shows the playbooks. Tools that need an API key say so; ot keys setup walks you through them, and keys stay in your OS keychain.

Scripts, CI and AI agents

  • --json (or OT_OUTPUT=json) gives JSON output and one-line JSON errors on stderr, and ot never prompts without a terminal. See https://otinstaller.com/docs/automation.
  • ot mcp install claude (or claude-desktop, cursor, vscode, codex, gemini) adds ot's MCP server to your client. Agents ask you before any run that touches a target. See https://otinstaller.com/docs/agents.

Updates

ot outdated lists installed tools with newer versions and ot update --all installs them. ot self-update installs a new release of ot after checking its signature.

Telemetry

ot counts installs and runs of registry packages, so the registry can show which tools are used and which versions fail. A count carries the tool and its version, how a run ended and how long it took, the container engine, what started it (a command, CI or an AI agent), and your OS, architecture and ot version. It never carries your inputs, targets or results, file paths, run ids, case names, keys or tokens, and tools installed from a local manifest are never counted. The registry keeps daily totals only.

sh
ot telemetry                          # what is sent, and whether it is onot telemetry off                      # or set OT_NO_TELEMETRY=1 or DO_NOT_TRACK=1OT_TELEMETRY_DEBUG=1 ot run <tool> …  # print each count instead of sending it

Turning it off also stops the offer to report a failed run; DO_NOT_TRACK stops the daily update check too. Details: https://otinstaller.com/policy/privacy

Links

Docs: https://otinstaller.com/docs/getting-started · CLI reference: https://otinstaller.com/docs/cli · Bugs and ideas: https://github.com/OTInstaller/feedback/issues · Source: https://github.com/OTInstaller/otinstaller

Licensed under the Apache License 2.0 (LICENSE).

Source: cli/README.md at commit cd330f6

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

5
  1. v0.16.1LatestOct 25, 2026
  2. v0.16.0Oct 24, 2026
  3. v0.15.0Oct 23, 2026
  4. v0.14.0Oct 23, 2026
  5. v0.13.1Oct 21, 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 Otinstaller integrations

OTInstaller Registry

com.otinstallerOfficial publisher

OTInstaller Registry's hosted MCP server, published by otinstaller.com; no sign-in required; Streamable HTTP; 6 tools.

Streamable HTTPWeb executable
6 toolsOct 25, 2026