MCP / SOURCE-GROUNDED / READ-ONLY

A research teammate for the agentic security stack

Security knowledge
with receipts.

BlackBook turns scattered cybersecurity research into answers an AI agent can actually defend - indexed, ranked, and linked back to the exact source excerpt.

⌁26 SOURCESgrounded corpus
◌GRAPHevidence-linked
BlackBook terminal mark BLACKBOOK KNOWLEDGE MCP
blackbook serveLIVE
$ knowledge_search "kerberoasting"
8 results / 4 sources / citations intact→
Built for the agent loop
CLAUDECURSORVS CODEANY MCP CLIENT
NO EXECUTION◆NO INVENTED CITATIONS◆LOCAL-FIRST RESEARCH◆NO EXECUTION◆NO INVENTED CITATIONS◆LOCAL-FIRST RESEARCH◆

Security research is
everywhere. Answers are not.

One investigation can touch writeups, cheat sheets, standards, PDFs, and bug bounty reports. The signal is there - buried under tabs, duplicated evidence, and sources that refuse to agree.

FRAGMENTED

26 sources.
One question.

Knowledge lives across different formats, authorities, and naming systems.

01 - source sprawl
UNVERIFIED

Can you trace
the claim?

An answer without an exact excerpt is only a confident guess.

02 - citation debt
CONTEXT-POOR

Search results
lose the plot.

Lexical hits alone cannot connect a technique to the case around it.

03 - missing context
BLACKBOOK / HYBRID KNOWLEDGE SYSTEM

Every answer
has a trail.

BlackBook is not query → embedding → dump. It is a deliberate retrieval pipeline that keeps the corpus visible at every step.

Read the architecture ↗
01Filtermetadata + intent
02RetrieveFTS5 BM25 always on
03Enrichsemantic + graph
04Proveexact chunk citation
↳Semantic search is optional and local. The lexical backbone never disappears.FALLBACK SAFE

Signal over
search noise.

A research surface shaped for real investigations: diverse evidence, defensible answers, and a clean boundary between knowing and doing.

A1
⌕

Hybrid by default

SQLite FTS5 BM25 is the always-available backbone. Optional local semantic search catches paraphrased questions without sending embeddings away.

LEXICALSEMANTICRERANK
A2
◈

Provenance built in

Every result carries a reference that resolves through its chunk_id to the exact indexed text. BlackBook never fabricates a citation.

chunk_id→exact excerpt
A3
◎

Graph, not gate

Evidence-linked relationships enrich technique dossiers and similar-case results. The knowledge graph makes retrieval smarter without ever blocking it.

A4
⊘

Read-only by design

No command execution. No host scanning. No arbitrary URL fetching. BlackBook tells the agent what is documented - another MCP can handle action.

EXECUTION BOUNDARY / INTACT

Your agent asks.
BlackBook proves.

Connect through MCP over stdio - the client spawns BlackBook for you. Or run a long-lived streamable HTTP server when the whole team needs one shared research surface.

See setup snippets ↗
Claude Codestdio / auto-launched
CONNECTED
Cursorstdio / MCP config
↗
VS Codestdio / MCP config
↗
streamable-httpshared / optional

Install the
teammate.

BlackBook is a local-first Python MCP. Install it with uv or pip, copy the example config, ingest your sources, then let your MCP client launch the stdio server.

Full installation guide ↗
blackbook / quickstartPYTHON 3.10+
# clone the MCP
git clone https://github.com/Daniel-wambua/BlackBook.git
cd BlackBook

# recommended install
uv pip install -e .

# configure your local corpus
cp config.example.yaml ~/.blackbook/config.yaml

# ingest, then launch the MCP
blackbook ingest
blackbook serve
01pip fallbackpip install -e .Installs the blackbook and cyber-knowledge CLI entry points.
02optional semantic searchuv pip install -e ".[semantic]"Enables local sentence-transformer embeddings when configured.
03shared HTTP modeblackbook serve --httpRun a long-lived server at the configured MCP endpoint.

Wide enough
to cross-check.

26configured sources
enabled by default
HACKTRICKSMITRE ATT&CK0xdf WRITEUPSPORTSWIGGER ACADEMYGTFOBINSLOLBASOWASP WSTGPAYLOADSALLTHETHINGSBUGCROWD VRTHACKER101GITHUB SECURITY LABLOCAL PDFSHTB WRITEUPSWEBHACKLISTTHE HACKER RECIPESGOOGLE BUG HUNTERS

Report archives are labeled with unknown authority and treated as local research data - not official guidance.

Make the answer
defensible.

BlackBook keeps the honest parts of research visible: where the claim came from, how results were balanced, and what the corpus cannot answer.

“

Nothing is presented as fact unless it traces to an indexed source chunk.

12MCP tools
across search, graph, and context
2transport modes
stdio + streamable HTTP
0execution paths
read-only external surface
QUERY / KERBEROASTING↗
FTS5SEMANTICRERANKEDCITED
BLACKBOOK v0.9.0

One teammate.
Every source in view.

Search a technique. Pull the exact section. Walk the graph. Find the similar case. Keep the agent grounded while it reasons.

Read the README ↗
BlackBook terminal mark
BLACKBOOK / SIGNAL COREREAD-ONLY / LOCAL-FIRST
01Searchhybrid + intent-aware
02Sourceexact excerpt resolution
03Graphtechniques + cases
04Contextinvestigation packets

THE NEXT QUERY STARTS HERE

Do better research.
Leave a trail.

Open BlackBook on GitHub ↗