Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Measure post-quantum TLS evidence and buy full reports through x402 USDC on Base
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://ather-quatum.cloud/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"quantum-aether": {
"command": "uvx",
"args": [
"quantum-aether-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http quantum-aether https://ather-quatum.cloud/mcpclaude mcp add quantum-aether -- uvx quantum-aether-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"quantum-aether": {
"url": "https://ather-quatum.cloud/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"quantum-aether": {
"command": "uvx",
"args": [
"quantum-aether-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"quantum-aether": {
"type": "http",
"url": "https://ather-quatum.cloud/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"quantum-aether": {
"type": "stdio",
"command": "uvx",
"args": [
"quantum-aether-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://ather-quatum.cloud/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.
scan_tlsRun a new, rate-limited TLS scan of a public hostname on port 443. Returns observation_status, measured time, negotiated group and certificate summary. Starts an external connection and stores a publicly accessible result. Does not judge application safety.
get_tls_evidenceRead existing TLS evidence with source, checked_at, expires_at and fresh/stale/undetermined/not_scanned state. Never starts a new network scan. A missing record is not proof that a domain is unsafe.
get_methodologyGet the documented measurement scope, observation states, certificate-grade rules and privacy limitations before interpreting a TLS result.
get_example_resultReturn an explicitly labeled archived example, not live telemetry. No payment and no network scan.
get_service_infoGet live endpoint locations, configured scan quotas, documentation and current full-report pricing. Automatic x402 payments and signed receipts are not available.
create_full_report_orderCreate a one-time full-report order for an existing scan. This does not transfer funds. Only set consent_immediate_delivery true after the payer has expressly agreed to immediate delivery and applicable withdrawal terms. The payer must send USDT on Polygon and then submit its tra
verify_full_report_paymentSubmit the payer-provided Polygon transaction hash. The server checks the confirmed USDT transfer, exact order amount and recipient on chain. Returns the private report URL only after confirmation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account moncef00327-cloud, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 677 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.3.0) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Thth
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Call before you post: ships a draft to Threads/Bluesky/Mastodon only after a person approved it.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Let any MCP-compatible AI assistant (Claude Desktop, and others) check a website's post-quantum TLS readiness — and, with the user's consent, buy the full report or start monitoring — by calling Quantum Aether as a native tool.
It wraps the public Quantum Aether API. No API key. No secrets.
| Tool | What it does |
|---|---|
scan_tls(domain) | Scans a host and returns an honest summary. If the site already uses post-quantum key exchange it says so; otherwise it states the "harvest now, decrypt later" risk and the fix. |
scan_tls_raw(domain) | The structured result (grade, key exchange group, post-quantum yes/no, certificate, scan_id, price). |
buy_full_report(scan_id, consent_immediate_delivery) | Returns a PayPal approval link for the $49 report. Consent required (Austrian FAGG). |
start_monitoring(email, plan, consent) | Starts a daily monitoring subscription ($29 or $99 / month). |
pip install quantum-aether-mcp
pip install -e .
Add to claude_desktop_config.json:
{
"mcpServers": { "quantum-aether": { "command": "python", "args": ["-m", "quantum_aether_mcp"] } } }
Then ask your assistant: *"Is example.com ready for post-quantum TLS?"* — it will call scan_tls.
The tool reports the real scan result. A site that already negotiates X25519MLKEM768 is told it is protected, with no upsell. A problem is surfaced only when it genuinely exists. This is what makes AI assistants trust and reuse the tool.
Scanner, methodology and open dataset: https://ather-quatum.cloud