feroxbuster-mcp

feroxbuster_config

Set default parameters for feroxbuster web content discovery scans, including wordlist, extensions, recursion depth, rate limit, and filters.

Instructions

Configure default feroxbuster settings for subsequent scans

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feroxbuster_config"
  }
}

Input Schema

Name	Required	Description
`wordlist`	No	Default wordlist path on Kali
`extensions`	No	Default file extensions
`recursion_depth`	No	Default recursion depth
`rate_limit`	No	Default rate limit (requests/sec)
`threads`	No	Default thread count
`timeout`	No	Default request timeout
`filter_status`	No	Default status codes to filter
`filter_size`	No	Default sizes to filter
`filter_words`	No	Default word counts to filter
`filter_lines`	No	Default line counts to filter
`headers`	No	Default headers
`proxy`	No	Default proxy URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations and minimal description; does not disclose whether settings persist globally, are overwritable, or any side effects of configuration.

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

Conciseness5/5

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

One sentence, zero waste, efficiently conveys the tool's purpose.

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

Completeness2/5

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

With 12 parameters and no output schema, the description lacks important context about how settings apply (e.g., session scoping) and what the tool returns.

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?

Schema coverage is 100%, so description adds no extra meaning beyond the schema; baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool configures default feroxbuster settings for subsequent scans, distinguishing it from scanning and result tools.

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

Usage Guidelines3/5

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

The description implies use before scans but does not explicitly state when or when not to use it, nor does it mention alternatives.

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

Deploy Server