AI & Machine Learning
quantum-expectations.com
Provides tools to compute quantum error rates, fault-tolerant resources, and compare quantum hardware scenarios.
ENDPOINT 1
https://www.quantum-expectations.com/api/mcp
MCP server metadata
- Name
- quantum-expectations
- Version
- 3.0.0
Known tools 12
compute_expectationGiven a quantum circuit (2-qubit error rate p, qubit count n, depth d), compute the effective error rate, success probability, and optional surface-code or qLDPC overhead.
Inferred read-onlycompute_fault_tolerant_resourcesGiven an algorithm stated as (numLogicalQubits, tCount) and a physical error rate (or hardwareId), derive the full surface-code + magic-state-distillation footprint from the general laws of the Litinski lattice-surgery cost model (no per-scenario constants): distillation factory choice, tile layout, required code distance, total physical qubits, and wall-clock time.
Inferred read-onlycompare_hardware_scenariosRun the same circuit against multiple current SOTA hardware entries in one call so an agent can rank platforms without N sequential compute_expectation calls.
Inferred read-onlylist_current_quantum_computersReturn the representative-entry table of current SOTA quantum computers (id, hardware type, physical qubit count, 2-qubit error rate).
Inferred read-onlylist_hardware_timingsReturn per-platform gate-cycle timings (2Q gate time, readout time, in SI seconds) plus the representative device and native 2Q gate name, with source URLs.
Inferred read-onlycompute_quantum_volume_rateCompute the Quantum Volume Rate (QV/second): QVR = V_Q / (log2(V_Q) * t_2Q + t_meas).
Inferred read-onlyfit_historic_seriesFit a log-linear trend (ln(value) = slope * year + intercept) to one historic series — fidelity or qubit-count — for one hardware type.
Inferred read-onlylist_example_algorithmsReturn the curated list of example quantum algorithms with published resource estimates (qubit count, depth/gate count, source paper URL).
Inferred read-onlylist_qldpc_codesReturn the catalog of supported qLDPC codes (id, label, family, n, k, d, circuitLevelDistance, ancilla counts, roundsPerLogicalOp, threshold, prefactor [per block per syndrome cycle], logicalErrorExponent [= d_circ/2], source URLs).
Inferred read-onlyget_historic_seriesReturn the full historic time series — either two-qubit gate error rates ("fidelity") or physical qubit counts ("qubit-count") — broken down by hardware type.
Inferred read-onlyget_agent_briefReturn the plain-text site brief describing scope, assumptions, the honesty clause, and the API contract.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.quantum-expectations]
url = "https://www.quantum-expectations.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"quantum-expectations": {
"type": "http",
"url": "https://www.quantum-expectations.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: quantum-expectations
Remote MCP URL: https://www.quantum-expectations.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"quantum-expectations": {
"url": "https://www.quantum-expectations.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"quantum-expectations": {
"type": "http",
"url": "https://www.quantum-expectations.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "quantum-expectations",
"transport": "streamable-http",
"url": "https://www.quantum-expectations.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for quantum-expectations.com was fetched 2026-08-24T04:25:30.015Z and is being refreshed.
quantum-expectations.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.