Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
A

addcontent/nuclei-mcp

Run Nuclei scans with the context the model needs

Before you install: no copy-paste command · no license recorded · link reachable

First step: go install github.com/your-org/nuclei-mcp/cmd/nuclei-mcp@latest

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
  "mcpServers": {
    "addcontent-nuclei-mcp": {
      "command": "npx",
      "args": ["@modelcontextprotocol/inspector"]
    }
  }
}

Parsed from the README we fetched on 2026-11-07; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
  "servers": {
    "addcontent-nuclei-mcp": {
      "command": "npx",
      "args": ["@modelcontextprotocol/inspector"]
    }
  }
}
Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio addcontent-nuclei-mcp -- npx @modelcontextprotocol/inspector
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
Source
collected from the abordage/awesome-mcp list · type: MCP server
Harvest history
first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score
score 1,003 · 10 sources · mcp
Install
npx @modelcontextprotocol/inspector
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx @modelcontextprotocol/inspector. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# Nuclei MCP Integration

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

A Model Context Protocol (MCP) server implementation that integrates Nuclei, a fast and customizable vulnerability scanner, with the MCP ecosystem. This server provides a standardized interface for performing security scans and managing vulnerability assessments programmatically.
## Features
Vulnerability Scanning: Perform comprehensive security scans using Nuclei's powerful scanning engine
Template Management: Add, list, and manage custom Nuclei templates
Result Caching: Configurable caching system to optimize repeated scans
Concurrent Operations: Thread-safe implementation for high-performance scanning
RESTful API: Standardized interface for integration with other MCP-compliant tools
Detailed Reporting: Structured vulnerability reports with severity levels and remediation guidance
## Tools & Endpoints
### Core Tools
nuclei_scan: Perform a full Nuclei scan with advanced filtering options
basic_scan: Quick scan with minimal configuration
vulnerability_resource: Query and retrieve scan results
add_template: Add custom Nuclei templates
list_templates: View available templates
get_template: Retrieve details of a specific template
## Getting Started
### Prerequisites
Nuclei (will be automatically downloaded if not present)
Node.js 14+ (for MCP Inspector, optional)
### Installation
#### Option 1: Download Pre-built Binary (Recommended)
1. Download the latest release for your platform from the Releases page
2. Extract the archive
3. Run the binary:
bash
# Linux/macOS
./nuclei-mcp
# Windows
nuclei-mcp.exe
#### Option 2: Install with Go
bash
go install github.com/your-org/nuclei-mcp/cmd/nuclei-mcp@latest
#### Option 3: Build from Source
1. Clone the repository:
bash
git clone https://github.com/your-org/nuclei-mcp.git
cd nuclei-mcp
2. Install dependencies:
bash
go mod download
3. Build and run:
bash
go build -o nuclei-mcp ./cmd/nuclei-mcp
./nuclei-mcp
### Running the Server
Start the MCP server:
bash
# If using pre-built binary
./nuclei-mcp
# If built from source
go run cmd/nuclei-mcp/main.go
### Using the MCP Inspector
For development and testing, use the MCP Inspector:
bash
# Install the MCP Inspector globally
npm install -g @modelcontextprotocol/inspector
# Start the inspector with the Nuclei MCP server
npx @modelcontextprotocol/inspector go run cmd/nuclei-mcp/main.go
The inspector UI will be available at http://localhost:5173
## Configuration
Configuration can be managed through a YAML configuration file or environment variables. The server looks for configuration in the following locations (in order of precedence):
1. File specified by --config flag
2. config.yaml in the current directory
3. $HOME/.nuclei-mcp/config.yaml
4. /etc/nuclei-mcp/config.yaml
### Configuration File Example
Create a config.yaml file with the following structure:
yaml
server:
name: "nuclei-mcp"
version: "1.0.0"
port: 3000
host: "127.0.0.1"
cache:
enabled: true
expiry: 1h
max_size: 1000
logging:
level: "info"
path: "./logs/nuclei-mcp.log"
max_size_mb: 10
max_backups: 5
max_age_days: 30
compress: true
nuclei:
templates_directory: "nuclei-templates"
timeout: 5m
rate_limit: 150
bulk_size: 25
template_threads: 10
headless: false
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/addcontent-nuclei-mcp/)
Source
awesome · https://github.com/addcontent/nuclei-mcp
Browse by field
MCP servers
Listed by
10 independent sources
added
today

More like this

All 6,229 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index