WAI Quantum

science.transaction.waiPublished by wai.transaction.sciencev0.2.4Updated Nov 5, 2026

OpenQASM 3 programs run, checked against their intent and signed on this machine.

The publisher's own server: WAI Quantum job service

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that runs OpenQASM 3 quantum programs, checks them against their stated intent, and signs the results on the user's machine.

What you can do
  • Run OpenQASM 3 quantum programs locally.
  • Check a program's execution against its declared intent.
  • Sign the run results on the local machine.
  • No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it
Worth adding when an assistant needs to execute OpenQASM 3 circuits and produce locally signed, intent-checked run records, for example in quantum computing experiments or reproducible research workflows.
Requirements
Runs as a local process over stdio, installed from the Cargo package wai-quantum-cli, so a Rust/Cargo toolchain is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It executes programs and signs results on your machine, so the signing key and any generated artifacts stay local and should be protected. The manifest lists no tools, so review what it actually runs and signs before relying on it. No credentials or third-party data sharing are declared.

Installation

In SourceWeft

  1. Open WAI Quantum in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

3
  1. v0.2.4LatestNov 5, 2026
  2. v0.2.3Nov 3, 2026
  3. v0.2.2Oct 30, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Transaction integrations