OTInstaller runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Oct 2026.
Install and run open-source OSINT tools in a local sandbox, asking before runs that touch a target.
What the code does
We read the source, 4 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
path := filepath.Join(out, name)
fmt.Fprintf(a.Err, "note: holding %s at %s; `ot update --all` leaves it there, `ot update %s` moves it to the latest version\n", inst.Ref, inst.Version, inst.Ref)
return subprocess.run(cmd, capture_output=True, text=True, timeout=timeout, env=env)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to OTInstaller
same job, measured the same wayLets your AI find open-source tools on GitHub and install them as sandboxed MCP tools.
One install that runs every sibling MCP server as a child process and merges their tools behind one
Local Windows MCP for Revit 2023-2027. Run the Windows installer before connecting a client.
Run Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more OSINT tools locally
Single exec tool running caller Python in a network-isolated locked-down sandbox.
Check what a repo would run on your machine (open, agent start, install) before you clone it.
Score and improve your AI coding agent setup. Local-only, open source.
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
OTInstaller — questions
Answers built from our own checks of this server.