Post-Quantum TLS Checker MCP tool

Check whether a website's server uses post-quantum key exchange in TLS 1.3, such as the hybrid X25519MLKEM768 that browsers offer, and which post-quantum key exchange groups it accepts.


The MCP server is in testing mode and is available only to selected users.

Tool

Tool name
post_quantum_tls_checker

Checks whether a host's HTTPS server (port 443) supports post-quantum key exchange in TLS 1.3. It makes one handshake offering the key exchange groups Chrome offers (X25519MLKEM768, X25519, P-256, P-384) and one TLS 1.3 handshake per post-quantum group offering only that group: X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 (hybrids of a classical curve with ML-KEM), MLKEM768 and MLKEM1024 (ML-KEM alone). host is a public hostname or IP address (a URL is reduced to its host); hosts that resolve to private or reserved addresses are refused. Returns host, port (always 443), protocol (TLS version of the browser-like handshake, such as TLSv1.3; null if unknown), keyExchange (the group the server picked from the browser's groups, such as X25519MLKEM768 or X25519; null if unknown), postQuantum (whether that group is post-quantum, i.e. browsers get post-quantum key exchange from this server), groups (one entry per post-quantum group with group and supported: true when the server completed the handshake, false when it refused it with a TLS alert, null when the handshake failed otherwise, such as a timeout or dropped connection, so support is unknown) and certificateKey (the public key of the server's certificate: type as Node names it, such as rsa, ec, ed25519 or ml-dsa-65, bits for RSA, curve for EC; null if unreadable). Post-quantum key exchange protects recorded traffic against future quantum computers; the certificate, which authenticates the server, is a separate matter and is still RSA or ECDSA on public websites. Fails when the host isn't a public address, can't be resolved or reached, or no TLS handshake succeeds.


Parameters
  • hoststring · Required
    Public hostname or IP address of an HTTPS server (port 443); a URL is reduced to its host
    Up to 2048 characters

Input schema
342 characters

Connection

Every request needs an API token, which you can create in your account and send as a Bearer token in the Authorization header.

193 characters

On the website

Post-Quantum TLS Checker also works in your browser, without an AI assistant.