quantum-aether
Related Servers
Alternatives to quantum-aether
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceFree SSL/TLS scanning and Let's Encrypt certificate issuance (private key stays local), plus certificate-expiry monitoring via one MCP server. Public scan and cert tools need no account.3MIT
- 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
- AlicenseAqualityAmaintenanceAn MCP server that scans local codebases for quantum-vulnerable cryptography (secp256k1, Ed25519, RSA, etc.) and CI signing commands, classifying each finding as quantum-broken, post-quantum, or neither. It runs entirely locally with no network calls, providing a deterministic inventory for AI agents.52,009 PyPI3Apache 2.0
- AlicenseNot gradedqualityDmaintenancePassive security scanner that audits a running MCP server against the OWASP MCP Top 10 and grades it A-F. Read-only static analysis of the advertised tools, prompts and resources with console/JSON/SARIF output, and it also runs as an MCP server itself.54 npmMIT
- AlicenseAqualityBmaintenanceSecurity scanner for MCP servers: detects tool poisoning, hidden instructions, tool shadowing, excessive permissions, leaked secrets and weak transports before you install a server.4538 npmApache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables comprehensive TLS security audits for any domain, including certificate validity, expiry warnings, cipher suite weaknesses, deprecated protocols, and HSTS checks. Supports single and bulk domain inspection via MCP tools or a CLI for CI/CD integration.787 npmMIT
TDQS
Scored across 4 tools
scan_tls and scan_tls_raw perform the identical scan and differ only in output shape, which is the one plausible source of misselection; descriptions do explicitly flag the difference and that scan_tls_raw yields the scan_id needed downstream. buy_full_report and start_monitoring target clearly distinct monetization flows.
All four tools use snake_case with a verb-first pattern (scan_tls, buy_full_report, start_monitoring), which is predictable. The only deviation is the '_raw' variant suffix on scan_tls_raw, a minor but readable exception.
Four tools is tight but defensible for a focused 'scan a domain for post-quantum TLS, then upsell report/monitoring' server. The set is slightly thin given the paid plans cover 10-100 domains and subscriptions have no management surface.
The scan-to-purchase funnel is covered, but lifecycle operations are missing: no tool to list/retrieve prior scans or reports, no monitoring status/list/cancel, and no batch scan despite plans advertising up to 100 domains. Agents must fall back on raw status_url polling outside the tool surface.