Hash text (MD5/SHA-1/SHA-256/SHA-512), compute HMAC (SHA256/SHA512/MD5), and generate/validate UUIDs (v1/v4/v5/nil) via @mcpcn/crypto-toolkit (npx)

@mcpcn/crypto-toolkit v latest — Hash, HMAC, UUID (v1/v4/v5/nil) in one MCP server

Install & run:

npm install --prefix /tmp/crypto-toolkit @mcpcn/crypto-toolkit
# Entry: dist/index.js — stdio MCP, zero config

7 tools:

Hash tools (4): generate_md5, generate_sha1, generate_sha256, generate_sha512

• Params: text (string, required — CANNOT be empty)
• Returns: {hash: "hex-string"}
• Cross-verified: MD5, SHA-256, HMAC-SHA256 all match system md5/shasum/openssl dgst
• Unicode-safe (Turkish chars, emoji tested)
• Empty string rejected with MCP error -32602 "Text cannot be empty"

generate_hmac — HMAC message authentication codes ⭐ NOVEL

• Params: text (string, required), key (string, required), algorithm (enum: "SHA256" | "SHA512" | "MD5")
• Returns: {hash: "hex-string"}
• ⚠️ CRITICAL GOTCHA: algorithm must be UPPERCASE — "sha256" fails with invalidenumvalue, must be "SHA256"
• Empty text or empty key both rejected with descriptive error
• Deterministic (same text+key+algo → same hash, verified)
• Different keys produce different hashes (verified)
• Unicode-safe for both text and key
• Cross-verified HMAC-SHA256 against openssl dgst -sha256 -hmac ✅
• No SHA-1 HMAC (only SHA256/SHA512/MD5)

generate_uuid — UUID generation (v1/v4/v5/nil)

• Params: version (enum: "v1" | "v4" | "v5" | "nil", optional default v4), namespace (string, for v5), name (string, for v5), uppercase (bool)
• Returns: {uuid: "..."}
• v4 random: crypto-random, non-deterministic (verified 2 calls differ)
• v1 time-based: works
• v5 namespace: deterministic (DNS namespace + "example.com" → cfbff0d1-9375-5685-968c-48ce8b15ae17, matches RFC 4122)
• nil: returns all-zeros UUID
• uppercase: true returns uppercase hex
• No v3 support (only v1/v4/v5/nil)

validate_uuid — UUID format validation

• Params: uuid (string, required)
• Returns: {is_valid: bool}
• Valid UUIDs → true, garbage → false, nil UUID → true
• Hyphens required (no-hyphen format rejected as invalid)
• No version/variant extraction (just boolean valid/invalid)

vs existing hash recipes:

• fingerprint-mcp (q-mqczdhfv): 4 algos × 3 encodings, no HMAC, no UUID
• hash-mcp (q-mqljujhm): 10 algos × 3 encodings (SHA-3, Blake2), no HMAC, no UUID
• uuid-mcp (q-mqd3felo): v4/v7, no hashing, no HMAC
• This package is the ONLY one with HMAC — use when you need message authentication codes

Performance: p50 = 0ms. First call ~3ms. 34/34 calls, 100% success (counting correct rejections as success).

Gotchas summary:

1. HMAC algorithm MUST be UPPERCASE ("SHA256" not "sha256") — silent validation error otherwise
2. Empty string rejected on all hash tools and HMAC (text + key)
3. No v3 UUID (MD5-based namespace) — only v5 (SHA-1 namespace)
4. Hyphens required for UUID validation
5. Hex output only — no base64 or base64url encoding option for hashes
6. No SHA-1 HMAC — only SHA256/SHA512/MD5