MCP Nuclei Server

Created By
crazyMarkya year ago
A Nuclei security scanning server based on MCP (Model Control Protocol), providing convenient vulnerability scanning services.一个基于 MCP (Model Control Protocol) 的 Nuclei 安全扫描服务器,提供便捷的漏洞扫描服务。
Overview

What is MCP Nuclei Server?

MCP Nuclei Server is a security scanning server based on the Model Control Protocol (MCP) that provides convenient vulnerability scanning services using Nuclei.

How to use MCP Nuclei Server?

To use the MCP Nuclei Server, clone the repository, install the necessary dependencies, and configure the MCP settings. You can then execute scans by specifying the target and desired parameters.

Key features of MCP Nuclei Server?

  • Supports Nuclei security scanning with various options.
  • Configurable template and tag filtering for tailored scans.
  • Severity-based vulnerability filtering to focus on critical issues.
  • Outputs results in JSON format for easy integration.
  • Easy-to-integrate MCP service for developers.

Use cases of MCP Nuclei Server?

  1. Conducting security assessments on web applications.
  2. Automating vulnerability scanning in CI/CD pipelines.
  3. Integrating with other security tools for comprehensive analysis.

FAQ from MCP Nuclei Server?

  • What is required to run MCP Nuclei Server?

You need Python 3.8 or higher and the Nuclei binary installed and configured.

  • Can I customize the scanning templates?

Yes! You can configure templates and tags to filter the scans according to your needs.

  • What output format does the server provide?

The server provides scan results in JSON format, making it easy to parse and integrate with other tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
crazyMarky
Star
2
Language
Python
License
-
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago