nuclei-server MCP Server
Related Servers
Alternatives to nuclei-server MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes.12898 npm3MIT
- FlicenseCqualityDmaintenanceA TypeScript-based MCP server implementing a simple notes system that allows users to create, access, and generate summaries of text notes.14 npm-
- AlicenseAqualityFmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes via URIs and tools.1210 npm8MIT
- AlicenseAqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing creation and management of text notes with URIs and metadata.46 npmMIT
- FlicenseNot gradedqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system with resources, tools for creating notes, and prompts for summarization.-
- FlicenseBqualityDmaintenanceA simple TypeScript-based MCP server that implements a notes system, allowing users to create, list, and generate summaries of text notes via Claude.13-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one starts a scan and the other cancels it. There is no overlap or ambiguity between these operations, making it easy for an agent to select the correct tool for the intended action.
Both tools follow a consistent verb_noun pattern (start_scan, cancel_scan), using snake_case throughout. This predictable naming scheme enhances readability and reduces confusion for agents.
With only 2 tools, the server feels too thin for a scanning domain, as it lacks essential operations like retrieving scan results, listing scans, or configuring scans. This minimal set may force agents into dead ends or require workarounds.
The tool surface is severely incomplete for a nuclei scanning server. While start and cancel are basic actions, there are significant gaps: no way to get scan status, view results, list scans, or manage templates. This will likely cause agent failures in typical scanning workflows.