Skip to content

MCP servers › science.transaction.wai › quantum-jobs

MCP server · registry snapshot 2026-11-02 · last tested 2026-11-02

science.transaction.wai/quantum-jobs

WAI Quantum job service — the publisher's title

by wai.transaction.science · domain (the registry's namespace rule)Website ↗

A free quantum job service: OpenQASM 3 run, checked and signed, with no account or key. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-02version 0.2.1streamable HTTP30 tools

Summary

science.transaction.wai/quantum-jobs is a remote MCP server listed in the official MCP registry at version 0.2.1, under the namespace of the domain wai.transaction.science. On 2026-11-02 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 9 resources and 3 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
30
Last tested
2026-11-02

Tool list size

Claude's token counter refused this tool list as listed, unchanged (tool "run_quantum_circuit" (no. 1): input_schema: input_schema does not support oneOf, allOf, or anyOf at the top level)

Tried on Claude Opus 5.5 on 2026-11-02, from the tool list we read on 2026-11-02 (30 tools). How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-02 (wai.transaction.science), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.2.1).

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (run_quantum_set). That is our reading of the names; we did not call it. Source: our connection, 2026-11-02.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-02
Mode
read-only (no tool calls)
Latest version
0.2.1, published 2026-11-02 (registry, as of the 2026-11-02 snapshot)
First listed version
2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-29 to 2026-11-02; 2 in the 90 days before the 2026-11-02 snapshot.
Most recent 2 versions
  • 0.2.1 · 2026-11-02
  • 0.2.0 · 2026-10-29
(versions still listed in the registry only)
Registry data
snapshot 2026-11-02
Package and repository
checked 2026-11-02
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.2.0 (published 2026-10-29) → 0.2.1 (published 2026-11-02), between the registry lists of 2026-11-01 and 2026-11-02.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-01 and on 2026-11-02; release notes from the GitHub Releases API, checked 2026-11-02.

What it is

What does this server offer?

Observed inventory
30tools
9resources
3prompts

None of its 30 tools are described as changing anything. For 30 the reading was uncertain, so no mark is shown.

  • run_quantum_circuit

    “Run an OpenQASM program and return measurement counts, Pauli expectation values and/or amplitudes.”

    Publisher declares: read-only no · idempotent yes · open-world no

    17 inputs
    • qasmstring“The program, OpenQASM 3 (or 2), read as the whole language: registers, aliases and slices; the standard gates, `U` and `gphase`; user `gate` definitions and `d…”
    • shotsinteger“Measurement shots.”
    • observablesarray“Pauli strings to take expectation values of, e.g.”
    • amplitudesarray“Basis states to give amplitudes of: one character per qubit, qubit n-1 first, e.g.”
    • noiseobject“Optional noise, each a probability: depolarizing_1q, depolarizing_2q, amplitude_damping, dephasing (after each gate on its qubits), readout (each measured bit).”
    • methodstring“Leave as auto unless you need a particular method; pulse runs a pulse program (OpenPulse calibrations on physical qubits, see pulse_schedule) under the pulse o…”
    • seedinteger“Sampling seed (default 1); the same job and seed give the same counts.”
    • optionsobject“Advanced, per method: max_bond (mps), threshold and max_terms (pauli), fusion (statevector), trajectories.”
    • compileobject“Compile the program first (as compile_qasm does) and run the compiled circuit: with basis clifford_t it runs bit-exact, and the result's `compiled` states its …”
    • target“A device target: a built-in target's name (list_targets) or a target document (wai.quantum.target/1).”
    • fabricstring or array“Where the statevector method's state runs: auto (the default: on a member only where the committed measurements show it faster than the host's CPU for the job'…”
    • intentobject or array“What the program must do, checked by the engine with the run: the result's `verdict` states how far it checked (proof, evidence, executed, parsed, refused) and…”
    • repair“Repair the program first, on the lines its diagnostics flag alone (as repair_qasm does): true, or the choices {"max_iterations": N, "dyadic_bits": K, "sizes": …”
    • mitigatestring or object“Mitigate the job's expectation values (or, for readout, its counts) under its own noise: zne (the whole program folded U(U†U)^k and extrapolated), pea (the noi…”
    • pulseobject“A pulse run's options (method "pulse"): the sample period, the levels kept, the tolerance on the stated error, the steps a sample is divided into, each qubit's…”
    • sourceobject“The program in another format, in place of qasm: read to the job's qasm before the job is read (a module that does not read is refused with the reader's code, …”
    • paramsobject“A value for each of the program's parameters (input float theta;, input angle phi;), as {"theta": 0.3}: bound exactly before the program is read; a parameter l…”
  • run_quantum_set

    “Run several OpenQASM programs as one set (`programs`: each a program's text or a job), or one program over a grid of its inputs (`qasm` with `sweep`, as {"theta": [0.1, 0.2], "n": [2, 3]}: every comb…”

    Publisher declares: read-only no · idempotent yes · open-world no

    18 inputs
    • qasmstring“With sweep: the program, which declares the inputs the sweep gives values (`input uint n;`, `input float theta;`, `input angle phi;`).”
    • shotsinteger“Measurement shots.”
    • observablesarray“Pauli strings to take expectation values of, e.g.”
    • amplitudesarray“Basis states to give amplitudes of: one character per qubit, qubit n-1 first, e.g.”
    • noiseobject“Optional noise, each a probability: depolarizing_1q, depolarizing_2q, amplitude_damping, dephasing (after each gate on its qubits), readout (each measured bit).”
    • methodstring“Leave as auto unless you need a particular method; pulse runs a pulse program (OpenPulse calibrations on physical qubits, see pulse_schedule) under the pulse o…”
    • seedinteger“Sampling seed (default 1); the same job and seed give the same counts.”
    • optionsobject“Advanced, per method: max_bond (mps), threshold and max_terms (pauli), fusion (statevector), trajectories.”
    • compileobject“Compile the program first (as compile_qasm does) and run the compiled circuit: with basis clifford_t it runs bit-exact, and the result's `compiled` states its …”
    • target“A device target: a built-in target's name (list_targets) or a target document (wai.quantum.target/1).”
    • fabricstring or array“Where the statevector method's state runs: auto (the default: on a member only where the committed measurements show it faster than the host's CPU for the job'…”
    • intentobject or array“What the program must do, checked by the engine with the run: the result's `verdict` states how far it checked (proof, evidence, executed, parsed, refused) and…”
    • repair“Repair the program first, on the lines its diagnostics flag alone (as repair_qasm does): true, or the choices {"max_iterations": N, "dyadic_bits": K, "sizes": …”
    • mitigatestring or object“Mitigate the job's expectation values (or, for readout, its counts) under its own noise: zne (the whole program folded U(U†U)^k and extrapolated), pea (the noi…”
    • pulseobject“A pulse run's options (method "pulse"): the sample period, the levels kept, the tolerance on the stated error, the steps a sample is divided into, each qubit's…”
    • paramsobject“A value for each of the program's parameters (input float theta;, input angle phi;), as {"theta": 0.3}: bound exactly before the program is read; a parameter l…”
    • programsarray“The set's programs: each a program's text, or a job ({"qasm", …}) whose own fields win over the set's.”
    • sweepobject“Each input of qasm and its values: every combination runs, the names in sorted order, the first varying slowest; an integer input's values are whole numbers.”
  • dry_run_quantum_job

    “What the service would do with a job or a set, running nothing: the method and why, the memory, the estimated time and energy (each with its basis: this service's own timings and readings where it ha…”

    Publisher declares: read-only yes

    19 inputs
    • qasmstring“The program, OpenQASM 3 (or 2), read as the whole language: registers, aliases and slices; the standard gates, `U` and `gphase`; user `gate` definitions and `d…”
    • shotsinteger“Measurement shots.”
    • observablesarray“Pauli strings to take expectation values of, e.g.”
    • amplitudesarray“Basis states to give amplitudes of: one character per qubit, qubit n-1 first, e.g.”
    • noiseobject“Optional noise, each a probability: depolarizing_1q, depolarizing_2q, amplitude_damping, dephasing (after each gate on its qubits), readout (each measured bit).”
    • methodstring“Leave as auto unless you need a particular method; pulse runs a pulse program (OpenPulse calibrations on physical qubits, see pulse_schedule) under the pulse o…”
    • seedinteger“Sampling seed (default 1); the same job and seed give the same counts.”
    • optionsobject“Advanced, per method: max_bond (mps), threshold and max_terms (pauli), fusion (statevector), trajectories.”
    • compileobject“Compile the program first (as compile_qasm does) and run the compiled circuit: with basis clifford_t it runs bit-exact, and the result's `compiled` states its …”
    • target“A device target: a built-in target's name (list_targets) or a target document (wai.quantum.target/1).”
    • fabricstring or array“Where the statevector method's state runs: auto (the default: on a member only where the committed measurements show it faster than the host's CPU for the job'…”
    • intentobject or array“What the program must do, checked by the engine with the run: the result's `verdict` states how far it checked (proof, evidence, executed, parsed, refused) and…”
    • repair“Repair the program first, on the lines its diagnostics flag alone (as repair_qasm does): true, or the choices {"max_iterations": N, "dyadic_bits": K, "sizes": …”
    • mitigatestring or object“Mitigate the job's expectation values (or, for readout, its counts) under its own noise: zne (the whole program folded U(U†U)^k and extrapolated), pea (the noi…”
    • pulseobject“A pulse run's options (method "pulse"): the sample period, the levels kept, the tolerance on the stated error, the steps a sample is divided into, each qubit's…”
    • paramsobject“A value for each of the program's parameters (input float theta;, input angle phi;), as {"theta": 0.3}: bound exactly before the program is read; a parameter l…”
    • programsarray“The set's programs: each a program's text, or a job ({"qasm", …}) whose own fields win over the set's.”
    • sweepobject“Each input of qasm and its values: every combination runs, the names in sorted order, the first varying slowest; an integer input's values are whole numbers.”
    • sourceobject“The program in another format, in place of qasm: read to the job's qasm before the job is read (a module that does not read is refused with the reader's code, …”
  • get_quantum_job

    “A job's status, and its result when it is done.”

    Publisher declares: read-only yes

    1 input, 1 required
    • idstringrequired
  • verify_quantum_receipt

    “Whether a result's receipt (an Ed25519 signature by the service) seals exactly that request and that result.”

    Publisher declares: read-only yes

    2 inputs, 2 required
    • requestobjectrequired
    • resultobjectrequired
  • critique_qasm

    “A program's measures, computed by the engine: gates by kind, two-qubit gates, depth and two-qubit depth, T count, whether it is a Clifford circuit, and a fidelity under reference error rates (a model…”

    Publisher declares: read-only yes

    1 input, 1 required
    • qasmstringrequired
  • check_equivalent

    “Whether two programs are the same circuit up to a global phase, and how the engine knows: Clifford circuits by their tableaus at any size, others on every basis state to 8 qubits, then by checked rew…”

    Publisher declares: read-only yes

    2 inputs, 2 required
    • astringrequired
    • bstringrequired
  • convert_program

    “Carry a program between OpenQASM 3, QIR (LLVM text, read under its base and adaptive profiles, written as QIR 2.0) and jeff (its Cap'n Proto message, as base64).”

    Publisher declares: read-only yes

    6 inputs, 1 required
    • programstring“The program's text: OpenQASM or QIR.”
    • program_base64string“The program's bytes as base64: jeff.”
    • fromstring“Its format; found from its bytes when not given.”
    • tostringrequired“The format to write.”
    • profilestring“QIR's profile to write: by default base when the program's measurements all come at the end, else adaptive.”
    • checkboolean“false: write it without the check.”
  • improve_qasm

    “The program with its smells fixed in its own text (all of them, and each alone), each candidate with its measures and the equivalence check's verdict against the program.”

    Publisher declares: read-only yes

    1 input, 1 required
    • qasmstringrequired
  • classical_shortcuts

    “Every exact classical route to simulating a program, priced on it: the stabilizer tableau, the cut-rank sum, an exact matrix product state at a rigorous bond bound, the light cone of a one-qubit expe…”

    Publisher declares: read-only yes

    1 input, 1 required
    • qasmstringrequired
  • compile_qasm

    “Compile an OpenQASM program through named passes (lowering, checked rewrites, phase folding, one- and two-qubit resynthesis, and every rotation off the multiples of π/4 written as a Clifford+T word w…”

    Publisher declares: read-only yes

    4 inputs, 1 required
    • qasmstringrequired
    • epsilonnumber“The most the output may differ from the program in the operator norm, up to a global phase, shared by its rotations (default 1e-6).”
    • levelinteger“0: lower and approximate; 1 (default): also checked rewrites and phase folding; 2: also one- and two-qubit resynthesis.”
    • basisstring“clifford_t (default): every rotation off the multiples of π/4 written as a Clifford+T word within its share of epsilon; standard: nothing approximated.”
  • estimate_resources

    “What a fault-tolerant quantum computer would need to run a program.”

    Publisher declares: read-only yes

    9 inputs
    • countsobject“A logical-counts document instead of a program: numQubits, tCount, rotationCount, rotationDepth, cczCount, ccixCount, measurementCount.”
    • routineobject“A routine document instead of a program (version v1: routines with their ports, resources, children and connections).”
    • budgetnumber“The probability the run may fail, shared by logical errors, distillation and the rotations' synthesis (default 1e-3).”
    • qubitstring or object“The physical qubit: a reference qubit (ns-e4, the default: 50 ns gates, 1e-4 error; us-* are 100 µs gates, meas-* measurement-based), or one described.”
    • calibrationstring“The gate-based surface code's model: fitted to this engine's exact-matching decoder (default) or its union-find decoder, or the planar model's assumed one.”
    • max_slowdowninteger“The most the frontier slows the program by to need fewer factories (default 256).”
    • exportstring“Also give the program's counts as a logical-counts or a routine document, under export.”
    • namestring“The program's name in a routine document.”
    • qasmstring“The program, OpenQASM 3 or 2.”
Show 18 more tools
  • repair_qasm

    “Repair a program the reader refuses, changing only the lines its diagnostics flag.”

    Publisher declares: read-only yes

    7 inputs, 1 required
    • qasmstringrequired
    • proposedstring“Your repaired version: taken only if every changed line is a flagged one (or a line added beside one).”
    • max_iterationsinteger“The bound for an unbounded `while` on measured bits (Q310), as the person chose it.”
    • dyadic_bitsinteger“Round each angle the bit-exact method refuses (Q500) to the nearest multiple of 2π/2^K.”
    • sizesobject“A register's size, for one used before it is declared (Q102).”
    • diagnosticsarray“Codes you saw that reading the text does not raise (Q500).”
    • rulesboolean“false: only check the proposal.”
  • quantum_service_info

    “The methods with their qubit limits and what each answers, the accuracy classes, the per-client limits, the current load, how jobs are kept and metered, the receipt keys, and the conventions (bit ord…”

    Publisher declares: read-only yes

    Takes no inputs.

  • qasm_diagnostics

    “Every code the OpenQASM reader gives (each refusal and warning carries one, as `[Q103]` at the end of its message): its outcome (refused, lowered, carried, preserved or warned) and its meaning; and b…”

    Publisher declares: read-only yes

    1 input
    • codestring“One code, as Q103 or J011.”
  • list_componentson 45 other servers

    “Every component the service plans, runs, compiles and converts through: the simulation methods, the compiler passes, the noise channels and the program formats, each with its version, its origin and …”

    Publisher declares: read-only yes

    Takes no inputs.

  • “The device targets the service knows by name: synthetic, made up in the shapes of published formats, each with its qubits, pairs, the gates a program compiles to, the spread of its T1 and readout err…”

    Publisher declares: read-only yes

    Takes no inputs.

  • show_target

    “A device target's qubits, pairs, native gates with the spread of their errors and durations, its calibration snapshot and its hash; with view, each qubit's place for drawing its coupling map with its…”

    Publisher declares: read-only yes

    2 inputs, 1 required
    • targetrequired“A built-in target's name, or a target document.”
    • viewboolean
  • run_on_target

    “Run an OpenQASM program as it would run on a device target: compiled exactly to its gates, placed on its most reliable qubits and routes (the expected success given), checked against the circuit, and…”

    Publisher declares: read-only no · idempotent yes · open-world no

    16 inputs, 1 required
    • qasmstring“The program, OpenQASM 3 (or 2), read as the whole language: registers, aliases and slices; the standard gates, `U` and `gphase`; user `gate` definitions and `d…”
    • shotsinteger“Measurement shots.”
    • observablesarray“Pauli strings to take expectation values of, e.g.”
    • amplitudesarray“Basis states to give amplitudes of: one character per qubit, qubit n-1 first, e.g.”
    • noiseobject“Optional noise, each a probability: depolarizing_1q, depolarizing_2q, amplitude_damping, dephasing (after each gate on its qubits), readout (each measured bit).”
    • paramsobject“A value for each of the program's parameters (input float theta;, input angle phi;), as {"theta": 0.3}: bound exactly before the program is read; a parameter l…”
    • seedinteger“Sampling seed (default 1); the same job and seed give the same counts.”
    • optionsobject“Advanced, per method: max_bond (mps), threshold and max_terms (pauli), fusion (statevector), trajectories.”
    • compileobject“Compile the program first (as compile_qasm does) and run the compiled circuit: with basis clifford_t it runs bit-exact, and the result's `compiled` states its …”
    • targetrequired“A device target: a built-in target's name (list_targets) or a target document (wai.quantum.target/1).”
    • fabricstring or array“Where the statevector method's state runs: auto (the default: on a member only where the committed measurements show it faster than the host's CPU for the job'…”
    • intentobject or array“What the program must do, checked by the engine with the run: the result's `verdict` states how far it checked (proof, evidence, executed, parsed, refused) and…”
    • repair“Repair the program first, on the lines its diagnostics flag alone (as repair_qasm does): true, or the choices {"max_iterations": N, "dyadic_bits": K, "sizes": …”
    • mitigatestring or object“Mitigate the job's expectation values (or, for readout, its counts) under its own noise: zne (the whole program folded U(U†U)^k and extrapolated), pea (the noi…”
    • pulseobject“A pulse run's options (method "pulse"): the sample period, the levels kept, the tolerance on the stated error, the steps a sample is divided into, each qubit's…”
    • sourceobject“The program in another format, in place of qasm: read to the job's qasm before the job is read (a module that does not read is refused with the reader's code, …”
  • quantum_circuit_examples

    “Worked examples, each a complete job (OpenQASM program and arguments) with what it shows: a Bell pair, a rotation, QAOA, noise, a 1000-qubit GHZ state, 100-qubit dynamics, 200 qubits as a matrix prod…”

    Publisher declares: read-only yes

    Takes no inputs.

  • qec_code

    “Show an error-correcting code and certify its distance: its checks (Z-type: they see X errors) and stabilizers (X-type), k counted by rank, a layout to draw it, the decoders it admits, and its distan…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 1 required
    • coderequired“A code by name: surface:D (the rotated surface code, odd D from 3 to 15), toric:L (2 to 12), steane, color:D (the triangular 6.6.6 colour code, odd D from 3 to…”
    • certifyboolean“Certify the distance (default true).”
    • boundinteger“The heaviest support to search (default the code's nominal distance).”
    • certificateobject“A certificate (wai.quantum.distance/1) to check against the code.”
  • qec_decode

    “Decode with the engine's decoders.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    12 inputs
    • code“A code by name: surface:D (the rotated surface code, odd D from 3 to 15), toric:L (2 to 12), steane, color:D (the triangular 6.6.6 colour code, odd D from 3 to…”
    • decoderstring“The decoder (default: matching, or color for a colour code, relay_bp for a bivariate-bicycle code).”
    • syndromearray“The violated checks, by index.”
    • errorarray“The flipped qubits, by index.”
    • max_weightinteger“search: the heaviest error to try.”
    • memoryobject“The rotated surface-code memory experiment at circuit level.”
    • circuitstring“A noisy Clifford circuit in the circuit text.”
    • modelstring“A detector error model in its text.”
    • detectorsarray“The detectors that fired.”
    • shotsinteger“Sample this many shots of the circuit and decode each.”
    • seedinteger“The sampling seed (default 1).”
    • windowobject“window: rounds each window commits and the rounds after them it sees.”
  • qec_threshold

    “Measure logical failure rates over distances and physical error rates: family surface at circuit level (decoders matching, correlated or union_find; the code model P(d) = a·(p/p*)^((d+1)/2) per round…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    7 inputs
    • familystring“surface (circuit level, the default) or a code at code capacity.”
    • distancesarray“Odd distances (default 3, 5, 7).”
    • parray“Physical error rates.”
    • shotsinteger“Shots at each point (default 10000).”
    • decoderstring“surface: the decoder (default matching).”
    • roundsinteger“surface: rounds (default the distance).”
    • seedinteger
  • pulse_schedule

    “Read a pulse program (OpenPulse calibrations: ports, frames, waveforms, play, delay, shift_phase, set_phase, shift_frequency, set_frequency, captures and barriers) into its schedule on frames: every …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 1 required
    • qasmstringrequired“A pulse program: OpenQASM 3 with `defcalgrammar "openpulse";`, `cal` blocks declaring ports (d0 drives qubit 0, m0 is its measurement port, a0 its acquisition …”
    • pulseobject“A pulse run's options (method "pulse"): the sample period, the levels kept, the tolerance on the stated error, the steps a sample is divided into, each qubit's…”
  • pulse_check

    “Check a pulse job as a host returned it ({"request", "result"}, the result with its receipt): the receipt's signature, the program's digest against the request's text, and the request run again here …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 2 required
    • requestobjectrequired“The pulse job's request.”
    • resultobjectrequired“Its result, with its receipt.”
  • gradient_qasm

    “The expectation E = ⟨ψ|H|ψ⟩ of a Hamiltonian at a program's parameters, and its gradient by each parameter, exactly: by adjoint differentiation or the parameter-shift rule on the double-precision sta…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs, 3 required
    • qasmstringrequired“The program, OpenQASM 3: its parameters declared `input float theta;` (or `input angle theta;`) and used in gates' arguments, through arithmetic, the built-in …”
    • paramsobjectrequired“A value for each parameter, by name, as {"theta": 0.3}: bound exactly.”
    • hamiltonianarrayrequired“A Hamiltonian as Pauli terms summed: "Z0 Z1", "0.5 X2", "-1.5" (a constant), or {"pauli": "Y0 Y1", "coeff": -0.7}; qubit 0 is q[0].”
    • gradientenum“adjoint (the default: one pass forward, one back) or parameter_shift (each gate a parameter moves run at shifted angles: two terms, four for a controlled rotat…”
  • optimize_qasm

    “Minimise E = ⟨ψ|H|ψ⟩ over a program's parameters from the given params, deterministically: gradient descent with a fixed step, Adam, or SPSA from a seeded stream (at most 2000 steps).”

    Publisher declares: read-only yes · idempotent yes · open-world no

    8 inputs, 3 required
    • qasmstringrequired“The program, OpenQASM 3: its parameters declared `input float theta;` (or `input angle theta;`) and used in gates' arguments, through arithmetic, the built-in …”
    • paramsobjectrequired“A value for each parameter, by name, as {"theta": 0.3}: bound exactly.”
    • hamiltonianarrayrequired“A Hamiltonian as Pauli terms summed: "Z0 Z1", "0.5 X2", "-1.5" (a constant), or {"pauli": "Y0 Y1", "coeff": -0.7}; qubit 0 is q[0].”
    • optimizerenum or object“gradient_descent (θ ← θ − step·∇E), adam (default; beta1, beta2, epsilon), or spsa (two evaluations a step along a ±1 perturbation from the seeded stream; c, A…”
    • stepsinteger“Steps to take (default 100).”
    • step_sizenumber“The step (gradient descent 0.1, Adam 0.05) or SPSA's gain a (0.2).”
    • gradientenum“adjoint (the default: one pass forward, one back) or parameter_shift (each gate a parameter moves run at shifted angles: two terms, four for a controlled rotat…”
    • seedinteger“SPSA's seed (default 1).”
  • vqe_ground_state

    “The variational eigensolver: an ansatz (the program given as qasm with params, or ansatz {"layers": L}: layers of ry and rz on every qubit and a ring of cx, its parameters t0, t1, … from 0.1) optimis…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    9 inputs, 1 required
    • hamiltonianarrayrequired“A Hamiltonian as Pauli terms summed: "Z0 Z1", "0.5 X2", "-1.5" (a constant), or {"pauli": "Y0 Y1", "coeff": -0.7}; qubit 0 is q[0].”
    • qasmstring“The program, OpenQASM 3: its parameters declared `input float theta;` (or `input angle theta;`) and used in gates' arguments, through arithmetic, the built-in …”
    • paramsobject“A value for each parameter, by name, as {"theta": 0.3}: bound exactly.”
    • ansatzobject“The built-in ansatz in place of qasm (layers default 2, qubits the Hamiltonian's).”
    • optimizerenum or object“gradient_descent (θ ← θ − step·∇E), adam (default; beta1, beta2, epsilon), or spsa (two evaluations a step along a ±1 perturbation from the seeded stream; c, A…”
    • stepsinteger“Steps to take (default 100).”
    • step_sizenumber“The step (gradient descent 0.1, Adam 0.05) or SPSA's gain a (0.2).”
    • gradientenum“adjoint (the default: one pass forward, one back) or parameter_shift (each gate a parameter moves run at shifted angles: two terms, four for a controlled rotat…”
    • seedinteger“SPSA's seed (default 1).”
  • qaoa_maxcut

    “Max-Cut by the quantum approximate optimisation algorithm: the program (|+⟩ⁿ, then for each layer rzz(gamma·w) on every edge and rx(2·beta) on every qubit) and its cost Hamiltonian built from the gra…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    8 inputs, 1 required
    • graphobjectrequired
    • layersinteger“QAOA's p (default 1).”
    • paramsobject“gamma_0, beta_0, … to start from.”
    • optimizerenum or object“gradient_descent (θ ← θ − step·∇E), adam (default; beta1, beta2, epsilon), or spsa (two evaluations a step along a ±1 perturbation from the seeded stream; c, A…”
    • stepsinteger“Steps to take (default 100).”
    • step_sizenumber“The step (gradient descent 0.1, Adam 0.05) or SPSA's gain a (0.2).”
    • gradientenum“adjoint (the default: one pass forward, one back) or parameter_shift (each gate a parameter moves run at shifted angles: two terms, four for a controlled rotat…”
    • seedinteger“SPSA's seed (default 1).”
  • build_algorithm

    “An OpenQASM 3 program for a standard algorithm, with how to read its result, what it gives, and the equivalence ladder's verdict on it against a reference matrix or truth table built from the definit…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    11 inputs, 1 required
    • algorithmenumrequired
    • countinginteger“qpe, amplitude_estimation: counting qubits (default 4).”
    • phasenumber“qpe: the phase φ, in turns.”
    • amplitudenumber“amplitude_estimation: the good state's probability a.”
    • bitsinteger“adder: the integers' width.”
    • ainteger“adder: the first addend, prepared.”
    • binteger“adder: the second, which the sum replaces.”
    • carry_inboolean“adder: a carry in.”
    • phasesarray“qsvt: φ₀ … φ_d, radians.”
    • xnumber“qsvt: the signal.”
    • matrixarray“qsvt: [[a, b], [b, c]], real and symmetric, its eigenvalues within [-1, 1].”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-02.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
92% of 174
Tools with a description
100% of 30
Typical description length
557 characters

The tool set

Counted from the listing

Tools
30
Size of the list
about 262,964 tokens for an agent to load (characters ÷ 4)
Naming
30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-02 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://wai.transaction.science/quantum-jobs/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "quantum-jobs": {
      "url": "https://wai.transaction.science/quantum-jobs/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "quantum-jobs": {
      "type": "http",
      "url": "https://wai.transaction.science/quantum-jobs/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"quantum-jobs","type":"http","url":"https://wai.transaction.science/quantum-jobs/mcp"}'
Claude Code
claude mcp add --transport http quantum-jobs https://wai.transaction.science/quantum-jobs/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "quantum-jobs": {
      "type": "streamableHttp",
      "url": "https://wai.transaction.science/quantum-jobs/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "quantum-jobs": {
      "httpUrl": "https://wai.transaction.science/quantum-jobs/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.quantum-jobs]
url = "https://wai.transaction.science/quantum-jobs/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "quantum-jobs": {
      "url": "https://wai.transaction.science/quantum-jobs/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://wai.transaction.science/quantum-jobs/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint wai.transaction.science/quantum-jobs/mcpSession openedmatchesour test · 2026-11-02
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-02

Tool list changes

Our reads compared · no tool called

Hosted endpoint wai.transaction.science/quantum-jobs/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-10-30 to 2026-11-02; versions 0.2.0 to 0.2.1).

Last change seen between our reads on 2026-10-30 (version 0.2.0) and 2026-11-02 (version 0.2.1).

Added (9):

build_algorithmconvert_programgradient_qasmlist_componentsoptimize_qasmpulse_checkpulse_scheduleqaoa_maxcutvqe_ground_state

Changed (4):

dry_run_quantum_job: input schemarun_on_target: input schemarun_quantum_circuit: input schemarun_quantum_set: input schema

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-02 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-02. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about science.transaction.wai/quantum-jobs

Answered from the data above

Who publishes science.transaction.wai/quantum-jobs?

The registry ties the namespace science.transaction.wai to the domain wai.transaction.science; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does science.transaction.wai/quantum-jobs need an API key or sign-in?

It opened a session without any credential on 2026-11-02. The registry entry declares no required credential; no declaration is not a guarantee.

Has science.transaction.wai/quantum-jobs been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-02
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-02, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,838 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 30 tools, 9 resources, 3 prompts.
  4. 17,678 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-11-02; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-02
MCP capability
prompts, resources, tools
our test · 2026-11-02
Transport
streamable HTTP
registry · 2026-11-02
Required credentials
none declared
registry · 2026-11-02 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-02
Lifecycle status
registry · 2026-11-02
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-02

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “science.transaction.wai/quantum-jobs: MCP server record.” Data checked 2026-11-02. https://protocolprobe.com/mcp/servers/science.transaction.wai/quantum-jobs

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/science.transaction.wai/quantum-jobs)](https://protocolprobe.com/mcp/servers/science.transaction.wai/quantum-jobs)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology