NeuralReaper
Aggregates security news from RSS feeds (The Hacker News, BleepingComputer, SecurityWeek) for threat intelligence updates.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NeuralReaperscan example.com for open ports and vulnerabilities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
███╗ ██╗███████╗██╗ ██╗██████╗ █████╗ ██╗
████╗ ██║██╔════╝██║ ██║██╔══██╗██╔══██╗██║
██╔██╗ ██║█████╗ ██║ ██║██████╔╝███████║██║
██║╚██╗██║██╔══╝ ██║ ██║██╔══██╗██╔══██║██║
██║ ╚████║███████╗╚██████╔╝██║ ██║██║ ██║███████╗
╚═╝ ╚═══╝╚══════╝ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚══════╝
██████╗ ███████╗ █████╗ ██████╗ ███████╗██████╗
██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔════╝██╔══██╗
██████╔╝█████╗ ███████║██████╔╝█████╗ ██████╔╝
██╔══██╗██╔══╝ ██╔══██║██╔══██╗██╔══╝ ██╔══██╗
██║ ██║███████╗██║ ██║██║ ██║███████╗██║ ██║
╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝AI-Native Security Research Platform — Claude × MCP × Real Offensive Tooling
Natural language in. Real recon, real CVE matches, real AD attack paths, real crypto posture out.
Table of Contents
Related MCP server: Pentester-MCP
Why NeuralReaper
Most "AI + security" demos wire a chatbot up to a single API and call it a day. NeuralReaper instead gives Claude direct, sandboxed execution access to a real offensive security toolchain — the same binaries a human pentester would run from a terminal — through the Model Context Protocol.
The result: you describe an objective in plain English, and Claude plans and executes the actual recon — choosing tools, chaining scans, and reasoning over real output — instead of guessing from training data.
What makes it worth putting on a resume rather than just a script:
**A live, auto-updating vulnerability intelligence engine. NeuralReaper synchronizes vulnerability data from sources such as NVD and CISA KEV into a local intelligence database, allowing AI workflows and scanning modules to operate with current vulnerability context. Nuclei templates provide additional detection coverage through continuously maintained community research.
Isolated by design. Every tool runs inside a locked-down, non-root Ubuntu container — never on the host.
A real engineering trail. Built across Windows + WSL2 + Docker Desktop + Claude Desktop, hitting (and solving) the exact integration failures documented below instead of glossing over them.
Breadth across the full modern assessment surface — network/web recon, Active Directory attack-path enumeration, cryptographic/post-quantum posture, supply-chain dependency auditing, and local fuzzing — not just a wrapper around one scanner.
Design Philosophy — Detection, Not Weaponization
Comparable AI-agent pentest frameworks exist, and some — most notably HexStrike AI — ship an automated exploit-generation layer on top of recon/scanning. Within hours of HexStrike's public release, researchers observed threat actors discussing how to weaponize it against a Citrix NetScaler zero-day (CVE-2025-7775), compressing what used to take days of manual exploit development into roughly 10 minutes.
NeuralReaper deliberately stops one step earlier. Every tool here identifies, enumerates, and reports — it does not generate exploit payloads, and it never will. The CVE watchlist is lookup-only: it calls existing Nuclei templates and ExploitDB entries for matches, writing zero new detection or exploitation logic of its own.
That's a constraint, not a missing feature — and worth saying explicitly: building security tooling with an eye on how it could be misused is itself a skill.
Architecture
Claude Desktop spawns the container per-session over stdio — there is no persistent network listener, no exposed port, and no state retained between runs beyond what Docker itself caches (e.g. Nuclei's template directory) and the in-memory session log used by generate_report().
🧠 Real-Time Threat Intelligence
NeuralReaper includes a built-in Threat Intelligence Engine that continuously aggregates and maintains a local database of vulnerability intelligence from trusted public sources. This enables AI agents and security researchers to work with up-to-date information during reconnaissance, vulnerability assessment, and exploitation planning without relying on manual searches.
Sources
National Vulnerability Database (NVD)
CISA Known Exploited Vulnerabilities (KEV)
The Hacker News
BleepingComputer
SecurityWeek
ProjectDiscovery
Capabilities
Automatic CVE synchronization
Security news aggregation via RSS
CISA KEV monitoring
Local threat intelligence database
AI-accessible intelligence queries
Continuous intelligence updates through MCP
MCP Commands
threat_intelligence_update()Synchronizes the latest intelligence from all configured sources and updates the local threat intelligence database.
threat_intelligence_status()Displays the current intelligence database status, including the last synchronization time, the number of tracked security articles, and the total number of indexed CVEs.
Example output:
Status:
Last updated: 2026-07-23 07:21 UTC
RSS articles tracked: 75
Total CVEs in DB: 1,703## GhostInShell — Adversary Emulation Engine
GhostInShell is NeuralReaper v2.0's adversary emulation module. It simulates multi-stage attack chains based on real-world CVEs and TTPs, generating detection artifacts for blue team training and validation.
### What GhostInShell Does
| Capability | Output | Purpose |
|------------|--------|---------|
| **Attack Surface Analysis** | Prioritized list of potential attack vectors | Recon planning for authorized engagements |
| **Exploit Chain Simulation** | Graph-optimized sequence of simulated exploits | Purple team exercise planning |
| **IOC Generation** | File paths, registry keys, network indicators | Detection rule development |
| **MITRE ATT&CK Mapping** | Technique and sub-technique IDs | Coverage gap analysis |
| **Detection Test Cases** | Sigma/YARA rule stubs | SIEM/EDR validation |
## Tool Arsenal
| Category | Tool(s) | What it does |
|---|---|---|
| **Network Recon** | `nmap`, `masscan`, `whois`, `dig`, `traceroute`, `ping` | Service/version detection, full-range port sweeps, DNS/WHOIS enumeration |
| **Web Scanning** | `nikto`, `curl`, `openssl` | Misconfig checks, header inspection, TLS/cert validation |
| **Content Discovery** | `gobuster`, `ffuf`, `dirb` | Directory/DNS brute-force, high-speed fuzzing |
| **Auto-CVE Engine** | `nuclei` | 12,000+ templates — CVEs, misconfig, exposures, default creds |
| **Curated CVE Watchlist** | `cve_watchlist_scan` | Lookup-only orchestration of Nuclei + ExploitDB against a curated list of recent high-severity CVE IDs |
| **Injection Testing** | `sqlmap`, `xsstrike` | SQL injection and XSS detection with WAF fingerprinting |
| **CMS Scanning** | `wpscan` | WordPress core/plugin/theme vulnerability enumeration |
| **Active Directory & Identity** | `certipy`, `bloodhound-python`, `bloodyAD`, Impacket (`GetUserSPNs.py`, `GetNPUsers.py`) | ADCS misconfig (ESC1–16), AD data collection, ACL/object enumeration, Kerberoast/AS-REProast detection |
| **Cryptographic Inventory / Post-Quantum** | nmap `ssl-enum-ciphers` / `ssh2-enum-algos` | TLS & SSH algorithm inventory; Harvest-Now-Decrypt-Later risk classification |
| **Host Hardening & Rootkit Detection** | `chkrootkit`, `rkhunter`, `lynis` | Signature-based rootkit checks and general Linux hardening audit |
| **Ransomware-Relevant Exposure** | nmap + nuclei (curated tags) | External RDP/SMB/VPN exposure check — attack-surface only, not infection detection |
| **Supply Chain** | `osv-scanner` | Dependency CVE audit against the OSV.dev database |
| **Fuzzing** | `AFL++` | Crash-finding fuzzing harness automation against a local instrumented binary |
| **OWASP Reference** | — | Static Top-10 (Web) and Top-10 (Agentic/AI) checklists mapped to tool coverage |
| **Recon Orchestrator** | — | `full_recon` chains DNS/WHOIS/port/tech-fingerprint recon into one attack-surface summary with suggested test priorities by detected stack |
| **Session Reporting** | — | `generate_report` compiles every tool call this session into one Markdown report with a severity summary |
| **Exploit Research** | `searchsploit` | Offline ExploitDB lookup by product or CVE |
55+ NeuralReaper security workflows — run `tool_help` inside Claude for the full callable list with parameters.
---
## CVE-Informed Adversary Simulation
GhostInShell's simulation library includes attack chain modeling based on vulnerability intelligence, CVE research, and MITRE ATT&CK techniques.
| Scenario | Category | Simulation Focus |
|-----|----------|------------------|
| CVE-2026-8461 | FFmpeg RCE | Media processing attack surface, file upload validation |
| CVE-2026-55200 | libssh2 RCE | SSH service hardening, packet size limit testing |
| CVE-2026-20253 | Splunk RCE | REST API authentication validation, application security controls |
| CVE-2026-31431 | Linux Kernel LPE | Privilege escalation monitoring, SUID auditing |
| CVE-2026-45648 | AD DS NSPI | RPC filtering, domain controller hardening |
| CVE-2026-50751 | Check Point VPN | VPN exposure assessment, authentication validation |
### Example GhostInShell Workflow
```bash
# Simulate an attack chain against a target profile
"Simulate a full compromise chain against my lab environment at 192.168.56.10"
# Output:
# [+] GhostInShell session GHOST-A7B3C9D8E1F2 initiated
# [+] Objective: full_compromise | Stealth: enabled | Max Depth: 3
# [+] Attack surface mapped: 5 vectors identified
# [+] Optimal exploit chain built: CVE-2026-20253 -> CVE-2026-31431 -> CVE-2026-45648
# [+] Detection artifacts generated: 12 IOCs, 4 Sigma rules, 3 MITRE techniques mapped
# [+] Report saved to: reports/ghost_a7b3c9d8e1f2.json
## Quick Start
```bash
git clone https://github.com/the-artist111/NeuralReaper.git
cd NeuralReaper
docker build -t neuralreaper:latest .Point Claude Desktop at it by merging claude_desktop_config.json into your own config, then restart Claude Desktop. Full instructions below.
Detailed Setup
git clone https://github.com/the-artist111/NeuralReaper.git
cd NeuralReaper
docker build -t neuralreaper:latest .
mkdir -p ~/.config/Claude
cp claude_desktop_config.json ~/.config/Claude/claude_desktop_config.json
# restart Claude DesktopInstall Docker Desktop for Windows.
In Docker Desktop → Settings → Resources → WSL Integration, enable your distro (e.g. Ubuntu) and Apply & Restart.
Inside your WSL2 distro:
git clone https://github.com/the-artist111/NeuralReaper.git cd NeuralReaper docker build -t neuralreaper:latest .Copy the config to Windows (run from PowerShell, not WSL — cross-filesystem writes from WSL into
AppDataare frequently permission-denied):New-Item -ItemType Directory -Force -Path "$env:APPDATA\Claude" Copy-Item "\\wsl.localhost\Ubuntu\home\<user>\NeuralReaper\claude_desktop_config.json" "$env:APPDATA\Claude\claude_desktop_config.json"Docker Desktop must be running before Claude Desktop launches the container — Claude calls
docker.exedirectly, and if the daemon isn't up yet you'll seefailed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine.Fully quit and reopen Claude Desktop (system tray → Quit, not just close-the-window).
bash tests/smoke_test.shOr check directly inside Claude Desktop: Settings → Developer → Local MCP servers. NeuralReaper should show a running badge. If it shows failed, click View Logs — the error is almost always either "Docker Desktop isn't running" or a stale docker path in the config.
Usage Examples
"Sync latest vulnerability intelligence, then run a full CVE scan on 192.168.1.10"
"Check my lab DC against current vulnerability intelligence, then check its TLS for post-quantum readiness"
"Run certipy_find against my lab domain, then check for kerberoastable accounts"
"Run a full_recon on target.local and tell me what to prioritize testing"
"Audit this container's hardening with lynis, then run chkrootkit"
"Check 192.168.1.50 for ransomware-relevant exposure, then generate a report of everything we've found this session"Example output from a NeuralReaper orchestrated nuclei_scan workflow:
=== NUCLEI SCAN: http://192.168.56.10 [severity=critical,high,medium] ===
[CVE-2026-41940] [http] [critical] Apache HTTP Server path traversal — 192.168.56.10
[exposed-panel:phpmyadmin] [http] [medium] phpMyAdmin panel exposed — 192.168.56.10/pma/
[tech-detect:nginx] [http] [info] nginx 1.24.0 detectedSample pqc_readiness_check output:
=== PQC / HNDL READINESS: target.local:443 ===
HNDL Risk Level: HIGH (classical-only key exchange — prioritize for PQ migration if data sensitivity/longevity is high)
- [HNDL RISK] No post-quantum hybrid key exchange group detected. Traffic captured today could be
decrypted retroactively once a sufficiently large quantum computer exists.
- [CLASSICAL] RSA key exchange/signature present — broken by Shor's algorithm on a sufficiently
large quantum computer. Long-lived sensitive data is the highest-priority migration candidate.Security & Safety Design
This is a security tool, so it's held to its own standard:
Non-root execution. The container runs as an unprivileged
pentesteruser; onlynmapandmasscanget the specificCAP_NET_RAW/CAP_NET_ADMINcapabilities they need viasetcap— nothing runs--privileged.Input sanitization. Every target string is validated against a strict allow-list pattern before it touches a subprocess call; nothing is passed through a shell, so there's no string-concatenation injection surface.
Hard timeouts. Every tool call is bounded (
MAX_TOOL_RUNTIME, default 180s) so a hung scan can't hang the MCP session indefinitely.No persistent listener. The container is spawned per-session over stdio and torn down with
--rm— there's no exposed port or standing service to leave open by accident.Stateless between runs. No scan history, credentials, or target lists are written to disk inside the container.
Known limitation: --network host is a native-Linux Docker feature. On Docker Desktop (Windows/macOS) it runs inside a managed VM, so host-network-dependent scans (e.g. raw ARP discovery) behave correctly on Linux hosts but may need bridge-network + port-mapping adjustments on Windows/macOS — tracked in Roadmap.
Engineering Notes — Real Problems Solved
Authentic build log, kept here deliberately instead of polished away — this is the part that's actually interesting in an interview.
Problem | Root Cause | Fix |
| Kali rolling repo had a transient broken dependency chain at build time ( | Migrated base image from |
| Not Ubuntu-packaged |
|
| Docker Desktop's WSL Integration toggle was off for that specific distro | Settings → Resources → WSL Integration → enable the distro → Apply & Restart |
| Cross-filesystem writes from WSL2 into Windows | Did the copy from native PowerShell instead, reading the WSL2 file via the |
Tool never appeared in Claude's tool list at all | Claude was running as the Microsoft Store package ( | Uninstalled the Store package, installed the direct |
MCP server showed | Logs showed | Docker Desktop simply wasn't running yet when Claude Desktop tried to spawn the container — config and image were already correct |
The takeaway that mattered most: read the actual log file before changing anything. Every fix above came from %APPDATA%\Claude\logs\mcp-server-NeuralReaper.log, not guesswork.
📂 Project Structure
NeuralReaper/
├── agents/ # AI agent configurations
├── intelligence/ # Real-time threat intelligence engine
│ ├── rss.py # RSS threat feed collector
│ ├── nvd.py # NVD CVE collector
│ ├── cisa.py # CISA KEV collector
│ ├── database.py # Intelligence database
│ ├── parser.py # Feed parser
│ ├── scheduler.py # Scheduled updates
│ ├── updater.py # Unified intelligence updater
│ └── __init__.py
│
├── data/ # Cached threat intelligence
│ ├── rss_news.json
│ ├── cisa_kev.json
│ ├── intelligence_db.json
│ └── threat_intelligence.json
│
├── docs/
│ ├── ARCHITECTURE.md
│ ├── neuralreaper_v2_architecture.png
│ ├── assets/
│ └── portfolio-kit.md
│
├── examples/
├── tests/
├── tools/
│ ├── recon/
│ ├── web/
│ ├── ad/
│ ├── crypto/
│ ├── host/
│ ├── supply_chain/
│ ├── ai_security/
│ └── ghostinshell/
│
├── server.py
├── Dockerfile
├── docker-compose.yml
├── claude_desktop_config.json
├── requirements.txt
├── CHANGELOG.md
├── CONTRIBUTING.md
├── SECURITY.md
└── LICENSE
---
## Roadmap
| Version | Planned Feature | Status |
| ------- | -------------------------------------------------------- | -------- |
| v2.1 | GhostInShell MITRE ATT\&CK Navigator export | Planned |
| v2.1 | Sigma rule auto-generation from simulation chains | Planned |
| v2.2 | Cloud-native attack path simulation (AWS/Azure/GCP) | Planned |
| v2.2 | Kubernetes security assessment tools | Planned |
| v3.0 | Multi-agent Claude orchestration for complex assessments | Research |
---
## Contributing
We welcome contributions that align with our Detection, Not Weaponization philosophy. Please see CONTRIBUTING.md for guidelines.
Types of contributions we love:
New MCP tool integrations for reconnaissance and detection
Additional Nuclei template categories for the CVE watchlist
GhostInShell simulation scenarios for emerging attack techniques
Documentation and tutorial improvements
Bug fixes and performance optimizations
Types of contributions we will not accept:
Exploit payload generation or weaponization features
Tools designed to bypass security controls on target systems
Any code that executes attacks against systems without explicit authorization
---
## Disclaimer
NeuralReaper is intended for authorized security research, penetration testing, and defensive training only. Users are responsible for ensuring they have explicit permission before scanning or assessing any target.
The GhostInShell adversary emulation module generates only simulated outputs and detection artifacts — it does not execute attacks against live systems. All exploit chain modeling is performed in-memory with no network egress.
By using this software, you agree to:
Only scan systems you own or have written authorization to test
Comply with all applicable laws and regulations in your jurisdiction
Not use this tool for unauthorized access, data theft, or disruption of services
---
## License
MIT License
Copyright (c) 2026 the-artist111
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
---
<div align="center">
Built with [Anthropic MCP](https://modelcontextprotocol.io) · [ProjectDiscovery Nuclei](https://github.com/projectdiscovery/nuclei) · [XSStrike](https://github.com/s0md3v/XSStrike)
</div>This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- -license-quality-maintenanceA Kali Linux-based MCP server that exposes over 45 penetration testing tools for AI-assisted security auditing and vulnerability scanning. It features strict scope enforcement, structured output parsing, and persistent finding storage to automate the offensive security workflow.Last updated
- Alicense-qualityDmaintenanceEnables AI assistants to autonomously execute over 200 open-source penetration testing tools via MCP, including reconnaissance, web exploitation, and brute-forcing, through a unified server architecture with Docker sandboxing for safe execution.Last updated51MIT
- Flicense-qualityDmaintenanceEnables natural-language-driven security testing by orchestrating multiple pen-testing tools through MCP, with automated scan execution and AI-assisted vulnerability summarization.Last updated
- Flicense-qualityBmaintenanceAI-driven penetration testing MCP server that equips Claude with 13 tools for automated reconnaissance, analysis, vulnerability validation, and exploitation.Last updated
Related MCP Connectors
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Security-first WordPress MCP server. 129 tools for Claude, ChatGPT, Gemini. Free on wp.org.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/the-artist111/NeuralReaper'
If you have feedback or need assistance with the MCP directory API, please join our Discord server