Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_pbkdf2

Read-only

Derive a PBKDF2 password hash from a plaintext password using a chosen HMAC digest, iteration count, and key length, returning the derived key and a self-describing encoded hash.

Instructions

PBKDF2 Hash Generator. Derive a PBKDF2 password hash from a plaintext password using a chosen HMAC digest, iteration count, and key length, returning the derived key plus a self-describing encoded hash. Use this to create a new hash; use crypto_pbkdf2_verify to check a password against one. PBKDF2 is the legacy/FIPS-friendly KDF — prefer crypto_argon2 (memory-hard) or crypto_bcrypt for new password storage, and crypto_scrypt for memory-hard derivation. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, rate-limited (5 requests/min anonymous). When no salt is supplied a random 16-byte salt is generated, so output is non-deterministic. Returns the derived key (hex and base64), a passlib-style $pbkdf2-... string, the salt, the resolved parameters, and a strength analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password (passphrase) to derive a key from. Required and non-empty.
algorithmNoHMAC digest backing the derivation. sha256/sha512 recommended; md5 and sha1 are cryptographically weak.sha256
iterationsNoNumber of PBKDF2 rounds. Higher is slower and stronger.
lengthNoDerived key length in bytes.
saltNoOptional salt string (8–128 characters). If omitted or empty, a random 16-byte (32 hex char) salt is generated and returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoThe plaintext password (echoed from the request).
hashNoDerived key encoded as lowercase hex.
base64HashNoDerived key encoded as base64.
formattedHashNoPasslib-style encoded hash: $pbkdf2-<algorithm>$<iterations>$<salt>$<base64DerivedKey>.
algorithmNoResolved digest token: sha1, sha256, sha384, sha512, or md5.
algorithmNameNoHuman-readable algorithm name, e.g. SHA-256.
iterationsNoIteration count used.
lengthNoDerived key length in bytes.
saltNoSalt used (supplied value or the generated 32-hex-char salt).
saltLengthNoCharacter length of the salt.
securityNoStrength analysis of the chosen parameters.
generatedAtNoISO 8601 timestamp of generation.
verifiedNoSelf-check that the generated formattedHash verifies against the password (always true on success).
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by detailing non-deterministic output when no salt is supplied, local execution, and return of derived key, encoded hash, salt, and strength analysis. No contradictions.

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?

The description is 4-5 sentences, well-structured, and front-loaded with the tool's main purpose. Every sentence adds essential information without redundancy or fluff, making it efficient for an AI agent to parse.

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 has 5 parameters, 1 required, an output schema, and annotations, the description covers purpose, usage guidelines, behavioral traits (non-determinism, local execution, rate limit), and key return fields. It is complete for an agent to decide and invoke correctly.

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%, so baseline is 3. The description adds value by explaining that if no salt is supplied, a random 16-byte salt is generated, making output non-deterministic. It also mentions the salt length range (8–128 characters) aligning with schema min/max. This enriches parameter understanding beyond schema.

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 'PBKDF2 Hash Generator' and explains it derives a hash from a plaintext password, specifying the tool's verb and resource. It distinguishes from siblings by naming crypto_pbkdf2_verify and alternative KDFs (argon2, bcrypt, scrypt).

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 says 'Use this to create a new hash; use crypto_pbkdf2_verify to check a password against one.' Provides guidance on when to prefer other KDFs and mentions rate limiting (5 requests/min anonymous), giving clear context for selection.

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