quantum-aether
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_tlsA | Check whether a website negotiates post-quantum TLS key exchange (X25519MLKEM768). Returns an honest summary: if the site is already protected it says so; if not, it states the "harvest now, decrypt later" risk and the available fix (full report) and monitoring options. |
| scan_tls_rawA | Same scan as scan_tls but returns the structured result (grade, key_exchange_group, post_quantum_key_exchange, certificate_key, scan_url, full_report_price, scan_id). |
| buy_full_reportA | Buy the full post-quantum readiness report ($49) for a prior scan. Returns a PayPal approval link (approve_url) and a status_url. Set consent_immediate_delivery to true ONLY after the buyer expressly agreed the report is delivered immediately and that they lose the right of withdrawal (Austrian FAGG). After the buyer approves in PayPal, the report link appears at status_url. |
| start_monitoringA | Start a daily monitoring subscription (plan "starter" = $29/mo up to 10 domains, "business" = $99/mo up to 100 domains). Returns the PayPal plan id to complete the subscription. Set consent to true ONLY after the customer agreed to email processing and immediate start. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.