Erlik Graph

An OSINT link-analysis graph with one shared transform core and two front-ends: a visual FastAPI + Cytoscape app and an MCP server for LLM-driven investigation.

🇩🇪 Deutsche Version

Part of the Erlik portfolio of open-source AI OSINT tools.

Overview

Erlik Graph implements the classic link-analysis workflow — Entities (nodes) connected by Transforms (functions that take one entity and return related ones) on an interactive Graph — as a small, hackable Python project.

The point is the architecture: transform logic is written once as plain Python functions and exposed through two adapters that share the same graph store:

• FastAPI + Cytoscape — a visual, clickable investigation graph. You drive it, every step is deterministic and auditable.

• MCP — the same transforms as tools an LLM agent (e.g. Claude) calls autonomously to enrich and follow leads.

Add a transform once, and it appears in both.

Related MCP server: maltego-mcp

Features

• 🔗 Entity/Transform/Graph model with automatic node de-duplication

• 🧩 13 transforms out of the box — DNS (A/MX/NS/TXT), reverse DNS, certificate-transparency subdomains (crt.sh), RDAP/WHOIS, Wayback Machine, IP geolocation, HIBP breaches, Gravatar, Shodan services, username enumeration across 10 platforms

• 🖥️ Visual graph front-end (Cytoscape.js), click a node → run applicable transforms → the graph grows

• 🤖 MCP adapter exposing every transform as a tool for LLM-driven OSINT

• ♻️ Shared core — one @transform decorator, both adapters pick it up automatically

• 🔌 Pluggable storage — in-memory networkx by default, or a shared Neo4j backend so the MCP and FastAPI adapters read/write the same graph (Claude enriches, you inspect it live in the browser)

Prerequisites

• Python 3.11+

• Optional: a SHODAN_API_KEY for the Shodan transform and a HIBP_API_KEY for the breach transform

• Optional: a running Neo4j instance to share one graph across both adapters

Installation

git clone https://github.com/malkreide/erlik-graph.git
cd erlik-graph
python -m venv .venv
# Windows: .\.venv\Scripts\Activate.ps1   |   Unix: source .venv/bin/activate
pip install -r requirements.txt

Usage

Variant A — visual graph (FastAPI)

python -m uvicorn erlik_graph.adapters.api_server:app --reload

Open http://127.0.0.1:8000 → add a seed entity → click a node → run a transform → the graph expands.

Variant B — MCP (LLM-driven)

Register the server (see .mcp.json) with your MCP client. The transforms appear as tools (domain_to_subdomains, username_to_profiles, get_graph, …) and the agent decides which leads to follow.

{
  "mcpServers": {
    "erlik-graph": {
      "command": "python",
      "args": ["-m", "erlik_graph.adapters.mcp_server"],
      "cwd": "/path/to/erlik-graph"
    }
  }
}

Configuration

Shared graph via Neo4j

By default each process keeps its own in-memory graph, so the MCP and FastAPI adapters don't see each other's data. Point both at Neo4j to share one graph — the intended "Claude enriches, you inspect visually" loop:

export ERLIK_GRAPH_BACKEND=neo4j
export NEO4J_URI=bolt://localhost:7687
export NEO4J_USER=neo4j
export NEO4J_PASSWORD=your-password

# Adapter 1 — the LLM enriches through MCP
python -m erlik_graph.adapters.mcp_server
# Adapter 2 — you watch the same graph grow in the browser
python -m uvicorn erlik_graph.adapters.api_server:app --reload

Swap in a different store by subclassing BaseGraphStore and returning it from create_store().

Adding a transform

1. Write a function decorated with @transform(name, input_type, description) in a file under erlik_graph/transforms/.

2. Import that file in erlik_graph/transforms/__init__.py.

It now appears in both adapters automatically.

@transform("domain_to_ipv4", "domain", "Resolves a domain to its IPv4 addresses.")
def domain_to_ipv4(value: str, properties: dict) -> list[Entity]:
    return [Entity(type="ipv4", value=ip, link_label="resolves_to")
            for ip in query(value, "A")]

Project Structure

erlik_graph/
├── core/                 Data model, registry, graph stores
│   ├── entity.py         Entity / Edge, de-dup key
│   ├── registry.py       @transform decorator + registry
│   ├── base_store.py     BaseGraphStore — shared expand() logic
│   ├── graph_store.py    in-memory networkx store
│   ├── neo4j_store.py    shared Neo4j-backed store
│   └── factory.py        create_store() — picks backend from env
├── transforms/           the actual logic — this is where the system grows
│   ├── dns_transforms.py
│   ├── rdns_transforms.py
│   ├── crtsh_transforms.py
│   ├── whois_transforms.py
│   ├── wayback_transforms.py
│   ├── geo_transforms.py
│   ├── breach_transforms.py
│   ├── gravatar_transforms.py
│   ├── shodan_transforms.py
│   └── username_transforms.py
├── adapters/
│   ├── api_server.py     FastAPI endpoints
│   └── mcp_server.py     MCP tools
└── web/index.html        Cytoscape front-end

tests/                    offline pytest suite (run in CI)
.github/workflows/ci.yml  install + import check + pytest on 3.11 / 3.12

The Erlik Portfolio

Erlik — named after the lord of the underworld in Turkic-Mongolic (Tengrist) mythology — is a growing family of small, focused, open-source AI OSINT tools. Each tool lives in its own repository and shares the erlik topic for discoverability. erlik-graph is the link-analysis flagship; further tools (scouts, enrichers, monitors) join the portfolio as separate repos.

Legal Notice

For use only against systems and data you are authorized to investigate. When aggregating personal data, comply with the GDPR and applicable law.

Changelog

See CHANGELOG.md.

License

MIT License — see LICENSE.

Author

Hayal Özkan · @malkreide