Dechonet MCP

Post-Quantum TLS Readiness

pqc_readiness

Read-onlyIdempotent

Check if a domain's TLS endpoint supports the post-quantum hybrid X25519MLKEM768 key exchange, returning a readiness verdict, score, and report link.

Instructions

Check whether a website's public TLS endpoint is ready for post-quantum cryptography: does it complete a TLS 1.3 handshake that offers only the hybrid X25519MLKEM768 key exchange (ML-KEM), and does the organisation's own server provide it or a CDN edge in front of it. Also reports what the certificate chain is signed with (tracked, not scored: public CAs do not issue post-quantum certificates yet). Verdicts: ready (the origin server supports it), partial (a CDN edge provides it; the CDN-to-origin leg is invisible), not_ready (the hybrid-only handshake was refused), unknown (inconclusive — not the same as "no"). Scope: only the public endpoint on port 443. Internal systems, VPNs, code, and Korean PQC algorithms (no standard TLS codepoints yet) are not observable, so the result is an external indicator of migration progress, not a full PQC audit. Read-only; requires no API key; rate-limited. Returns the verdict, a 0-100 readiness score and grade, per-check statuses, and a shareable report link.

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain whose HTTPS endpoint to check (e.g., 'example.com'). Scheme and path are stripped.

Output Schema

Name	Required	Description
`grade`	No
`score`	No	0-100 post-quantum readiness; null when inconclusive
`checks`	No
`verdict`	Yes	'ready' \| 'partial' \| 'not_ready' \| 'unknown'
`receipts`	No	Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.
`reportUrl`	Yes	Human-facing interactive report on dechonet.com
`tlsVersion`	No
`keyExchange`	No	Hybrid group accepted (e.g. X25519MLKEM768), null if none
`terminatedBy`	No	'origin' or the CDN name whose edge answered

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.5.14Oct 15, 2026

addedOutput schema / properties / receipts

Added value: +{
+  "description": "Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "tool": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool",
+      "id",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Addedv1.3.1Oct 6, 2026

TDQS

A4.2/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly/idempotent/non-destructive/open-world, but the description adds substantial context beyond them: no API key required, rate-limited, the CDN-to-origin leg is invisible, certificate chain is tracked but not scored, and the 'unknown vs no' distinction. This is exactly the extra context an agent needs to interpret results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then scope, verdicts, and return shape in a logical order. It is dense and long, but nearly every clause carries decision-relevant information (verdict semantics, limitations). Minor trimming possible in the verdict enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-parameter tool with an output schema, the description covers everything needed: what is checked, what is not observable, verdict meanings, scoring, and limitations. Return-value redundancy with the output schema is minor and does not detract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'domain' parameter is fully documented in the schema (including scheme/path stripping). The description adds no syntax or format detail beyond that, so the baseline 3 is appropriate for a schema-does-the-work case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Check) and a tightly scoped resource: whether a website's public TLS endpoint completes a TLS 1.3 handshake offering only the hybrid X25519MLKEM768 key exchange. The post-quantum framing and port-443-only scope clearly distinguish it from the generic ssl_check sibling, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description defines scope boundaries (public endpoint on port 443; internal systems, VPNs and code not observable) and explains each verdict, which implies when the tool is appropriate. However, it never explicitly names ssl_check or any sibling as the alternative, nor states a when-not-to-use condition. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.