Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_scrypt

Read-only

Derive a memory-hard key using scrypt to resist GPU and ASIC cracking. Tune N, r, p parameters for desired strength.

Instructions

Scrypt Password Hash Generator. Generate a memory-hard scrypt password hash and key derivation from a password and tunable cost parameters (N, r, p, key length). scrypt deliberately consumes large amounts of RAM to resist GPU/ASIC cracking; use it when you want memory-hardness. Prefer crypto_argon2 or crypto_bcrypt for general password storage; use crypto_pbkdf2 when only iteration count matters; use crypto_scrypt_verify to check a password against an existing scrypt hash. A random 16-byte salt is generated when salt is omitted, so output is non-deterministic between calls. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the derived key (hex and base64), an encoded hash string, the salt, the parameters used, and a strength analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password to derive the scrypt hash from. Required and must be non-empty.
NNoCPU/memory cost factor; must be a power of 2 between 2 and 1048576. Higher values increase both time and memory cost (32768 or above recommended).
rNoBlock-size factor (1 to 256); scales memory usage. 8 is the standard value.
pNoParallelization factor (1 to 256); number of independent mixing operations.
lengthNoDerived key length in bytes (16 to 128).
saltNoOptional salt as a hexadecimal string (even number of hex digits). When omitted or empty, a random 16-byte salt is generated, making output non-deterministic.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNoDerived key encoded as a hexadecimal string.
base64HashNoDerived key encoded as base64.
formattedHashNoEncoded hash string in the format $scrypt$N=<N>,r=<r>,p=<p>$<saltHex>$<base64DerivedKey>, accepted by crypto_scrypt_verify.
algorithmNoAlgorithm identifier; always scrypt.
parametersNoThe cost parameters used for the derivation.
saltNoSalt used for the derivation, in hexadecimal (random when none supplied).
saltLengthNoLength of the hex salt string.
securityNoStrength analysis of the chosen parameters.
Behavior5/5

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

Discloses that it runs locally, is read-only and non-destructive, contacts no external service, is rate-limited, and generates random salt for non-deterministic output. Aligns with annotations (readOnlyHint, destructiveHint).

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?

Two well-structured paragraphs: first states purpose and usage, then details behavior and output. Every sentence adds value, no redundancy.

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?

Output schema exists, and description lists return fields (derived key, hash string, salt, parameters, strength analysis). With 100% param coverage and clear behavior, it's fully complete.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds context on N being a power of 2, r as standard, p for independent mixing, length as derived key bytes, and salt optional with random generation, plus explains memory-hardness.

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 a scrypt password hash and key derivation, explicitly contrasting with siblings like crypto_argon2, crypto_bcrypt, crypto_pbkdf2, and crypto_scrypt_verify.

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?

Explicitly specifies when to use scrypt ('when you want memory-hardness') and provides alternatives for different use cases (argon2/bcrypt for general storage, pbkdf2 for iteration counts, scrypt_verify for checking).

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