Skip to main content
Glama
schwarztim

feroxbuster-mcp

by schwarztim

feroxbuster_scan

Scan target URLs to discover hidden directories and files using configurable wordlists, recursion, and filters, executed remotely via SSH.

Instructions

Start a feroxbuster directory scan against a target URL. Executes on remote Kali system via SSH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTarget URL to scan (e.g., http://example.com)
wordlistNoPath to wordlist on Kali (default: /usr/share/wordlists/seclists/Discovery/Web-Content/common.txt)
extensionsNoFile extensions to check (e.g., ['php', 'html', 'js'])
recursion_depthNoMaximum recursion depth (0 = infinite, default: 4)
threadsNoNumber of concurrent threads (default: 50)
timeoutNoRequest timeout in seconds (default: 7)
rate_limitNoMaximum requests per second per directory
filter_statusNoStatus codes to filter OUT (exclude from results)
status_codesNoStatus codes to include (default: 200,204,301,302,307,308,401,403,405,500)
filter_sizeNoResponse sizes to filter OUT
filter_wordsNoWord counts to filter OUT
filter_linesNoLine counts to filter OUT
headersNoCustom headers to include (e.g., {"Authorization": "Bearer token"})
proxyNoProxy URL (e.g., http://127.0.0.1:8080 or socks5://127.0.0.1:9050)
insecureNoDisable TLS certificate validation
no_recursionNoDisable recursive scanning
force_recursionNoForce recursion on all found paths
auto_tuneNoAutomatically lower scan rate on errors
auto_bailNoAutomatically stop on excessive errors
silentNoOnly output URLs (for piping)
jsonNoOutput results as JSON
backgroundNoRun scan in background and return immediately
dont_scanNoURLs to exclude from recursion
time_limitNoMaximum scan time (e.g., '10m', '1h', '30s')
scan_limitNoMaximum concurrent directory scans
user_agentNoCustom User-Agent string
cookiesNoCookies to include (e.g., 'session=abc123; token=xyz')
dataNoRequest body data for POST requests
methodsNoHTTP methods to use (default: GET)
queryNoQuery parameters to append (e.g., 'token=abc&debug=true')
Behavior3/5

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

With no annotations, the description carries full burden. It discloses remote execution via SSH, but lacks details on whether the scan is blocking, asynchronous, how results are returned, or safety implications (e.g., network impact).

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 a single concise sentence, front-loads the action, and has no redundancy. However, it could be slightly expanded to improve clarity without sacrificing conciseness.

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?

Given the tool has 30 parameters and no output schema, the description is too minimal. It does not explain parameter relationships, expected behavior of complex options (e.g., background or recursion), or how to interpret results.

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% (all parameters have descriptions), so the description adds no additional meaning. 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 action ('Start'), the resource ('feroxbuster directory scan'), and the target ('target URL'). It distinguishes from sibling tools like feroxbuster_config or feroxbuster_results by focusing on initiating a scan.

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 mentions remote execution via SSH but provides no guidance on when to use this tool versus siblings, such as when to stop or resume a scan, or prerequisites like having feroxbuster installed.

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/schwarztim/sec-feroxbuster-mcp'

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