Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

crypto_bcrypt

Read-only

Hash a plaintext password using bcrypt with a configurable cost factor. Generates a fresh salt each call, returning the hash string, cost, salt, and strength analysis.

Instructions

Bcrypt Password Hasher. Hash a plaintext password with bcrypt at a chosen cost factor, generating a fresh random salt on every call. Use this to create a new stored password hash; use crypto_bcrypt_verify instead to check a password against an existing hash, and crypto_argon2 / crypto_scrypt / crypto_pbkdf2 for the other adaptive/memory-hard password KDFs. Runs locally with PHP password_hash on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (5 requests/minute for anonymous callers). Because a new salt is drawn each call, the same password yields a different hash each time. Returns the bcrypt hash string plus the cost, salt, parsed format breakdown, and a strength analysis of the chosen cost factor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password to hash. Must be non-empty.
costNoBcrypt cost factor (log2 of the key-expansion rounds); higher is slower and more brute-force resistant. 12 is recommended for production. Values outside 4-15 are rejected with a 400.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoThe plaintext password that was hashed (echoed back from the request).
hashNoThe bcrypt hash in modular crypt format $2y$<cost>$<22charSalt><31charDigest>.
costNoThe cost factor used to generate the hash.
algorithmNoAlways "bcrypt".
saltNoThe 22-character base64 salt parsed from the generated hash.
durationNoTime taken to generate the hash, in seconds (rounded to 3 decimals).
infoNoFields parsed from the generated bcrypt hash.
formatNoStructural breakdown of the hash string.
securityNoStrength analysis of the chosen cost factor.
errorNoPresent only on a 4xx/5xx error response (e.g. missing password or cost out of range); absent on success.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cost / default
      Added value: +12
    • addedInput schema / properties / cost / description
      Added value: +"Bcrypt cost factor (log2 of the key-expansion rounds); higher is slower and more brute-force resistant. 12 is recommended for production. Values outside 4-15 are rejected with a 400."
    • addedInput schema / properties / cost / maximum
      Added value: +15
    • addedInput schema / properties / cost / minimum
      Added value: +4
    • addedInput schema / properties / password / description
      Added value: +"The plaintext password to hash. Must be non-empty."
    • addedInput schema / properties / password / examples
      Added value: +[
+  "correct horse battery staple"
+]
    • addedInput schema / properties / password / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "password",
-  "cost"
-]New value: +[
+  "password"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "algorithm": {
+      "description": "Always \"bcrypt\".",
+      "type": "string"
+    },
+    "cost": {
+      "description": "The cost factor used to generate the hash.",
+      "type": "integer"
+    },
+    "duration": {
+      "description": "Time taken to generate the hash, in seconds (rounded to 3 decimals).",
+      "type": "number"
+    },
+    "error": {
+      "description": "Present only on a 4xx/5xx error response (e.g. missing password or cost out of range); absent on success.",
+      "type": "string"
+    },
+    "format": {
+      "description": "Structural breakdown of the hash string.",
+      "properties": {
+        "length": {
+          "description": "Total character length of the hash string.",
+          "type": "integer"
+        },
+        "parts": {
+          "description": "The hash split into its component substrings.",
+          "properties": {
+            "cost": {
+              "description": "Cost factor read from the hash, or null if it could not be parsed.",
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "hash": {
+              "description": "The digest substring following the salt.",
+              "type": "string"
+            },
+            "identifier": {
+              "description": "The 3-character algorithm identifier (e.g. $2y).",
+              "type": "string"
+            },
+            "salt": {
+              "description": "The 22-character salt substring.",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "structure": {
+          "description": "Human-readable layout label: $version$cost$salt_and_hash.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "hash": {
+      "description": "The bcrypt hash in modular crypt format $2y$<cost>$<22charSalt><31charDigest>.",
+      "type": "string"
+    },
+    "info": {
+      "description": "Fields parsed from the generated bcrypt hash.",
+      "properties": {
+        "cost": {
+          "description": "Cost factor read from the hash.",
+          "type": "integer"
+        },
+        "full_length": {
+          "description": "Total character length of the hash string.",
+          "type": "integer"
+        },
+        "hash_part": {
+          "description": "The 31-character base64 digest segment.",
+          "type": "string"
+        },
+        "is_valid_format": {
+          "description": "True when the hash matched the expected bcrypt structure.",
+          "type": "boolean"
+        },
+        "salt": {
+          "description": "The 22-character base64 salt segment.",
+          "type": "string"
+        },
+        "version": {
+          "description": "Algorithm version prefix: $2a, $2b, $2x, or $2y.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "password": {
+      "description": "The plaintext password that was hashed (echoed back from the request).",
+      "type": "string"
+    },
+    "salt": {
+      "description": "The 22-character base64 salt parsed from the generated hash.",
+      "type": "string"
+    },
+    "security": {
+      "description": "Strength analysis of the chosen cost factor.",
+      "properties": {
+        "cost_factor": {
+          "description": "The cost factor analysed.",
+          "type": "integer"
+        },
+        "estimated_time": {
+          "description": "Rough hashing-time estimate for this cost, e.g. \"1-3s\".",
+          "type": "string"
+        },
+        "iterations": {
+          "description": "Key-expansion rounds (2 ^ cost_factor).",
+          "type": "integer"
+        },
+        "recommendation": {
+          "description": "Advisory note on whether to adjust the cost factor.",
+          "type": "string"
+        },
+        "security_level": {
+          "description": "Qualitative rating, e.g. \"Strong - Good for high-security applications\".",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, the description specifies local execution, read-only and non-destructive nature, no external service contact, rate limiting, and non-idempotent behavior due to fresh salt per call. 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?

Every sentence provides distinct value: purpose, usage, behavior, return details. Front-loaded and no redundant or vague phrasing.

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?

Covers all necessary aspects: purpose, when to use, behavior, parameters with recommendations, and output summary (hash string, cost, salt, etc.). With output schema present, return values are adequately described.

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?

Input schema has 100% coverage with descriptions and examples, but the description adds context like recommended cost (12), valid range, and the effect of salt. This adds marginal value 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 hashes a plaintext password with bcrypt for creating new stored password hashes, and differentiates it from sibling tools like crypto_bcrypt_verify and other KDFs.

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 (create new hash) and when to use alternatives (crypto_bcrypt_verify for verification, other KDFs for different algorithms). Also mentions rate limiting for anonymous callers.

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