OnlineCyberTools MCP (280+ filterable tools)

crypto_mysql_password_generator

Read-only

Generate MySQL server-side password hashes for any plaintext. Supports SHA1-based formats (mysql41-57) and caching_sha2_password (mysql80). Returns hash with version, algorithm, and salt info.

Instructions

MySQL Password Hash Generator. Generate the server-side password hash MySQL stores in mysql.user.authentication_string for a given plaintext, across MySQL versions. Use it to build CREATE USER / SET PASSWORD statements or seed test fixtures; use crypto_postgresql_password_generator for PostgreSQL (md5/SCRAM) hashes instead, and crypto_password_generator to invent a new random plaintext rather than hash one. Runs locally on the input you provide: read-only, non-destructive, contacts no database or external service, and is rate-limited (30 requests/min anonymous). SHA1-based formats (mysql41/5/55/56/57) are deterministic; the mysql80/mysql8 caching_sha2_password format uses a fresh random salt, so its hash differs on every call. Returns the hash plus its version label, algorithm, format, and (for 8.0) salt and iterations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "password": "<password>"
    },
    "name": "crypto_mysql_password_generator"
  }
}

Input Schema

Name	Required	Description	Default
`password`	Yes	Plaintext password to hash. Required and non-empty.
`version`	No	Target MySQL format. mysql41/5/55/56/57 produce the SHA1(SHA1()) PASSWORD() hash; mysql80/mysql8 produce a salted caching_sha2_password hash; old_mysql/mysql323 produce the deprecated, insecure pre-4.1 hash.	mysql57

Output Schema

Name	Required	Description
`original`	No	The plaintext password, echoed back.
`hash`	No	The MySQL-format password hash (e.g. *HEX, or $A$005$... for 8.0).
`version`	No	Human-readable label of the MySQL format used.
`algorithm`	No	Hash algorithm, e.g. SHA1(SHA1(password)) or PBKDF2-SHA256.
`format`	No	Description of the output encoding/format.
`iterations`	No	PBKDF2 iteration count (caching_sha2_password / mysql80 only).
`salt`	No	Base64 random salt used (caching_sha2_password / mysql80 only).
`warning`	No	Present only for deprecated old_mysql/mysql323 formats.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.1Jun 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties

Added value: +{
+  "password": {
+    "description": "Plaintext password to hash. Required and non-empty.",
+    "examples": [
+      "s3cret"
+    ],
+    "minLength": 1,
+    "type": "string"
+  },
+  "version": {
+    "default": "mysql57",
+    "description": "Target MySQL format. mysql41/5/55/56/57 produce the SHA1(SHA1()) PASSWORD() hash; mysql80/mysql8 produce a salted caching_sha2_password hash; old_mysql/mysql323 produce the deprecated, insecure pre-4.1 hash.",
+    "enum": [
+      "mysql41",
+      "mysql5",
+      "mysql55",
+      "mysql56",
+      "mysql57",
+      "mysql80",
+      "mysql8",
+      "old_mysql",
+      "mysql323"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "password"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "algorithm": {
+      "description": "Hash algorithm, e.g. SHA1(SHA1(password)) or PBKDF2-SHA256.",
+      "type": "string"
+    },
+    "format": {
+      "description": "Description of the output encoding/format.",
+      "type": "string"
+    },
+    "hash": {
+      "description": "The MySQL-format password hash (e.g. *HEX, or $A$005$... for 8.0).",
+      "type": "string"
+    },
+    "iterations": {
+      "description": "PBKDF2 iteration count (caching_sha2_password / mysql80 only).",
+      "type": "integer"
+    },
+    "original": {
+      "description": "The plaintext password, echoed back.",
+      "type": "string"
+    },
+    "salt": {
+      "description": "Base64 random salt used (caching_sha2_password / mysql80 only).",
+      "type": "string"
+    },
+    "version": {
+      "description": "Human-readable label of the MySQL format used.",
+      "type": "string"
+    },
+    "warning": {
+      "description": "Present only for deprecated old_mysql/mysql323 formats.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds that it runs locally, contacts no database or external service, is rate-limited (30 req/min), and explains deterministic vs non-deterministic behavior (SHA1-based formats are deterministic, mysql80 uses random salt). This goes beyond annotations.

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 a single well-structured paragraph, front-loading the main purpose and use cases. It covers key points without excessive verbosity. Could be slightly more concise but overall effective.

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 (2 parameters, enum, simple behavior), the description covers purpose, parameters, usage, behavior, rate limits, and output (returns hash, version, algorithm, format, salt, iterations). No output schema provided but description adequately hints at return structure.

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 covers both parameters (password and version) with descriptions and examples. The description adds context about version-specific formats (e.g., mysql80 uses caching_sha2_password with random salt) and behavior differences, providing useful nuance 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 generates MySQL password hashes for a given plaintext across versions. It specifies the exact use case (building CREATE USER/SET PASSWORD statements or test fixtures) and distinguishes from sibling tools like crypto_postgresql_password_generator and crypto_password_generator.

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 provides when to use (for MySQL password hash generation) and when not to use (for PostgreSQL, use crypto_postgresql_password_generator; for random plaintext, use crypto_password_generator). Also notes it runs locally, is read-only, non-destructive, and rate-limited.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server