Quantum Expectations

com.quantum-expectations由 quantum-expectations.com 發布官方發布者v0.8.1更新於 Oct 29, 2026

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

已驗證Streamable HTTP可網頁執行資料與分析AI 與機器學習

概覽

AI 產生的概覽

唯讀的量子運算可行性計算服務:針對指定電路估算錯誤率、成功率、量子位元開銷與硬體趨勢。

可以做什麼
  • 計算電路在指定裝置或錯誤率下的有效錯誤率、成功機率及表面碼或 qLDPC 開銷
  • 由目標錯誤率反推所需的每閘邏輯錯誤率與糾錯方案
  • 依邏輯量子位元數與 T 閘數量估算完整的容錯表面碼與魔法態蒸餾資源
  • 以同一電路比較多個硬體平台,並計算量子體積速率
  • 讀取現行量子電腦、QUOPS 基準分數、閘時序、qLDPC 碼與範例演算法的資料表
  • 取得歷史保真度或量子位元數序列,並擬合對數線性趨勢以推測硬體何時達到目標
適用情境
適合需要快速且有出處的估算時:某個量子演算法能否在現有或近期硬體上執行、需要多少糾錯開銷,或硬體趨勢何時達到某個目標。也適用於研究寫作、平台間可行性比較與核對資源估算。
執行需求
遠端 streamable HTTP 端點;未宣告任何套件、帳號、API 金鑰或環境變數。需要能連線至提供方網站。
安裝前請注意
結果是模型輸出而非實測資料;伺服器本身要求使用時保留其附帶的注意事項與來源連結,並標明哪些數字是模型推算。部分資料為作者自述的估計值,而非可重現的電路。工具被描述為唯讀且具確定性,不會寫入或修改資料。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Quantum Expectations,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.quantum-expectations%2Fquantum-expectations/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "quantum-expectations": {
      "type": "http",
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}

工具

13

compute_expectation

Compute Quantum Expectation

Given a quantum circuit (2-qubit error rate p, qubit count n, depth d, optional connectivity class), compute the effective error rate, success probability, and optional surface-code or qLDPC overhead. Without error correction a 2d-lattice connectivity is charged as a routing multiplier on depth (result.routingOverheadFactor); hardwareId supplies the device's class automatically. 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.

輸入參數verbosecompDepth必填numQubits必填hardwareIdconnectivityqubitErrorRateuseErrorCorrectiondistanceSurfaceCodeerrorCorrectionCode

compute_required_error_rate

Compute Required Error Rate (Inverse)

Inverse of compute_expectation. Given a circuit (numQubits, compDepth) and an acceptable effective error rate, return the required per-gate logical error rate (requiredLogicalErrorRatePerGate: a number, or null only when the target is genuinely unreachable; never 0) 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. An option whose inverse lands above the code threshold is capped at min(MAX_P, threshold) and carries a `note` (any sub-threshold p satisfies it); `unreachableReason` is reserved for genuinely unreachable options. Answers "what hardware do I need to run this algorithm?".

輸入參數compDepth必填numQubits必填acceptableErrorRatePercent必填

compute_fault_tolerant_resources

Compute Fault-Tolerant Resources

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).

輸入參數tCount必填dataBlockhardwareIdqubitErrorRatecycleTimeSecondsnumLogicalQubits必填targetSuccessProbability

compare_hardware_scenarios

Compare Hardware Scenarios

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.

輸入參數compDepth必填numQubits必填hardwareIdsuseErrorCorrectiondistanceSurfaceCodeerrorCorrectionCode

list_current_quantum_computers

Current Quantum Computers

Return the representative-entry table of current SOTA quantum computers (id, hardware type, physical qubit count, 2-qubit error rate, connectivity class with a note on the coupling graph, source URL). Same data that powers the website's "Current Quantum Computers" table. For the model's capability prediction per entry in QUOPS units, read hardwareContext.currentQuantumComputers[].modelCapability from compute_expectation; for measured scores, list_quops_scores.

無需輸入參數。

list_quops_scores

Measured QUOPS Capability Scores

Return the measured QUOPS (quantum universal operation performance system, a cross-platform capability benchmark) scores (arXiv:2609.12146): per device, the largest random universal circuit size executed at polarization >= 1/sqrt(e) inside the cone w^2 <= s <= w^3, with width, QUOPS rate, architecture (physical, physical-postselected, logical) and source URL, plus the utility-scale targets in the same unit (RSA-2048 and FeMoco). These are measurements, the yardstick the site's own model is checked against: compare them with modelCapability.quopsEquivalent on the compute_expectation hardware context. Vendor and device names appear here because this table is agent-facing only.

無需輸入參數。

list_hardware_timings

Hardware Gate-Cycle Timings

Return per-platform gate-cycle timings (2Q gate time, readout time, in SI seconds) plus the testbed they were measured on (`representativeDevice`) and the native 2Q gate name, with source URLs. Joins list_current_quantum_computers via `hardwareType`, but the numbers are BEST-CASE DEMONSTRATIONS from small testbeds, not measurements on the joined devices, which run their gates and array readout orders of magnitude slower. Use for ratio analysis or as optimistic lower-bound inputs to runtime estimates and compute_quantum_volume_rate, and say so when you quote a runtime.

無需輸入參數。

compute_quantum_volume_rate

Compute Quantum Volume Rate

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).

輸入參數t2QSeconds必填quantumVolume必填tMeasurementSeconds必填

fit_historic_series

Fit Historic Series (log-linear)

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.

輸入參數seriesType必填targetValuehardwareType必填

list_example_algorithms

Example Quantum Algorithms

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. Each entry carries a `provenance` field: 'published-circuit' means the figure is reproducible from the source, 'attested-estimate' means the source withholds the circuit and the figure rests on the authors' attestation, with a `provenanceNote` giving the specifics. Carry that caveat whenever you quote an attested figure; do not present it as equivalently sourced.

無需輸入參數。

list_qldpc_codes

qLDPC Code Catalog (Quantum Low-Density Parity-Check)

Return the catalog of supported qLDPC (quantum low-density parity-check) error-correction codes (id, label, family, n, k, d, circuitLevelDistance, ancilla counts, roundsPerLogicalOp, threshold, fitCoefficients {c0, c1, c2}, logicalErrorExponent [alpha = d_circ/2], source URLs, provenance, caveats). The per-block, per-syndrome-cycle logical error rate is p^alpha * exp(c0 + c1*p + c2*p^2) for p <= threshold (the source paper's own fitting form; c1 = c2 = 0 means a plain power law). `provenance` names the table or section each constant was read from. `caveats` is an array of source-level qualifications on the entry's constants (loose distance bounds, values a source marks as assumed, numbers that differ between sources); empty when the sources carry none. Read it before quoting a code's logical error rate as firm. Use a code's `id` as the `errorCorrectionCode` input to `compute_expectation`.

無需輸入參數。

get_historic_series

Historic Hardware Series (Fidelity or Qubit Count)

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.

輸入參數seriesType必填

get_agent_brief

Agent Brief

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.

無需輸入參數。

版本歷史

3
  1. v0.8.1最新Oct 29, 2026
  2. v0.8.0Oct 23, 2026
  3. v0.6.0Sep 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。