Skip to main content
Glama
SlanyCukr

Bug Bounty MCP Server

by SlanyCukr

fierce_scan

Perform DNS reconnaissance and subdomain discovery for target domains using customizable scanning parameters and wordlists.

Instructions

Execute Fierce for DNS reconnaissance and subdomain discovery.

Args: domain: Target domain dns_server: DNS server to use wordlist: Custom wordlist for subdomain brute force threads: Number of threads delay: Delay between requests wide: Wide scan (more comprehensive) additional_args: Additional Fierce arguments

Returns: DNS reconnaissance results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
additional_argsNo
delayNo
dns_serverNo
domainYes
threadsNo
wideNo
wordlistNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration (@mcp.tool()) and handler function for 'fierce_scan'. Proxies parameters to REST API endpoint '/api/fierce' via BugBountyAPIClient.
    def fierce_scan(
        domain: str,
        dns_server: str = "",
        wordlist: str = "",
        threads: int = 20,
        delay: int = 0,
        wide: bool = False,
        additional_args: str = "",
    ) -> dict[str, Any]:
        """Execute Fierce for DNS reconnaissance and subdomain discovery.
    
        Args:
            domain: Target domain
            dns_server: DNS server to use
            wordlist: Custom wordlist for subdomain brute force
            threads: Number of threads
            delay: Delay between requests
            wide: Wide scan (more comprehensive)
            additional_args: Additional Fierce arguments
    
        Returns:
            DNS reconnaissance results
        """
        data = {
            "domain": domain,
            "dns_server": dns_server,
            "wordlist": wordlist,
            "threads": threads,
            "delay": delay,
            "wide": wide,
            "additional_args": additional_args,
        }
    
        logger.info(f"🔍 Starting Fierce DNS reconnaissance on {domain}")
        result = api_client.safe_post("api/fierce", data)
    
        if result.get("success"):
            logger.info(f"✅ Fierce scan completed on {domain}")
        else:
            logger.error("❌ Fierce scan failed")
    
        return result
  • Core execution handler for the 'fierce' tool in REST API. Extracts params, builds and runs 'fierce' command, parses output into structured findings with subdomains.
    @tool(required_fields=["target"])
    def execute_fierce():
        """Execute Fierce for DNS reconnaissance and subdomain discovery."""
        data = request.get_json()
        params = extract_fierce_params(data)
    
        started_at = datetime.now()
        command = build_fierce_command(params)
        execution_result = execute_command(
            " ".join(command), timeout=params.get("timeout", 600)
        )
        ended_at = datetime.now()
    
        return parse_fierce_output(execution_result, params, command, started_at, ended_at)
  • Helper function to construct the 'fierce' command-line arguments based on input parameters.
    def build_fierce_command(params: dict) -> list[str]:
        """Build the fierce command from parameters."""
        args = ["fierce", "--domain", params["domain"]]
    
        # Add optional parameters
        if params["dns_servers"]:
            if isinstance(params["dns_servers"], list):
                dns_servers_str = " ".join(params["dns_servers"])
            else:
                dns_servers_str = str(params["dns_servers"])
            args.extend(["--dns-servers", dns_servers_str])
    
        if params["wide"]:
            args.append("--wide")
    
        if params["connect"]:
            args.append("--connect")
    
        if params["delay"] > 0:
            args.extend(["--delay", str(params["delay"])])
    
        if params["traverse"]:
            args.extend(["--traverse", params["traverse"]])
    
        if params["range"]:
            args.extend(["--range", params["range"]])
    
        if params["subdomain_file"]:
            args.extend(["--subdomain-file", params["subdomain_file"]])
    
        if params["subdomains"]:
            if isinstance(params["subdomains"], list):
                subdomains_str = " ".join(params["subdomains"])
            else:
                subdomains_str = str(params["subdomains"])
            args.extend(["--subdomains", subdomains_str])
    
        if params["tcp"]:
            args.append("--tcp")
    
        # Add any additional arguments
        if params["additional_args"]:
            args.extend(params["additional_args"].split())
    
        return args
  • Helper function to parse 'fierce' tool output, extract subdomains, and format into structured JSON findings with stats.
    def parse_fierce_output(
        execution_result: dict[str, Any],
        params: dict,
        command: list[str],
        started_at: datetime,
        ended_at: datetime,
    ) -> dict[str, Any]:
        """Parse fierce execution results into structured findings."""
        duration_ms = int((ended_at - started_at).total_seconds() * 1000)
    
        if not execution_result["success"]:
            return {
                "success": False,
                "tool": "fierce",
                "params": params,
                "command": command,
                "started_at": started_at.isoformat(),
                "ended_at": ended_at.isoformat(),
                "duration_ms": duration_ms,
                "error": execution_result.get("error", "Command execution failed"),
                "findings": [],
                "stats": {"findings": 0, "dupes": 0, "payload_bytes": 0},
            }
    
        # Parse successful output
        stdout = execution_result.get("stdout", "")
        with open("/tmp/fierce_raw_output.log", "a") as f:
            f.write(stdout + "\n")
        findings = []
    
        # Extract subdomains from fierce output
        for line in stdout.strip().split("\n"):
            line = line.strip()
            if not line:
                continue
    
            # Parse subdomain findings
            subdomain_info = _extract_subdomain_from_line(line, params["domain"])
            if subdomain_info:
                finding = {
                    "type": "subdomain",
                    "target": subdomain_info.get("subdomain", line),
                    "evidence": {
                        "raw_output": line,
                        "domain": params["domain"],
                        "discovered_by": "fierce",
                    },
                    "severity": "info",
                    "confidence": "medium",
                    "tags": ["fierce", "subdomain-discovery"],
                    "raw_ref": line,
                }
                findings.append(finding)
    
        payload_bytes = len(stdout.encode("utf-8"))
    
        return {
            "success": True,
            "tool": "fierce",
            "params": params,
            "command": command,
            "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,
            },
        }
  • Helper function to extract and normalize input parameters for the 'fierce' tool from the API request JSON.
    def extract_fierce_params(data: dict) -> dict:
        """Extract and organize fierce parameters from request data."""
        return {
            "domain": data.get("target", ""),
            "dns_servers": data.get("dns_servers", []),
            "wide": data.get("wide", False),
            "connect": data.get("connect", False),
            "delay": data.get("delay", 0),
            "traverse": data.get("traverse"),
            "range": data.get("range"),
            "subdomain_file": data.get("subdomain_file"),
            "subdomains": data.get("subdomains", []),
            "tcp": data.get("tcp", False),
            "additional_args": data.get("additional_args", ""),
            "timeout": data.get("timeout", 600),
        }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool executes Fierce for DNS reconnaissance, implying it performs network scanning, but does not cover critical aspects like rate limits, permissions needed, potential impact on target systems, or error handling. For a tool with no annotations and 7 parameters, this is insufficient 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. It starts with a clear purpose statement, followed by a bullet-point list of args and returns, with no redundant information. Every sentence serves a purpose, making it 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, no annotations, but an output schema exists), the description is moderately complete. It covers the purpose and parameters but lacks behavioral context and usage guidelines. The presence of an output schema means return values are documented elsewhere, reducing the burden, but overall completeness is limited by missing operational details.

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

Parameters3/5

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

The description lists all 7 parameters with brief explanations (e.g., 'domain: Target domain', 'wide: Wide scan (more comprehensive)'), adding meaning beyond the schema, which has 0% description coverage. However, the explanations are minimal and lack depth (e.g., no details on wordlist format or thread limits). With low schema coverage, this partially compensates but does not fully elucidate parameter usage.

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 Fierce for DNS reconnaissance and subdomain discovery.' It specifies the verb ('Execute'), the tool ('Fierce'), and the resource/domain ('DNS reconnaissance and subdomain discovery'). However, it does not explicitly differentiate from sibling tools like 'dnsenum_scan' or 'subfinder_scan', which may have overlapping functionality, so it falls short of a perfect score.

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 reconnaissance (e.g., 'dnsenum_scan', 'subfinder_scan', 'amass_scan'), there is no mention of specific contexts, prerequisites, or comparisons. This lack of differentiation leaves the agent without clear usage instructions.

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