io.github.daedalus/mcp-cryptography
Related Servers
Alternatives to io.github.daedalus/mcp-cryptography
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables cryptographic operations including hashing, encoding/decoding, ID generation, password tools, and JWT inspection via MCP.536 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables management of Azure Key Vault secrets and certificates, including creation, retrieval, deletion, format conversion (PEM/CRT to PFX), certificate chain imports, and self-signed certificate generation.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to construct SHA-256 Merkle trees, generate and verify state inclusion proofs, validate JWT HMAC signatures, perform Schnorr zero-knowledge proofs, and enforce nonce replay protection for immutable state attestation.7MIT
- AlicenseNot gradedqualityDmaintenanceProvides cryptographic identity and signing capabilities for AI agents, enabling them to create persistent identities, sign actions with private keys, and allow external systems to verify the authenticity and provenance of agent-initiated operations.4MIT
- AlicenseNot gradedqualityBmaintenanceProvides cryptographic hash and HMAC computation for text, supporting algorithms like md5, sha1, sha256, sha384, and sha512. All operations are performed locally without transmitting or storing input data.160 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to construct SHA-256 Merkle trees and generate/verify inclusion proofs, validate JWT HMAC-SHA256 claims, run Schnorr zero-knowledge identification, and enforce constant-time secret comparison with nonce replay protection for tamper-evident state attestation. It runs as a zero-dependency, stdlib-only MCP stdio server for clients such as Claude Desktop, Cursor, and Windsurf.7MIT
TDQS
Scored across 22 tools
Tools are generally distinct, but generate_symmetric_key and generate_random_bytes both produce random data, which could cause confusion; however, descriptions clarify their purposes.
Naming conventions vary: some tools use verb_noun (generate_symmetric_key), others use algorithm_verb (fernet_encrypt, aes_encrypt), and hash_sha256 mixes verb and algorithm. Inconsistency reduces predictability.
22 tools cover a broad cryptography domain; while slightly above the typical 3-15 range, each tool has a clear purpose and the count is justified.
Major cryptographic operations are covered: symmetric/asymmetric encryption, hashing, signing, key derivation, certificates. Missing modern algorithms like Ed25519 or ECDSA are minor gaps.