Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_pbkdf2_verify

Read-onlyIdempotent

Verify a plaintext password against a PBKDF2 hash by recomputing the derivation from the hash's algorithm, iterations, salt, and key length. Returns match status and parameter strength analysis.

Instructions

PBKDF2 Hash Verifier. Check whether a plaintext password matches an existing PBKDF2 hash, recomputing the derivation from the digest algorithm, iteration count, key length, and salt encoded in the hash string. Use this to verify a candidate password; use crypto_pbkdf2 instead to generate a new hash. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (5 requests/min for anonymous callers). Returns whether the password matched, the parameters parsed from the hash, and a strength analysis of those parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password to test against the hash.
hashYesThe encoded PBKDF2 hash to verify against. Two formats are accepted: the passlib-style string produced by crypto_pbkdf2, $pbkdf2-<algorithm>$<iterations>$<saltHex>$<base64DerivedKey>, or a colon-delimited <algorithm>:<iterations>:<salt>:<derivedKeyHexOrBase64>. The digest algorithm, iteration count, salt, and key length are read from this string to recompute the derivation; no separate algorithm, iterations, length, or salt fields are supplied.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoThe plaintext password that was tested (echoed from the request).
hashNoThe encoded hash that was verified against (echoed from the request).
verifiedNoTrue when the recomputed derivation matches the digest in the supplied hash.
infoNoParameters parsed from the hash. Absent when the hash format is invalid.
securityNoStrength analysis of the parsed parameters. Absent on error.
verifiedAtNoISO 8601 timestamp of when verification ran. Absent on error.
errorNoError message when verification fails (e.g. "Invalid hash format"). Absent on success.
Behavior5/5

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

Adds context beyond annotations: runs locally, read-only, non-destructive, contacts no external service, rate-limited (5 req/min for anonymous callers). No contradiction with annotations.

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?

Three sentences covering purpose, usage, behavior, and return values. Front-loaded with key information, no wasted words.

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?

Complete for a PBKDF2 verification tool: explains what it does, how it works, what it returns (match status, parsed parameters, strength analysis), and has output schema for return values.

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?

Both parameters have detailed descriptions and examples in the schema. The description explains the hash format and that no separate fields are needed, adding meaning beyond the schema which has 100% 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 is a 'PBKDF2 Hash Verifier' and explains that it checks if a plaintext password matches an existing PBKDF2 hash, distinguishing it from the sibling tool crypto_pbkdf2 which generates new hashes.

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 states 'Use this to verify a candidate password; use crypto_pbkdf2 instead to generate a new hash,' providing clear when-to-use and when-not-to-use with an alternative tool name.

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