Skip to main content
Glama
SlanyCukr

Bug Bounty MCP Server

by SlanyCukr

wfuzz_scan

Execute web application fuzzing to discover hidden directories, files, and parameters by testing various inputs against target URLs.

Instructions

Execute Wfuzz for web application fuzzing.

Args: url: Target URL with FUZZ keyword wordlist: Wordlist file path fuzz_parameter: Parameter to fuzz (default: FUZZ) hide_codes: HTTP status codes to hide threads: Number of concurrent threads follow_redirects: Follow HTTP redirects additional_args: Additional Wfuzz arguments

Returns: Web application fuzzing results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
additional_argsNo
follow_redirectsNo
fuzz_parameterNoFUZZ
hide_codesNo404
threadsNo
urlYes
wordlistNo/usr/share/wordlists/dirb/common.txt

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler implementing the wfuzz tool logic: extracts parameters, builds command, executes wfuzz, parses output.
    @tool(required_fields=["url"])
    def execute_wfuzz():
        """Execute Wfuzz for web application fuzzing."""
        data = request.get_json()
        params = extract_wfuzz_params(data)
    
        logger.info(f"Executing Wfuzz on {params['url']}")
    
        started_at = datetime.now()
        command = build_wfuzz_command(params)
        logger.info(f"Wfuzz command: {command}")
    
        execution_result = execute_command(command, timeout=params["timeout"])
        ended_at = datetime.now()
    
        return parse_wfuzz_result(execution_result, params, command, started_at, ended_at)
  • MCP server registration of the 'wfuzz_scan' tool, defining input schema via parameters and proxying to REST API /api/wfuzz.
    @mcp.tool()
    def wfuzz_scan(
        url: str,
        wordlist: str = "/usr/share/wordlists/dirb/common.txt",
        fuzz_parameter: str = "FUZZ",
        hide_codes: str = "404",
        threads: int = 10,
        follow_redirects: bool = False,
        additional_args: str = "",
    ) -> dict[str, Any]:
        """Execute Wfuzz for web application fuzzing.
    
        Args:
            url: Target URL with FUZZ keyword
            wordlist: Wordlist file path
            fuzz_parameter: Parameter to fuzz (default: FUZZ)
            hide_codes: HTTP status codes to hide
            threads: Number of concurrent threads
            follow_redirects: Follow HTTP redirects
            additional_args: Additional Wfuzz arguments
    
        Returns:
            Web application fuzzing results
        """
        data = {
            "url": url,
            "wordlist": wordlist,
            "fuzz_parameter": fuzz_parameter,
            "hide_codes": hide_codes,
            "threads": threads,
            "follow_redirects": follow_redirects,
            "additional_args": additional_args,
        }
    
        logger.info(f"🎯 Starting Wfuzz scan on {url}")
        result = api_client.safe_post("api/wfuzz", data)
    
        if result.get("success"):
            logger.info(f"✅ Wfuzz scan completed on {url}")
        else:
            logger.error("❌ Wfuzz scan failed")
    
        return result
  • Helper to extract and normalize wfuzz parameters from input data, with aggressive mode support.
    def extract_wfuzz_params(data: dict) -> dict:
        """Extract wfuzz parameters from request data."""
        aggressive = data.get("aggressive", False)
    
        base_params = {
            "url": data.get("url", data.get("domain", "")),
            "wordlist": data.get(
                "wordlist", "/usr/share/wordlists/wfuzz/Injections/All-attack.txt"
            ),
            "threads": data.get("threads", 40),
            "hide_codes": data.get("hide_codes", "404"),
            "show_codes": data.get("show_codes", "200,301,302,401,403,500"),
            "follow_redirects": data.get("follow_redirects", False),
            "payload": data.get("payload", "FUZZ"),
            "timeout": data.get("timeout", 300),
            "additional_args": data.get("additional_args", ""),
        }
    
        if aggressive:
            base_params.update(
                {
                    "threads": 100,
                    "hide_codes": "404",
                    "show_codes": "200,301,302,401,403,500",
                    "timeout": 30,
                }
            )
    
        return base_params
  • Helper to construct the full wfuzz command line from parameters.
    def build_wfuzz_command(params: dict) -> str:
        """Build wfuzz command from parameters."""
        command_parts = ["wfuzz", "-w", params["wordlist"], "-t", str(params["threads"])]
    
        if params["hide_codes"]:
            command_parts.extend(["--hc", params["hide_codes"]])
    
        if params["show_codes"]:
            command_parts.extend(["--sc", params["show_codes"]])
    
        if params["follow_redirects"]:
            command_parts.append("-L")
    
        # Handle FUZZ parameter in URL
        url = params["url"]
        if params["payload"] not in url:
            if url.endswith("/"):
                url += params["payload"]
            else:
                url += f"/{params['payload']}"
        command_parts.append(url)
    
        if params["additional_args"]:
            command_parts.extend(params["additional_args"].split())
    
        return " ".join(command_parts)
  • Helper to parse wfuzz execution results into structured findings with stats and execution details.
    def parse_wfuzz_result(
        execution_result: dict,
        params: dict,
        command: str,
        started_at: datetime,
        ended_at: datetime,
    ) -> dict[str, Any]:
        """Parse wfuzz execution result and format response."""
        duration_ms = int((ended_at - started_at).total_seconds() * 1000)
    
        if not execution_result["success"]:
            return {
                "success": False,
                "tool": "wfuzz",
                "params": params,
                "started_at": started_at.isoformat(),
                "ended_at": ended_at.isoformat(),
                "duration_ms": duration_ms,
                "error": execution_result.get("stderr", "Command execution failed"),
                "findings": [],
                "stats": {"findings": 0, "dupes": 0, "payload_bytes": 0},
            }
    
        stdout = execution_result.get("stdout", "")
        findings = parse_wfuzz_output(stdout)
        payload_bytes = len(stdout.encode("utf-8"))
    
        return {
            "success": True,
            "tool": "wfuzz",
            "target": params["url"],
            "command": command,
            "parameters": params,
            "started_at": started_at.isoformat(),
            "ended_at": ended_at.isoformat(),
            "duration_ms": duration_ms,
            "findings": findings,
            "stats": {
                "findings": len(findings),
                "dupes": 0,
                "payload_bytes": payload_bytes,
            },
            "execution": {
                "success": execution_result["success"],
                "return_code": execution_result["return_code"],
                "stdout": execution_result["stdout"],
                "stderr": execution_result["stderr"],
            },
        }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Execute Wfuzz' and 'Returns: Web application fuzzing results,' but lacks critical details: whether this is a read-only or destructive operation, permission requirements, rate limits, error handling, or output format specifics. For a security testing tool with potential impact, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized: a clear purpose statement followed by categorized Args and Returns sections. Every sentence adds value, with no redundant information. It could be slightly more front-loaded by emphasizing the core action earlier, but overall it's efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 parameters, security tool, no annotations) and the presence of an output schema, the description is moderately complete. It covers parameters adequately but lacks behavioral context and usage guidelines. The output schema likely handles return values, so the description's brief 'Returns' statement is sufficient. However, for a tool in a crowded sibling set with no annotations, more guidance would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates well by listing all 7 parameters with brief explanations (e.g., 'Target URL with FUZZ keyword,' 'Wordlist file path'). It adds meaningful context beyond the schema's property titles, clarifying usage like the FUZZ keyword and default values. However, it doesn't detail parameter interactions or advanced usage scenarios, preventing a perfect score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Execute Wfuzz for web application fuzzing.' It specifies the verb ('execute') and resource ('Wfuzz'), and distinguishes it from siblings by mentioning 'web application fuzzing' (unlike general scanning tools like nmap_scan or specific vulnerability scanners like dalfox_xss_scan). However, it doesn't explicitly differentiate from similar fuzzing tools like ffuf_scan or dirb_scan, keeping it at a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools for scanning, fuzzing, and reconnaissance (e.g., ffuf_scan, dirb_scan, nuclei_scan), there's no indication of specific use cases, prerequisites, or comparisons. The only implied context is 'web application fuzzing,' but this is too vague for effective tool selection among the crowded sibling set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/SlanyCukr/bugbounty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server