F
Warning
24/100
12 days ago

Hashcat-MCP

MCP wrapper for Hashcat – automate hash cracking with natural language

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

MorDavid

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Tool descriptions don’t match what handlers do
3 tools describe read intent but their handlers mutate — show_cracked_hashes (line 692: result = subprocess.run(cmd, capture_output=True, text=True, timeout=HASHCAT_QUICK_TIMEOUT)); get_backend_info (line 710: result = subprocess.run([HASHCAT_PATH, "-I"], capture_output=True, text=True, timeout=HASHCAT_QUICK_); get_gpu_status (line 1042: result = subprocess.run([HASHCAT_PATH, "-I"], capture_output=True, text=True, timeout=HASHCAT_QUICK_)
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHASHCAT_PATH"": "C:\\path\\to\\hashcat\\hashcat.exe",
configHASHCAT_SESSION_DB
configHASHCAT_PRESETS_FILE
configHASHCAT_MODES_CSV
configHASHCAT_RATE_LIMIT
configHASHCAT_RATE_WINDOW
configHASHCAT_MAX_RUNTIME
configHASHCAT_MAX_OUTPUT_SIZE
configHASHCAT_TIMEOUT
configHASHCAT_QUICK_TIMEOUT
configHASHCAT_BENCHMARK_TIMEOUT
configHASHCAT_MAX_HASH_LENGTH
configHASHCAT_MAX_PATH_LENGTH
configHASHCAT_MAX_PLAINTEXT_LENGTH
configHASHCAT_DEFAULT_TIME_LIMIT_PER_HASH
configHASHCAT_MAX_MASK_LENGTH
configHASHCAT_MAX_CHARSET_LENGTH
configHASHCAT_MAX_HASH_TYPE
configHASHCAT_MAX_OUTPUT_LINES
configHASHCAT_MAX_LINE_LENGTH
configHASHCAT_SAFE_DIRS"": "C:\\wordlists"
configHASHCAT_DEFAULT_WORDLISTS
configHASHCAT_DEFAULT_RULES
configHASHCAT_LOG_LEVELLogging level: DEBUG, INFO, WARNING, ERROR (default: DEBUG)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

23/23 tools missing one or more hints — identify_hash (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); crack_hash (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); benchmark_hashcat (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +20 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

4 tools perform destructive updates without destructiveHint — identify_hash deletes at line 375 (os.unlink(safe_filename)); crack_hash deletes at line 519 (os.unlink(os.path.join(HASHCAT_DIR, safe_filename))); show_cracked_hashes deletes at line 694 (os.unlink(hash_file))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

3 tools describe read intent but their handlers mutate — show_cracked_hashes (line 692: result = subprocess.run(cmd, capture_output=True, text=True, timeout=HASHCAT_QUICK_TIMEOUT)); get_backend_info (line 710: result = subprocess.run([HASHCAT_PATH, "-I"], capture_output=True, text=True, timeout=HASHCAT_QUICK_); get_gpu_status (line 1042: result = subprocess.run([HASHCAT_PATH, "-I"], capture_output=True, text=True, timeout=HASHCAT_QUICK_)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

20/23 tool handlers declare input schemas (87%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

3 tools have description/behavior mismatches: show_cracked_hashes: description implies read-only but handler writes/deletes/executes; get_backend_info: description implies read-only but handler writes/deletes/executes; get_gpu_status: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/mordavid-hashcat-mcp-17n3ns?variant=verified)](https://m8ven.ai/mcp/mordavid-hashcat-mcp-17n3ns)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 41b6fc6d0cf072178a9dc9ebc8ffff1b12705d98
code hash: a4b79977e97986863de6a0d45f831ccf334b8b08068fddbb344bc3a7a5ad9627
verified: 8/8/2026, 8:21:32 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client