qrp-mcp
Related Servers
Alternatives to qrp-mcp
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.1611Apache 2.0
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server that provides security scanning, project mapping, and vulnerability fix generation to AI coding assistants.155 npm2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for ai-scanner that enables AI agents to scan codebases for LLM usage, AI frameworks, and exposed secrets.38 npm1MIT
- FlicenseNot gradedqualityDmaintenanceLocal 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.-
- AlicenseCqualityBmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseAqualityBmaintenanceA local MCP server that scans repository dependencies for known vulnerabilities (CVEs) using OSV.dev, enriches findings with NVD and CISA KEV data, and supports triage, remediation, and accepted risk management directly from an AI coding assistant.619 npm1MIT
TDQS
Scored across 4 tools
Each tool has a distinct job: list_algorithms is a read-only reference, scan_repo returns a human-readable inventory, export_cbom produces a portable document, and compare_coverage assesses comparability of coverage numbers. The only near-overlap is scan_repo vs export_cbom, but their output formats and use cases are explicitly separated.
All tool names follow the same snake_case verb_noun pattern: list_algorithms, scan_repo, export_cbom, compare_coverage. The verbs are clear, distinct, and consistently positioned.
Four tools is well-scoped for the narrow domain of cryptographic repository scanning and coverage reporting. Each tool earns its place and none feels redundant.
The core workflow is covered: understanding detection coverage, scanning a directory, producing a CBOM, and judging whether coverage numbers are comparable. Minor gaps exist, such as no direct way to diff two scans' findings or scan a single file, but these do not block the server's stated purpose.