Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_argon2_verify

Read-onlyIdempotent

Verify a plaintext password against an encoded Argon2 hash. Automatically reads the Argon2 variant, version, and cost parameters from the hash string.

Instructions

Argon2 Hash Verifier. Check whether a plaintext password matches an existing Argon2 hash using PHP's password_verify, which reads the variant, version, and m/t/p parameters from the encoded hash itself. Use this to verify a candidate password; use crypto_argon2 instead to generate a new hash. Runs server-side on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (5 requests/min, 30/hour, 100/day for anonymous callers; CAPTCHA may trigger above 20/hour). Returns whether the password matched plus the parameters parsed from the hash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password to test against the hash.
hashYesThe encoded Argon2 hash to verify against, in PHP's PHC format produced by crypto_argon2: $argon2id$v=19$m=65536,t=4,p=3$<saltBase64>$<hashBase64>. The variant, version, and m/t/p cost parameters are read from this string; argon2i and argon2id are both accepted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoThe plaintext password that was tested (echoed from the request).
hashNoThe encoded Argon2 hash that was checked (echoed from the request).
verifiedNoTrue when the password matches the supplied hash.
infoNoComponents parsed from the hash. Contains only {error} when the hash has fewer than six $-delimited segments.
verifiedAtNoISO 8601 timestamp of when verification ran.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds critical context: runs server-side, rate limits (5/min, 30/hr, 100/day), CAPTCHA trigger, and return type (match status + parsed parameters). 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?

Three concise sentences: purpose, usage vs alternative, and behavioral details (rate limits, output). Front-loaded with key info; every sentence adds value.

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 simplicity (2 required params, output schema exists), the description covers purpose, usage, behavior, rate limits, and output. Annotations and schema are rich, so no gaps remain.

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

Parameters3/5

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

Input schema covers both parameters fully (100% coverage with descriptions and examples). Description adds that hash includes cost parameters, but this is already in the schema's description of 'hash'. No additional meaningful semantics 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 the tool's purpose ('verify a plaintext password against an Argon2 hash') and distinguishes it from the sibling 'crypto_argon2' (generate new hash). The verb 'verify' and resource 'Argon2 hash' are specific.

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 when to use ('to verify a candidate password') and when not ('use crypto_argon2 instead to generate a new hash'). Also notes behavior: read-only, non-destructive, no external service, and rate limits.

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