Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_ntlm

Read-onlyIdempotent

Generate NTLM and LM hashes from a plaintext password for Active Directory testing, pass-the-hash simulations, and credential-cracking setup. Computes hashes locally with no external service contact.

Instructions

NTLM and LM Hash Generator. Compute the Windows NTLM (NT) hash and optionally the legacy LM (LAN Manager) hash of a password, for Active Directory labs, pass-the-hash testing, and credential-cracking setup. NTLM is MD4 of the UTF-16LE password; LM upper-cases and 14-byte-pads the password, then DES-encrypts the constant "KGS!@#$%" per 7-byte half. This generates hashes from a known password; to recognise an unknown hash string's type instead use crypto_hash_id, and to recover the password behind a hash use crypto_hash_cracker. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/minute for anonymous callers). Returns the requested hashes plus password length, unicode flag, a complexity score, and security warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesPlaintext password to hash. UTF-16LE-encoded for NTLM; upper-cased and truncated to 14 characters for LM.
outputFormatNoHex case of the returned hash strings; hex/lower/lowercase emit lowercase, upper/uppercase emit uppercase.hex
includeHashNoInclude the NTLM (NT) hash in the result.
includeLmNoInclude the legacy LM hash; fails if the runtime has DES disabled, and truncates the password to 14 characters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashesNoComputed hashes, keyed by algorithm; only requested algorithms are present.
password_infoNoAnalysis of the submitted password.
output_formatNoThe output format that was applied.
algorithms_usedNoAlgorithm keys present in hashes (e.g. ntlm, lm).
Behavior5/5

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

Beyond annotations (readOnly, destructive, idempotent), description adds specific behavioral details: runs locally, no external service, rate-limited, and potential failure for LM hash.

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?

Description is thorough and well-structured, but somewhat lengthy. All sentences add value, but could be slightly more terse.

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

Completeness5/5

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

Given the tool's complexity (multiple hash types, algorithms, output fields), the description covers purpose, usage, behavior, parameters, and return values comprehensively.

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

Parameters5/5

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

Description adds deep meaning beyond schema: explains hashing algorithms (MD4, DES), default behavior, and output fields (length, complexity, warnings), complementing the 100% schema coverage.

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 it generates NTLM and LM hashes for Windows security testing, and explicitly distinguishes from siblings like crypto_hash_id and crypto_hash_cracker.

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

Usage Guidelines5/5

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

Description provides explicit guidance on when to use this tool vs. alternatives, including when not to use it (for hash type identification or password recovery).

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/Jambozx/onlinecybertools-mcp-server'

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