Open-source OSINT agents, MCP servers, and investigation workflows.

Useful for

Useful for studying an end-to-end OSINT agent that lets an LLM request real tool output instead of inventing results.

OSINT relevance

Maps directly to username, email, breach, WHOIS, DNS, Shodan, VirusTotal, GitHub, and reporting workflows.

Useful for

Useful as a discovery map before choosing which MCP servers to connect to an investigation copilot.

OSINT relevance

Helps compare username, search, social, domain, and threat-intelligence MCP options in one place.

Useful for

Useful for controlled username research where public-source matches need to be reviewed by a human.

OSINT relevance

Fits the entity discovery phase, but results require careful false-positive handling.

Useful for

Useful as an example of packaging several existing OSINT utilities behind one MCP interface.

OSINT relevance

Shows the design tradeoff between convenience and the need for strict scope, rate, and safety controls.

Useful for

Useful for passive infrastructure visibility checks inside an agent workflow.

OSINT relevance

Supports domain, IP, exposed-service, and vulnerability context without adding active scanning.

Useful for

Useful for studying deterministic tool output for agent chaining without an LLM embedded inside the server.

OSINT relevance

Maps to collection, entity profiling, conflict detection, and document review stages.

Useful for

Useful for studying source gathering, synthesis, and report generation loops.

OSINT relevance

Maps to collection, source comparison, evidence summarization, and report draft generation.

Useful for

Useful as a simple reference implementation before building a heavier investigation copilot.

OSINT relevance

Shows breadth/depth controls, query generation, source processing, and final report generation.

Useful for

Useful for studying a modern research agent that can swap search and model providers.

OSINT relevance

Good architectural reference for iterative collection, source selection, and report assembly.

Useful for

Useful for studying multi-agent decomposition and resource lifecycle management.

OSINT relevance

Maps to investigation planning, tool selection, evidence gathering, and iterative refinement.

Useful for

Useful for human-in-the-loop investigation workflow design.

OSINT relevance

Focuses on evidence structuring, review gates, approval traceability, and correction handling.

Useful for

Useful for claim-level verification rather than asking an LLM for a single verdict.

OSINT relevance

Maps well to evidence verification, misinformation review, and report-ready claim breakdowns.

Useful for

Useful as a structured evidence and indicator-sharing backend for defensive investigations.

OSINT relevance

Gives an OSINT agent a mature event/IOC data model instead of a flat note store.

Useful for

Useful as a backend model for analyzer orchestration and repeatable enrichment pipelines.

OSINT relevance

Connects services such as VirusTotal, Abuse.ch, GreyNoise, URLScan, Shodan, OTX, MISP, and OpenCTI.

Useful for

Useful for adding defensive CTI enrichment to an investigation copilot.

OSINT relevance

Supports IOC context, indicator review, and report enrichment for defensive investigations.

Useful for

Useful for connecting a local or private OpenCTI knowledge base to an assistant.

OSINT relevance

Turns stored observables, reports, and relationships into queryable investigation context.

Useful for

Useful for teams that already store events, attributes, and IOCs in MISP.

OSINT relevance

Can expose structured indicator and event context to an analyst copilot.

Useful for

Useful when an agent needs consistent CTI lookups without opening several browser tabs.

OSINT relevance

Helps with source collection, IOC triage, and confidence-building across multiple feeds.

Useful for

Useful for turning investigation corpora into graph memory for question answering and synthesis.

OSINT relevance

Provides architectural ideas for entity extraction, relationship storage, and graph-guided summaries.

Useful for

Useful as the graph-backed case memory behind an investigation copilot.

OSINT relevance

Uses STIX-style relationships and observables that map well to entity and relationship analysis.

Useful for

Useful for converting collected OSINT material into entities and relationships.

OSINT relevance

Fits document intake, entity extraction, relationship analysis, and graph exploration.

Useful for

Useful for studying memory design around CTI entities, aliases, and offline investigation context.

OSINT relevance

Targets threat-actor alias resolution and graph-backed memory, both useful in entity-heavy investigations.

Useful for

Useful for turning public pages into structured material that an agent can cite or summarize.

OSINT relevance

Supports evidence collection and source text extraction when terms and robots rules allow it.

Useful for

Useful for semantic web discovery and source collection inside an agent.

OSINT relevance

Can help find sources, similar pages, and context for public web research.

Useful for

Useful when a research agent needs browser automation for public pages that are hard to fetch directly.

OSINT relevance

Fits controlled web collection and screenshot workflows, with explicit human oversight.

Useful for

Useful as a web-search and extraction layer for research agents.

OSINT relevance

Supports collection and source discovery, but conclusions still need human verification.

Useful for

Useful for studying actor-based collection pipelines and reusable extraction jobs.

OSINT relevance

Can support public-data collection, but every actor needs legal, terms-of-service, and scope review.

Useful for

Useful for studying investigation gates and task files rather than only autonomous tool calls.

OSINT relevance

Closely mirrors target, collection, entity resolution, relationship analysis, hypothesis, and reporting stages.