Skip to main content
Glama

Related Servers

Alternatives to qrp-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      B
      maintenance
      A read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.
      210 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, zero-egress MCP clients to scan codebases for post-quantum cryptography and structural issues, inspect standards constraints, verify dependency and candidate-fix safety, generate CycloneDX CBOMs, and map cryptographic assets to compliance mandates before commit or in CI.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server that scans code for security issues (secrets, dependencies, configurations, risky patterns) and integrates with GitHub Copilot in VS Code for automated pre-commit reviews.
      -

    TDQS

    A4.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool occupies a distinct slot in the audit lifecycle: inventory (scan_repo), emit (export_cbom), classify (list_algorithms), compare coverage conditions (compare_coverage), compare findings for closure (prove_closure), and validate detection by seeding (run_self_seeded_control). The descriptions go further than most servers, explicitly naming the neighbouring tool and stating when it, not this one, is correct (e.g. scan_repo vs list_algorithms, compare_coverage vs prove_closure, scan_repo vs export_cbom). The one genuine overlap — scan_repo and export_cbom run the same reading — is resolved by an explicit output-consumer distinction (read here vs send off-machine).

    Naming Consistency5/5

    All six names are snake_case verb_noun constructions (scan_repo, compare_coverage, export_cbom, list_algorithms, prove_closure, run_self_seeded_control) with no casing or style drift. The single long outlier, run_self_seeded_control, is still the same pattern and is descriptive of what it does.

    Tool Count5/5

    Six tools is tightly scoped for a crypto-inventory server and each maps to a non-redundant operation rather than a variation of another. Nothing feels padded or missing at the count level.

    Completeness4/5

    The lifecycle is well covered: scan, export to a standard format, classify, compare coverage, prove remediation, and self-validate detection, plus the .qrp.toml baseline/ignore mechanism surfaced through scan results. Minor gaps remain — there is no tool to query or page through a saved scan result directly (only the two comparison tools read saved files), and no operation for managing or validating the policy/baseline configuration itself.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues