OTInstaller MCP server
com.otinstaller/ot·v0.16.1Install and run open-source OSINT tools in a local sandbox, asking before runs that touch a target.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed OTInstaller yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
OTInstaller tools
No tool declarations could be read from the package source. They show once the server is installed.
How OTInstaller compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 90/100
- higher than 83% of 48,255 servers
Release history: 3 versions in the registry since 2026-10-23, latest 2026-10-24, typically one every 1 day.
Install OTInstaller in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the OTInstaller repository's README, as published. We do not edit it. Read it on GitHub
OTInstaller Registry
A free, public registry of OSINT tools and guides, and ot, the CLI that installs and runs them. This repository holds weeks 1–7 of the plan: the manifest spec, the ot CLI, the registry API's read side, publishing intake (GitHub/GitLab sign-in, the GitHub App webhook, the queue that validates tagged releases), and security scans with the review queue (scanner, verdicts, publishing, reviewer decisions, emails), and GitLab support with sync (connecting GitLab projects, GitLab webhooks and CI templates, and a poller that catches missed tags, renames, archiving and deleted repositories), and the import wizard (detecting what a repository contains, drafting its manifest, opening a pull or merge request, registry-held manifests, and bulk imports of up to 50 repositories), and source and artifact backups (week 11: the image mirror at mirror.otinstaller.com, wheel and git bundle copies in R2, ot's fallback to them, Restore from backup, and a monthly restore drill). To connect real GitHub and GitLab apps, follow docs/publishing-setup.md.
It also holds otlite, the no-Docker edition: a Python CLI (from OSINTVerseHQ/OTinstaller, imported with its history into otlite/, called otinstaller until 1.0) that installs tools from pip or git into per-tool virtualenvs on Linux. Its tool catalog has also been converted into registry packages (see otlite (otlite/)). Moving between the two: docs/migrating-from-otinstaller.md.
Requirements
- Go 1.25+ (for the CLI)
- Node.js 22+ (for the API)
- Docker Desktop or Podman (to run Docker tools and sandboxed pipx tools)
CLI
cd cli
go test ./...
go build -o ../bin/ot ./cmd/ot
../bin/ot validate ../spec/fixtures/valid/docker-tool.yamlShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
OTInstaller: common questions
- Is OTInstaller MCP server safe?
- Yes, by our scan: it is graded A (90/100). Read the OTInstaller safety report
- Does OTInstaller need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is OTInstaller maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v0.16.1.