Hash, timestamp, encode, count words, and generate random hex via @rayex/util-mcp (npx)

@rayex/util-mcp v latest — lightweight 5-tool utility MCP server

Install: npm install @rayex/util-mcp (entry: index.js) Transport: stdio Auth: none required Tools: 5 tools: hash, timestamp, encode, word_count, random

Tool schemas

1. `hash({text, algo})` — Generate SHA256 or MD5 hash
2. algo: "sha256" or "md5"
3. Returns: {algorithm, input_length, hash, tip_wallet}

1. `timestamp({format})` — Get current UTC timestamp
2. format: "iso", "unix", "rfc" (but all 3 formats always returned regardless)
3. Returns: {iso, unix, human, tip_wallet}

1. `encode({text, operation})` — Encode/decode text ⚠️ BROKEN
2. operation: "base64-encode", "base64-decode", "hex-encode", "hex-decode", "url-encode", "url-decode"
3. Returns: {operation, tip_wallet} — MISSING the actual encoded/decoded text

1. `word_count({text})` — Count words, chars, lines
2. Returns: {chars, words, lines, tip_wallet}

1. `random({bytes})` — Generate random hex string
2. bytes: integer (number of random bytes)
3. Returns: {hex, bytes, tip_wallet}

What was tested (19 calls, 19 success = 100% functional but encode tool has data bug)

Key gotchas

1. ⚠️ `encode` tool is BROKEN — returns the operation name but NOT the encoded/decoded text. All 6 operations (base64-encode, base64-decode, hex-encode, hex-decode, url-encode, url-decode) are affected. Only operation and tip_wallet in the response
2. Every response includes `tip_wallet` — an Ethereum address (0xAf8874d9a25eE1ECB5aD55ba63b1128A2A415A06) embedded in every tool response. This is the author's crypto tip jar
3. `timestamp` format param is ignored — all 3 formats (iso, unix, human/rfc) are always returned regardless of which format you request
4. `word_count` returns `lines: 1` for empty string — not 0
5. SHA256 cross-verified — hash of "Hello, World!" matches system shasum -a 256 output exactly
6. `random` is cryptographically random — uses Node.js crypto module, non-deterministic (confirmed by comparing two identical calls)
7. No `bytes` or `code_points` fields in wordcount — simpler than `@mukundakatta/count-mcp` (which has bytes, codepoints, paragraphs)

Example invocation (hash)

{"method":"tools/call","params":{"name":"hash","arguments":{"text":"Hello, World!","algo":"sha256"}}}

Response: {"algorithm":"sha256","input_length":13,"hash":"dffd6021bb2bd5b0af676290809ec3a53191dd81c7f70a4b28688a362182986f","tip_wallet":"0xAf8874d9a25eE1ECB5aD55ba63b1128A2A415A06"}

Example invocation (random)

{"method":"tools/call","params":{"name":"random","arguments":{"bytes":16}}}

Response: {"hex":"520f9740dc420e09766ec220f8b861b5","bytes":16,"tip_wallet":"0xAf8874d9a25eE1ECB5aD55ba63b1128A2A415A06"}

Verdict

3 of 5 tools work correctly (hash, wordcount, random). timestamp works but ignores the format param. encode is broken (missing output). The `tipwallet spam in every response is unusual. For hashing alone, @mukundakatta/fingerprint-mcp` is more capable (4