Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Quantum Expectations

REMOTE · WWW.QUANTUM-EXPECTATIONS.COM · SCANNED AUG 3

Quantum error-correction feasibility: success probability, qubit overhead, records, trends.

+7 this week 77 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2231 tokens (~117/item across 19 items; 12 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · www.quantum-expectations.com

# add to Claude Code
claude mcp add --transport http com-quantum-expectations-quantum-expectations https://www.quantum-expectations.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.com-quantum-expectations-quantum-expectations]
url = "https://www.quantum-expectations.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-quantum-expectations-quantum-expectations": {
      "type": "remote",
      "url": "https://www.quantum-expectations.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-quantum-expectations-quantum-expectations --url https://www.quantum-expectations.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-quantum-expectations-quantum-expectations:
    url: "https://www.quantum-expectations.com/api/mcp"
// mcp.json
{
  "mcpServers": {
    "com-quantum-expectations-quantum-expectations": {
      "type": "http",
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • Stability: unverified → 0.03 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://www.quantum-expectations.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.quantum-expectations.com CN=YR1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 RSA 2048 SHA256-RSA 66b7420e87246a7fbd3e823a823171711c2
SANs: *.quantum-expectations.com, quantum-expectations.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of www.quantum-expectations.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
quantum-expectations.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://vercel.live https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://vitals.vercel-insights.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.quantum-expectations.com/api/mcp Verified 200
http (plaintext) http://www.quantum-expectations.com/api/mcp HTTPS enforced 308 https://www.quantum-expectations.com/api/mcp
MCP tools — 12 exposed · ~2,069 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
compare_hardware_scenarios ~178

Run the same circuit against multiple current SOTA hardware entries in one call so an agent can rank platforms without N sequential compute_expectation calls. Defaults to every entry in list_current_quantum_computers when hardwareIds is omitted.

NameTypeReqDescription
compDepthintegeryes
distanceSurfaceCodeintegerRequired when useErrorCorrection=true and errorCorrectionCode="surface" (odd integer).
errorCorrectionCodestringEither "surface" (default when useErrorCorrection=true) or a qLDPC code id. "surface-code" is accepted as an alias for "surface".
hardwareIdsarraySubset of QUANTUM_COMPUTERS ids to compare. Omit to compare every entry.
numQubitsintegeryes
useErrorCorrectionboolean

No output schema declared.

No examples provided.

compute_expectation ~345

Given 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. The response is self-describing (formulas, assumptions, caveats, glossary, SOTA hardware, historic series with source URLs) so an agent can reason from one call. For the inverse ("what hardware do I need?") use compute_required_error_rate; to rank multiple platforms in one call use compare_hardware_scenarios.

NameTypeReqDescription
compDepthintegeryes
distanceSurfaceCodeinteger
errorCorrectionCodestringEither "surface" (default when useErrorCorrection=true) or a qLDPC code id from list_qldpc_codes. "surface-code" is accepted as an alias for "surface".
hardwareIdstringAlias for qubitErrorRate: resolves to the 2-qubit error rate of the given SOTA hardware entry from list_current_quantum_computers. Supply exactly one of qubitErrorRate or hardwareId.
numQubitsintegeryes
qubitErrorRatenumberPer-gate 2-qubit error rate p, in (0, 0.1]. Supply exactly one of qubitErrorRate or hardwareId.
useErrorCorrectionboolean
verbosebooleanWhen false, omits hardwareContext, formulas, assumptions, caveats, glossary, examples, and exampleProblems from the response — leaving only modelVersion, scenario, and result. Use for parameter sweep…

No output schema declared.

No examples provided.

compute_fault_tolerant_resources ~448

Given 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. Results are reported under TWO published logical-error fits (conservative + optimistic) because they disagree by 13-268x (d=7 to d=25) - always state both. Returns an explicit `infeasible` block when no cataloged factory or code distance can satisfy the error budget. Computes numbers only: comparing against classical alternatives and concluding "should this run on a quantum computer" stays with you, the calling agent (state the caveats when you do).

NameTypeReqDescription
cycleTimeSecondsnumberSurface-code cycle time in seconds. Default 1 µs (Litinski convention; Google 2024 measured 1.1 µs on superconducting hardware). Trapped-ion/neutral-atom cycles are orders of magnitude slower.
dataBlockstringData-block layout (Litinski §2): compact = fewest qubits, fast = shortest time per T gate.
hardwareIdstringAlias for qubitErrorRate: resolves to the error rate of a SOTA hardware entry.
numLogicalQubitsintegeryesNumber of logical data qubits the algorithm needs.
qubitErrorRatenumberPhysical 2-qubit error rate p in (0, 0.1]. Supply exactly one of qubitErrorRate or hardwareId.
tCountintegeryesTotal number of T gates (magic states consumed). Convention: state Toffoli-counted algorithms in T gates before calling (1 Toffoli ≈ 4–7 T depending on decomposition).
targetSuccessProbabilitynumberTarget end-to-end success probability. The failure budget (1 − target) is split evenly between T-state error and logical (memory/surgery) error, matching Litinski §4.

No output schema declared.

No examples provided.

compute_quantum_volume_rate ~233

Compute the Quantum Volume Rate (QV/second): QVR = V_Q / (log2(V_Q) * t_2Q + t_meas). First-order estimate of how fast a device prepares one QV-sized square circuit (one native 2Q gate per QV layer + one end-of-circuit measurement). OVERSTATES achievable rate: real compilation inflates the 2Q-gate count per layer; omits reset/SPAM, mid-circuit measurement, and classical-control latency. For a production throughput metric, see IBM's CLOPS (arXiv:2110.14108).

NameTypeReqDescription
quantumVolumeintegeryesQuantum volume V_Q (integer ≥ 2, e.g. 64 for a depth-log2=6 square circuit).
t2QSecondsnumberyesNative 2-qubit gate time in seconds (e.g. 60e-9 for a 60 ns CZ).
tMeasurementSecondsnumberyesEnd-of-circuit measurement/readout time in seconds (e.g. 5e-3 for 5 ms).

No output schema declared.

No examples provided.

compute_required_error_rate ~186

Inverse of compute_expectation. Given a circuit (numQubits, compDepth) and an acceptable effective error rate, return the required per-gate logical error rate and, for every EC option (no-EC, surface-code per distance, every qLDPC code), the required physical error rate plus the subset of current SOTA hardware that already qualifies. Answers "what hardware do I need to run this algorithm?".

NameTypeReqDescription
acceptableErrorRatePercentnumberyesUpper bound on the effective error rate, as a percent. Default website convention is 33 (i.e. ≤33% effective error is "acceptable").
compDepthintegeryesCircuit depth d (sequential 2-qubit gate layers). Accepts values up to 1e13.
numQubitsintegeryesNumber of logical qubits n in the circuit.

No output schema declared.

No examples provided.

fit_historic_series ~234

Fit a log-linear trend (ln(value) = slope * year + intercept) to one historic series — fidelity or qubit-count — for one hardware type. Atomic primitive: compose with list_current_quantum_computers, compute_required_error_rate, or your own modelling to answer "when might hardware reach X?". residualStdDev is the BIASED (maximum-likelihood) RMS — divides by n, not (n - 2); on small series (n ≈ 3–5) inflate by √(n / (n - 2)) before building confidence intervals.

NameTypeReqDescription
hardwareTypestringyesHardware platform as used by get_historic_series.
seriesTypestringyesWhich historic series to fit: "fidelity" (2-qubit gate error rate) or "qubit-count" (physical qubits).
targetValuenumberOptional. When supplied, the response includes yearAtTargetValue — the extrapolated year the fit crosses this value (error rate for fidelity series, qubit count for qubit-count series). Null if slope…

No output schema declared.

No examples provided.

get_agent_brief ~41

Return the plain-text site brief describing scope, assumptions, the honesty clause, and the API contract. Mirrors the /agent.txt document served by the website.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_historic_series ~118

Return the full historic time series — either two-qubit gate error rates ("fidelity") or physical qubit counts ("qubit-count") — broken down by hardware type. Each datapoint carries a source URL. Use this to extrapolate trends — "when might hardware reach X?" — or pair with fit_historic_series for a log-linear fit on one hardware type.

NameTypeReqDescription
seriesTypestringyes"fidelity" → 2-qubit gate error rates; "qubit-count" → physical qubit counts.

No output schema declared.

No examples provided.

list_current_quantum_computers ~56

Return the representative-entry table of current SOTA quantum computers (id, hardware type, physical qubit count, 2-qubit error rate). Same data that powers the website's "Current Quantum Computers" table.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_example_algorithms ~49

Return the curated list of example quantum algorithms with published resource estimates (qubit count, depth/gate count, source paper URL). Useful for comparing what algorithms need vs. what hardware can deliver.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_hardware_timings ~89

Return 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. Joins list_current_quantum_computers via `hardwareType`. Use for runtime estimates, ratio analysis, or as inputs to compute_quantum_volume_rate. Values are representative current-generation numbers, not records.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_qldpc_codes ~92

Return 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). Use a code's `id` as the `errorCorrectionCode` input to `compute_expectation`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.