mcp-noctua
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Debug mode (default from .env.example) | |
| NOCTUA_TIMEOUT | No | Timeout for tool execution (default from .env.example) | |
| NOCTUA_COMPOSE_DIR | No | Directory for compose files (default from .env.example) | |
| NOCTUA_REPORTS_DIR | No | Directory for reports (default from .env.example) | |
| DOCKER_CONTAINER_NAME | No | The Docker container name for the toolbox (default from .env.example) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_toolA | Execute un outil de reconnaissance/scan whiteliste dans la toolbox (forme exec, sans shell : pas de pipe ni de chainage). Usage test AUTORISE uniquement. Borne par un timeout qui tue reellement le process. Pour enchainer des outils, faire plusieurs appels. |
| web_crawlB | Crawl borne d'une URL (katana, profondeur 1..3, crawling JS). |
| port_scanB | Scan de ports (naabu top-ports) puis sonde HTTP (httpx) des ports ouverts. |
| vuln_scanB | Scan de vulnerabilites borne (nuclei) : debit/concurrence limites, tags et severite optionnels. |
| list_toolsA | Liste les outils whitelistes presents (et absents) dans la toolbox. |
| healthA | Etat du conteneur toolbox (present/absent, running, image). Ne demarre rien. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: health checks container state, list_tools enumerates whitelisted tools, port_scan performs port scanning, run_tool executes a generic recon tool, vuln_scan does vulnerability scanning, and web_crawl does web crawling. No overlap or ambiguity.
All names use snake_case and are descriptive, but there's a mix of verb-first (list_tools, run_tool) and noun-first (port_scan, vuln_scan, web_crawl) patterns, plus health stands alone. Still consistent in style and readable.
6 tools is well-scoped for a reconnaissance/scanning toolbox, covering essential functions without being overly numerous or sparse.
The set covers core recon tasks: tool listing, port scanning, vulnerability scanning, web crawling, and a generic run_tool for extensibility. Minor gaps like explicit service detection or DNS enumeration are likely addressable via run_tool.