Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_postgresql_password_generator

Read-only

Hash a plaintext password into PostgreSQL credential format for roles. Supports md5, scram_sha256, plain, and crypt to build CREATE/ALTER ROLE statements.

Instructions

PostgreSQL Password Hash Generator. Hash a plaintext password into the credential format a PostgreSQL server stores for a role, across PostgreSQL versions. Use it to build CREATE ROLE / ALTER ROLE statements, populate pg_hba.conf or test fixtures; use crypto_mysql_password_generator for MySQL 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). The md5 format is deterministic; scram_sha256 and crypt use a fresh random salt, so their hash differs on every call. Returns the hash plus its version label, algorithm, format, and (where applicable) salt, iterations, and a plaintext-insecurity warning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesPlaintext password to hash. Required and non-empty.
usernameNoRole name mixed into the md5 hash (md5 is MD5 of password plus username). Defaults to postgres.postgres
versionNoTarget format. md5 produces the legacy md5-prefixed hash (PostgreSQL under 10); scram_sha256 produces a salted SCRAM-SHA-256 verifier (PostgreSQL 10 and later); plain returns the unencrypted password (HIGHLY INSECURE); crypt produces a Unix MD5 modular-crypt hash.md5

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe plaintext password, echoed back.
usernameNoThe role name used (relevant for the md5 format).
hashNoThe PostgreSQL-format password hash or verifier.
versionNoHuman-readable label of the format used.
algorithmNoHash algorithm used, for example MD5 of password plus username, or SCRAM-SHA-256.
formatNoDescription of the output encoding format.
iterationsNoPBKDF2 iteration count (scram_sha256 only).
saltNoSalt used (scram_sha256 base64 salt, or crypt modular-crypt salt).
warningNoPresent only for the plain format, warning the password is unencrypted.
Behavior5/5

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

Annotations already show readOnlyHint=true and destructiveHint=false. The description adds critical context: runs locally, contacts no database, rate-limited (30 req/min), deterministic vs non-deterministic behavior for different algorithms, and returns hash with metadata (version, algorithm, salt, etc.).

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?

Single paragraph with front-loaded purpose, then usage, alternatives, behavioral notes, algorithm details, and return structure. Every sentence earns its place; no fluff.

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 description, annotations, and output schema, this is highly complete. It covers purpose, when to use/avoid, behavioral traits, algorithm details, and return value structure. No obvious gaps for a deterministic input-output tool.

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?

Schema coverage is 100% with descriptive parameter fields. The description adds little beyond schema for password and username, but clarifies version algorithm behavior (deterministic for md5, random salt for others). This adds marginal value over schema, so baseline 3 is appropriate.

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 explicitly states it hashes passwords into PostgreSQL credential formats, lists use cases (CREATE ROLE statements, pg_hba.conf, test fixtures), and distinguishes from siblings crypto_mysql_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?

Provides explicit when-to-use context and alternatives: 'use crypto_mysql_password_generator for MySQL hashes instead, and crypto_password_generator to invent a new random plaintext rather than hash one.' Also notes it runs locally.

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