Crypto

io.github.rog0xPublished by GitHub account rog0xv1.0.2Updated Oct 24, 2026

Hash, encode, UUID, password analysis for AI agents

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that gives an AI assistant hashing, encoding, ID generation, password analysis and JWT inspection tools.

What you can do
Hash text with MD5, SHA-1, SHA-256, SHA-512 or HMAC, compare two hashes, and compute all algorithms at once. Encode and decode Base64, URL, HTML entities, hex and binary, with format auto-detection. Generate UUID v4, nanoid, ULID, CUID or random strings with configurable length and charset. Generate passwords and check strength with entropy and crack-time estimates. Decode JWT headers and payloads, check expiry, and create unsigned JWTs for testing.
When to use it
Useful when an assistant needs to compute checksums or HMACs, convert encoded text, mint identifiers, assess password strength, or inspect a JWT during development and debugging.
Requirements
Runs as a local Node.js process installed from the npm package @rog0x/mcp-crypto-tools; the README shows building it and pointing the MCP client at the built entry file. No accounts, API keys or environment variables are declared.
Before you install
Hashing, encoding, password generation and JWT decoding all handle sensitive input, so anything passed to the tools reaches the local process. The JWT tool can create unsigned tokens, which must not be used as real credentials. Password strength checks estimate crack time and are not a security guarantee.

Installation

In SourceWeft

  1. Open Crypto in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-crypto-tools

Cryptography and encoding tools for AI agents, served via the Model Context Protocol (MCP).

Tools

hash

Hash text using MD5, SHA-1, SHA-256, SHA-512, or HMAC. Compare two hash values. Compute all algorithms at once.

Actions: hash, hmac, compare, hash_all

encode_decode

Encode and decode text using Base64, URL encoding, HTML entities, hex, or binary. Auto-detect encoding format.

Actions: base64_encode, base64_decode, url_encode, url_decode, html_encode, html_decode, hex_encode, hex_decode, binary_encode, binary_decode, detect

generate_id

Generate unique identifiers: UUID v4, nanoid, ULID, CUID, or random strings with configurable length and charset.

Types: uuid, nanoid, ulid, cuid, random

password

Generate secure passwords with configurable character sets, length, and count. Check password strength with entropy calculation and crack time estimation.

Actions: generate, check_strength

jwt

Decode JWT tokens to inspect header and payload, check expiry status, or create unsigned JWTs for testing.

Actions: decode, check_expiry, create_unsigned

Setup

bash
npm installnpm run build

MCP Configuration

Add to your MCP client configuration:

json
{  "mcpServers": {    "crypto-tools": {      "command": "node",      "args": ["D:/products/mcp-servers/mcp-crypto-tools/dist/index.js"]    }  }}

Dependencies

  • @modelcontextprotocol/sdk - MCP server framework
  • Node.js built-in crypto module - all cryptographic operations

No external crypto libraries required.

License

MIT

Source: README.md at commit f433a5e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts