OpenOSINT
v2.35.0 open-sourceThe section your link pointed to isn't on OpenOSINT's page any more, so we've brought you to the top.
OpenOSINT is an OSINT agent with 21 investigation tools behind a natural-language interface, plus an MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server so any MCP-compatible AI client can drive them.
uvx openosint web openosint censys 8.8.8.8 -t 30 export CENSYS_API_ID=your_api_id export CENSYS_SECRET=your_secret openosint censys example.com openosint search_email --target example.com --parallel openosint search_email --target example.com --json
Summary
OpenOSINT is an open-source (MIT) OSINT agent that wraps 19 investigation tools — email, username, breach, DNS, Shodan, and Google dork lookups among them — behind a natural-language AI interface, so an analyst can describe what they want investigated rather than chain commands by hand. It runs as a CLI or interactive REPL, and can also be launched as an MCP server or a browser web UI, with tool calls executed against real binaries rather than left to model output, which the README frames as ruling out hallucinated findings. Support for upstream HTTP/SOCKS5SOCKS5A proxy protocol that relays TCP and UDP traffic through an intermediary server without inspecting it, letting cyber tools tunnel connections through firewalls or pivot hosts with minimal overhead. proxies across its web-facing tools indicates ongoing development, with two releases in the tracked window and the latest 38 days old.
OpenOSINT is an OSINT agent with 21 investigation tools behind a natural-language interface, plus an MCP server so any MCP-compatible AI client can drive them.
How OpenOSINT helps
Which email address, username, or domain am I actually dealing with before I commit to investigating it?
takes a plain-language request, picks the matching tool from the set of 19, and runs the real binary against it — email recon, username search, or domain checks — returning findings from that execution rather than a model's guess
Has this IP or domain shown up as malicious anywhere before?
runs a Shodan lookup on the IP or a VirusTotal check on the domain through the wrapped binaries and reports back what those services actually return
What can I find about a target using search-engine exposure alone?
runs a live Google dork search against the target and returns the raw results, so the analyst doesn't have to hand-build the query syntax
Which platforms does this username appear on?
checks the username across services through its username-search tool and lists where it resolves, so an analyst can see the target's footprint without querying each site by hand
Can I run an investigation without exposing it to whoever's watching my network traffic?
routes the web-facing tools through an upstream HTTP or SOCKS5 proxy, so the lookups it performs go out through that proxy instead of directly
Do I need to touch a terminal to run one of these lookups?
offers the same tool set through a browser-based web UI in addition to the REPL, CLI, and MCP server, so the investigation can be launched by pointing and clicking instead of scripting
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for OpenOSINT, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail OpenOSINT puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What OpenOSINT connects to, runs on and detects, read from its release notes and docs. So far: 1 new integration.
1 change, tracked since Oct 9, 2026.
-
Oct 92026
new GDELT GKG feed integration
feat: keyless geolocated news for the globe (GDELT GKG feed) by @SonoTommy in https://github.com/OpenOSINT/OpenOSINT/pull/70
Other 1
Nothing first seen in this window. That doesn't mean OpenOSINT shipped nothing, only that we found no record of it.
How we count
Read from 5 of 13 release notes and docs updates we hold for OpenOSINT. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through OpenOSINT's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
13 entries
No entries match these filters.
- October 20265
- September 20262
- August 20262
- July 20261
- June 20261
- May 20262
Project health
Issue, contributor and maintainer activity in OpenOSINT/OpenOSINT, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 +5 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 93% of issues opened, last 12 months
- Median time to close 3.5 days first maintainer reply 5.2 hours
- Open backlog 11 of 14 issues ever filed
- Issues opened / month 2 · 0 communitymaintainers
- Open backlog 11
- Contributors / month 2
- Commits / month 20
- Stars 1,593
- bugs 14%
- features 7%
- other 79%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →