Index / MCP servers / Quantum Expectations

Quantum Expectations MCP server

Quantum Expectations is a remote MCP server that gives an AI agent 12 tools, among them compare_hardware_scenarios, compute_expectation, compute_fault_tolerant_resources. It answers at https://www.quantum-expectations.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.

Status
Answering
Tools
12
Official
yes, served from quantum-expectations.com
Reliability
10 of 10 checks
Response time
271 ms
Transport
streamable HTTP
Last checked
18 October 2026

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

Description as the publisher wrote it.

The 12 tools Quantum Expectations offers

ToolWhat it does
compare_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. Defaults to every entry in list_current_quantum_computers when hardwareIds is omi
Inputs: numQubits, compDepth, useErrorCorrection, errorCorrectionCode, distanceSurfaceCode, hardwareIds
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. The response is self-describing (formulas, assumptions, caveats, glo
Inputs: qubitErrorRate, hardwareId, numQubits, compDepth, useErrorCorrection, errorCorrectionCode
compute_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-sc
Inputs: numLogicalQubits, tCount, qubitErrorRate, hardwareId, targetSuccessProbability, dataBlock
compute_quantum_volume_rateCompute 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). OVERSTA
Inputs: quantumVolume, t2QSeconds, tMeasurementSeconds
compute_required_error_rateInverse 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), th
Inputs: numQubits, compDepth, acceptableErrorRatePercent
fit_historic_seriesFit 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
Inputs: seriesType, hardwareType, targetValue
get_agent_briefReturn the plain-text site brief describing scope, assumptions, the honesty clause, and the API contract. Mirrors the /agent.txt document served by the website.
get_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. Each datapoint carries a source URL. Use this to extrapolate trends — "when might
Inputs: seriesType
list_current_quantum_computersReturn 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.
list_example_algorithmsReturn 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 `proven
list_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. Joins list_current_quantum_computers via `hardwareType`. Use for runtime estimates,
list_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). Use a c

Add Quantum Expectations to your AI client

Every block below points at https://www.quantum-expectations.com/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http quantum-expectations https://www.quantum-expectations.com/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "quantum-expectations": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.quantum-expectations.com/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "quantum-expectations": {
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "quantum-expectations": {
      "type": "http",
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "quantum-expectations": {
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "quantum-expectations": {
      "serverUrl": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "quantum-expectations": {
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Quantum Expectations
version: 0.0.1
schema: v1
mcpServers:
  - name: Quantum Expectations
    type: streamable-http
    url: https://www.quantum-expectations.com/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "quantum-expectations": {
      "httpUrl": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "quantum-expectations": {
      "type": "http",
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "quantum-expectations": {
      "url": "https://www.quantum-expectations.com/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fwww.quantum-expectations.com%2Fapi%2Fmcp&type=streamable_http&id=quantum-expectations&name=Quantum%20Expectations

Is Quantum Expectations up right now?

It answered our last check on 18 October 2026 in 271 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Quantum Expectations

Questions about Quantum Expectations

Is there an official Quantum Expectations MCP server?

Yes. It is published by quantum-expectations.com and served from www.quantum-expectations.com, the vendor's own domain: https://www.quantum-expectations.com/api/mcp.

How many tools does Quantum Expectations have?

12, as returned by the server's own tools/list on 31 August 2026: compare_hardware_scenarios, compute_expectation, compute_fault_tolerant_resources, compute_quantum_volume_rate, compute_required_error_rate, fit_historic_series, get_agent_brief, get_historic_series, and 4 more.

Is Quantum Expectations down?

It answered our last check on 18 October 2026 in 271 ms. Over 10 checks since 5 September 2026 it answered 10.

How do I add Quantum Expectations to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.quantum-expectations.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Quantum Expectations need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: com.quantum-expectations. Endpoint host: www.quantum-expectations.com. ARD identifier: urn:air:com.quantum-expectations:mcp:quantum-expectations. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.