otinstaller · Username
Install user-scanner on Linux in one command
user-scanner takes a username or email and checks platforms that reveal whether an account exists. It groups results by category and ships an MCP server, so agents can call it too.
user-scanner in three lines
pipx install otinstaller
ot install user-scanner
ot run user-scanner -- u:jane_doeRuns kaifcodec/user-scanner (MIT, ★ 5k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What user-scanner is for
- One run for both a handle and the email behind it.
- Agent workflows: the same checks over MCP.
- A second source next to Sherlock and Holehe.
Typed inputs for user-scanner
otinstaller translates these prefixes into user-scanner's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- username ·
ot run user-scanner -- u:jane_doe - e:
- email ·
ot run user-scanner -- e:jane@example.com
Run every installed tool that takes the same input at once: ot run --all u:jane_doe
Where the results go
Every run lands under ./results/user-scanner/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff user-scanner <target>, and pull indicators out with ot extract.
Before you run it
- otinstaller never runs it with --allow-loud, which would notify the target.
Update, remove, inspect
ot info user-scanner # inputs, flags, keys
ot example user-scanner # sample output
ot update user-scanner # move to the next tested version
ot remove user-scanner # delete its virtualenvFull reference for this tool: docs for user-scanner.
Pairs with
When open-source isn't enough
user-scanner says which accounts exist. SearchIn's identity and leak providers return what those accounts reveal.
FAQ
user-scanner with otinstaller, answered
How do I install user-scanner on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install user-scanner. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.
Which inputs does user-scanner take through otinstaller?
u: (username), e: (email). otinstaller maps each prefix to user-scanner's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otinstaller save user-scanner results?
Under ./results/user-scanner/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff user-scanner <target> to compare the last two.
Does user-scanner need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.
Can I run user-scanner together with other tools?
Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including user-scanner. Save the combination as a playbook to repeat it.