Agentic Detection Lookups MCP server
Commit Oct 16, 2026Enriches AI agents and SIEMs with structured detection context for LOLBAS, GTFOBins, and suspicious process relationships.
Also known as detection-forge/agentic-detection-lookups, agentic-detection-lookups
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Oct 16, 2026
- License
- Apache-2.0
What is Agentic Detection Lookups MCP?
Agentic Detection Lookups enriches AI agents and SIEMs with structured detection context for LOLBAS, GTFOBins, and suspicious process relationships. It exposes 6 tools, such as detection_lookup_binary, detection_check_parent_child, detection_list_by_category.
Summary generated from the project's README
About Agentic Detection Lookups MCP server
Agentic Detection Lookups provides structured security context for AI agents and SIEM platforms. It uses machine-readable CSV files to identify risky binaries and process behaviors, helping security professionals move away from complex regex matching. The server includes data for Windows LOLBAS binaries, Linux GTFOBins, and process parent-child relationship baselines.
Developers can deploy this as a local MCP server using Python to connect with AI clients like VS Code with GitHub Copilot. Once configured via stdio, an agent can query specific tools such as detection_lookup_binary or detection_check_parent_child to receive real-time risk scores and MITRE ATT&CK mappings. The system is designed for both real-time agentic reasoning and static enrichment within security tools like Splunk, CrowdStrike, Elastic, or Microsoft Sentinel.
What you can do with it
- 1Identify risky Windows binariesAsk an AI agent to determine if a specific Windows file is a known Living Off The Land binary.
- 2Analyze suspicious process relationshipsCheck if a specific parent and child process combination is considered unexpected or high risk.
- 3Enrich SIEM security logsUse lookup files to automatically add risk scores and MITRE technique IDs to process events in a SIEM.
- 4Browse binaries by attack techniqueRetrieve a list of binaries that map to a specific MITRE ATT&CK technique ID.
Written from the project's README. Every use case is checked against a quote from it.
Agentic Detection Lookups MCP tools 6
Detected from the READMEdetection_lookup_binarydetection_check_parent_childdetection_list_by_categorydetection_list_by_mitredetection_searchdetection_list_lookups
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabledetection-forge/agentic-detection-lookups is public and reachablegithub.com/detection-forge/agentic-detection-lookups ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-16github.com/detection-forge/agentic-detection-lookups ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubAgentic Detection Lookups
Machine-readable detection lookups for SIEM enrichment and AI agents. MCP-native.
Stop regex-matching 200+ binaries. Enrich in one
match()call.
Feed it to your SIEM, your SOAR, your agent, or your LLM.
What is this?
A collection of structured CSV lookup files purpose-built for:
- SIEM enrichment — one
match()/lookup/joinreplaces entire rule categories - AI agent tooling — MCP server included, agents query detection context in real-time
- Detection automation — consistent schema, CI-updated, deploy-ready
Lookup Files
| File | Entries | OS | Description |
|---|---|---|---|
lolbas_binaries.csv |
234 | Windows | Living Off The Land Binaries and Scripts — risk-scored, categorized, MITRE-mapped |
gtfobins.csv |
477 | Linux | GTFOBins Unix binaries — shell escape, priv-esc, file ops, MITRE-mapped |
parent_child_baselines.csv |
98 | Both | Expected/suspicious process parent→child relationships for Windows and Linux |
Schema Contract
Every lookup file follows:
- First column = match key (the field you join on)
- Always includes
riskorrisk_if_unexpectedcolumn - Always includes MITRE ATT&CK technique mapping
- No nested data — flat columns, pipe-delimited for multi-value
- UTF-8, no BOM, Unix line endings, header row always present
Quick Start
SIEM (copy-paste)
CrowdStrike NG-SIEM:
#event_simpleName=ProcessRollup2
| binary := lower(FileName)
| match(file="lolbas_binaries.csv", field=binary, column=filename, include=[categories, mitre_ids, risk])
| risk="high"
Splunk:
index=crowdstrike event_simpleName=ProcessRollup2
| rex field=FileName "(?<binary>[^\\\\]+)$"
| lookup lolbas_binaries.csv filename AS binary OUTPUT categories mitre_ids risk
| where risk="high"
Elastic (ES|QL):
FROM logs-endpoint.events.process-*
| WHERE event.action == "start"
| ENRICH lolbas-policy ON process.name = filename WITH categories, risk
| WHERE risk == "high"
Microsoft Sentinel:
DeviceProcessEvents
| extend binary = tolower(FileName)
| join kind=inner (_GetWatchlist('lolbas_binaries')) on $left.binary == $right.filename
| where risk == "high"
See queries/ for full query libraries per platform.
MCP Server (AI agents)
{
"servers": {
"detection-lookups": {
"type": "stdio",
"command": "python",
"args": ["-m", "mcp_server"],
"cwd": "/path/to/agentic-detection-lookups"
}
}
}
Then your agent can:
→ detection_lookup_binary("certutil.exe")
← {source: "lolbas", risk: "medium", categories: ["Download"], mitre_ids: ["T1105"]}
→ detection_lookup_binary("python")
← {source: "gtfobins", risk: "high", categories: ["shell", "reverse-shell", ...], mitre_ids: ["T1059"]}
→ detection_check_parent_child("winword.exe", "cmd.exe")
← {expected: false, risk_if_unexpected: "critical", mitre_id: "T1204.002"}
MCP Tools
| Tool | Input | Output |
|---|---|---|
detection_lookup_binary |
filename | Risk, categories, MITRE IDs, source (lolbas/gtfobins) |
detection_check_parent_child |
parent, child, os_filter | Expected/suspicious, risk level, triage guidance |
detection_list_by_category |
category, limit, offset | Paginated binaries in that abuse category (cross-platform) |
detection_list_by_mitre |
technique_id, limit, offset | Paginated binaries mapped to that technique (cross-platform) |
detection_search |
query, limit | Matches across all lookup data with total/has_more |
detection_list_lookups |
— | All files with row counts and columns |
Data Sources
| Lookup | Source | Update Frequency |
|---|---|---|
| LOLBAS binaries | LOLBAS Project | Weekly (automated) |
Installation
Prerequisites
- Python 3.10+
- VS Code with GitHub Copilot (for MCP integration)
Install
git clone https://github.com/detection-forge/agentic-detection-lookups.git
cd agentic-detection-lookups
python -m venv .venv
# Windows:
.venv\Scripts\activate
# Linux/macOS:
source .venv/bin/activate
pip install -e .
Configure MCP Client (VS Code)
Add to your VS Code User settings (Ctrl+Shift+P → "Preferences: Open User Settings (JSON)") or ~/.vscode/mcp.json:
{
"servers": {
"detection-lookups": {
"type": "stdio",
"command": "/absolute/path/to/.venv/bin/python",
"args": ["-m", "mcp_server"],
"cwd": "/absolute/path/to/agentic-detection-lookups"
}
}
}
Windows example:
{ "servers": { "detection-lookups": { "type": "stdio", "command": "C:\\Code\\.venv\\Scripts\\python.exe", "args": ["-m", "mcp_server"], "cwd": "C:\\Code\\agentic-detection-lookups" } } }
Reload VS Code: Ctrl+Shift+P → "Reload Window"
Verify
In Copilot Chat (Agent mode):
Is certutil.exe a LOLBAS binary?
✅ Returns risk, categories, and MITRE mappings = working!
Run standalone (CLI)
detection-lookups
This starts the MCP server on stdio transport (useful for piping JSON-RPC or connecting other MCP clients).
Upload to your SIEM
- CrowdStrike NG-SIEM: Upload via API or UI (Settings → Lookup Files)
- Splunk: Settings → Lookups → Lookup table files → Add new
- Elastic: Create enrich index + ingest pipeline
- Sentinel: Configuration → Watchlist → Add new
Project Structure
agentic-detection-lookups/
├── lookups/ # The data (CSV files)
│ ├── lolbas_binaries.csv
│ ├── gtfobins.csv
│ └── parent_child_baselines.csv
├── queries/ # Copy-paste detection queries
│ ├── crowdstrike_ngsiem.md
│ ├── splunk.md
│ ├── elastic.md
│ └── microsoft_sentinel.md
├── mcp_server/ # MCP server for AI agents
│ ├── server.py
│ └── __init__.py
├── scripts/ # Update/maintenance scripts
├── LICENSE # Apache 2.0
├── NOTICE
└── pyproject.toml
Contributing
PRs welcome. See CONTRIBUTING.md for guidelines.
To add a new lookup file:
- Follow the schema contract (match key first, include risk + MITRE columns)
- Include at least one query example per SIEM platform
- Add a tool to the MCP server
License
Apache 2.0 — See LICENSE and NOTICE.
Built by Gene Kazimiarovich | Part of Detection Forge
Agentic Detection Lookups MCP questions
What tools does Agentic Detection Lookups MCP provide?
It exposes 6 tools, including detection_lookup_binary, detection_check_parent_child, detection_list_by_category, detection_list_by_mitre, detection_search.
Can I use this with my SIEM?
Yes, the lookup files are designed for SIEM enrichment in platforms like CrowdStrike NG-SIEM, Splunk, Elastic, and Microsoft Sentinel.