Crypto Tools MCP Server
Related Servers
Alternatives to Crypto Tools MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancePost-quantum readiness for AI coding agents: scans code for quantum-vulnerable cryptography (RSA/ECDH/ECDSA/DH) and returns NIST ML-KEM/ML-DSA/SLH-DSA (and hybrid) migration guidance, with fix verification and dependency checks. Content-based, advisory tools only; runs local (npx @quantakrypto/mcp) or as a hosted OAuth endpoint.1615Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables querying NIST CMVP data for FIPS 140 certificate status, validation history, vendor holdings, CVE associations, Modules in Process phases, and upcoming sunset dates through read-only MCP tools.MIT
- AlicenseBqualityCmaintenanceProvides six MCP tools for AI agents to compute post-quantum cryptography migration facts, such as credential sizes, fragment counts, and failure taxonomy, enabling accurate migration decisions without estimation.6Apache 2.0
- AlicenseAqualityAmaintenanceEnables inspection and verification of X.509 certificates and chains, CRLs, OCSP responses, CMS signatures and RFC 3161 timestamps, along with issuing certificates and CSRs, decoding ASN.1/PEM/OIDs, and opening PKCS#8 and PKCS#12 files without ever returning a key byte. Runs entirely offline with no network access, exposing 34 tools to any MCP client.3482 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform quantum-resistant cryptographic operations using NIST-standardized algorithms including ML-KEM, ML-DSA, and SPHINCS+. Supports key generation, encryption, digital signatures, and security analysis for post-quantum cryptography research and development.1MIT
- AlicenseAqualityDmaintenanceEnables cryptographic operations including hashing, encoding/decoding, ID generation, password tools, and JWT inspection via MCP.542 npmMIT
TDQS
Scored across 18 tools
Most tools have distinct purposes: Caesar encrypt/decrypt/crack are clearly different; Vigenere and XOR similarly. Compliance tools (FIPS, CNSA, PQC, combined report) overlap somewhat but descriptions clarify their scope. A few analytical tools (frequency_analysis, detect_cipher_type) are distinct. Overall, minimal confusion.
Names are all lowercase with underscores. Most follow a verb_noun pattern (e.g., generate_key, check_fips_compliance). However, 'frequency_analysis' uses noun_noun and 'rot13' is just a name, deviating from the pattern. Predominantly consistent.
18 tools is slightly above the ideal range (3-15) but still reasonable for the breadth of coverage: classical ciphers, compliance, key management, and analysis. Not excessive; each tool serves a clear function.
The set covers classical ciphers and compliance/audit well, but lacks modern cryptographic operations (AES encryption, hashing, digital signatures). Key management is about metadata, not key pair generation. These are notable gaps for a 'crypto tools' server.