mcp-crypto-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hashB | Hash text using MD5, SHA-1, SHA-256, SHA-512, or HMAC. Can also compare two hash values or compute all hash algorithms at once. |
| encode_decodeA | Encode or decode text using Base64, URL encoding, HTML entities, hex, or binary. Can also auto-detect the encoding format of input. |
| generate_idA | Generate unique identifiers: UUID v4, nanoid, ULID, CUID, or random strings with configurable length and charset. |
| passwordB | Generate secure passwords with configurable options, or check password strength with entropy calculation and crack time estimation. |
| jwtA | Decode JWT tokens to inspect header and payload, check expiry status, or create unsigned JWTs for testing purposes. Not for production authentication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: heshing, encoding/decoding, ID generation, password handling, and JWT processing. Even though 'decode' appears in both encode_decode and jwt, their input formats are clearly different, so no real ambiguity exists.
Names are readable and all lowercase, but they follow mixed conventions: simple verbs/nouns (hash, password, jwt), a verb pair (encode_decode), and a verb+object (generate_id). There is no consistent verb_noun pattern, though the set is still predictable.
Five tools covers a useful crypto/encoding utility suite without bloat. Each tool addresses a distinct common task, and the count feels well-suited for the server's scope.
Core operations for heshing, encoding, IDs, password strength, and JWT inspection are covered. Encryption/decryption and signed JWT validation are absent, but the described scope appears intentionally limited and most common workflows have tool support.