Skip to main content
Glama

runHashcat

Crack password hashes using dictionary, brute-force, or hybrid attacks to test security and recover credentials during penetration testing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashDataYesString containing the password hashes, one per line.
attackModeNoAttack mode: 0=Straight, 1=Combination, 3=Brute-force, 6=Hybrid Wordlist + Mask, 7=Hybrid Mask + Wordlist
hashTypeNoHash-type, e.g., 0=MD5, 100=SHA1, 1000=NTLM, 1400=SHA2-256, 1800=sha512crypt, 22000=WPA*01/WPA*02
wordlistNoPath to wordlist file for dictionary attacks
maskNoMask for brute-force attacks (e.g., '?a?a?a?a?a?a?a?a' for 8 chars)
incrementNoEnable incremental mode (start with shorter passwords)
incrementMinNoMinimum password length for incremental mode
incrementMaxNoMaximum password length for incremental mode
rulesNoRules file to apply to wordlist
sessionNoSession name for resuming attacks
restoreNoRestore a previous session
optimizedKernelsNoEnable optimized kernels (-O)
workloadProfileNoWorkload profile: 1=Low, 2=Default, 3=High, 4=Nightmare
deviceTypesNoDevice types: 1=CPU, 2=GPU, 3=FPGA
forceNoIgnore warnings
potfilePathNoPath to custom potfile
outfileNoOutput file for cracked hashes
outfileFormatNoOutput format: 1=hash, 2=plain, 3=hex-plain, etc.
runtimeNoAbort session after X seconds
showProgressNoShow progress every X seconds
quietNoSuppress output
loopbackNoAdd new plains to induct directory
markovThresholdNoThreshold X when to stop accepting new Markov-chains
customCharset1NoUser-defined charset ?1
customCharset2NoUser-defined charset ?2
customCharset3NoUser-defined charset ?3
customCharset4NoUser-defined charset ?4
optionsNoAdditional raw hashcat options
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/DMontgomery40/pentest-mcp'

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