Skip to main content
Glama
Post-Quantum Cryptography MCP Server

Post-Quantum Cryptography MCP Server

by scottdhughes

Related Servers

Alternatives to Post-Quantum Cryptography MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to discover post-quantum cryptography and quantum-inspired optimization packages, retrieve ready-to-run code snippets, detect classical-only cryptography in code or configuration, and receive migration guidance.
      4
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Post-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.
      16
      16
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to sign and verify post-quantum attestations of AI agent actions (mint, trajectory, coherence) using ML-DSA-65 signatures, with offline verification always free.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Defense-grade cryptographic compliance and analysis tools for MCP, including FIPS 140-3 validation, CNSA 2.0 analysis, post-quantum readiness assessment, and classical cipher utilities.
      18
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to sign and verify actions with ML-DSA-65 digital signatures, providing tamper-proof receipts that can be verified offline without any secrets.
      MIT

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Core PQC operations, hybrid operations, key-store operations, and envelope inspection are clearly separated by distinct names and descriptions. Minor overlap exists between pqc_compare/pqc_benchmark and pqc_algorithm_info/pqc_security_analysis, but the descriptions make their purposes distinguishable.

    Naming Consistency4/5

    All tools use a consistent pqc_ snake_case prefix, and the hybrid/auth namespaces are predictable. A few tools use noun-style names (pqc_algorithm_info, pqc_security_analysis, pqc_fingerprint, pqc_envelope_inspect) rather than strict verb_noun, but the pattern remains readable.

    Tool Count3/5

    At 25 tools, the surface is at the heavy end for this domain. Most tools earn their place, but some informational/benchmarking tools could potentially be consolidated.

    Completeness5/5

    The server covers algorithm discovery, key generation and storage, KEM encapsulation/decapsulation, signing/verification, hashing, hybrid sealed envelopes, authenticated envelopes, inspection, and benchmarking. No obvious lifecycle or workflow gaps are apparent for the stated PQC domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues