
QECTOR Quantum Error Correction
io.github.GuillaumeLessardPublished by GitHub account GuillaumeLessardv1.0.6Updated Oct 24, 2026
Local quantum error correction tools; decoder output verified against H c = s (mod 2).
Overview
Local quantum error correction server for Claude that decodes syndromes and verifies each correction against the parity relation H c = s (mod 2).
- What you can do
- Decode quantum error correction syndromes with the bundled qector-decoder-v3 engine, with each returned correction checked against the parity relation before it leaves the process. Run stable library tools by default, with research and administrative tool sets available only when explicitly enabled. Use bundled commands, agents and skills for setup, theorem facts, reproduction, threshold sweeps, detector error models, code inspection, benchmarking and validation. Produce deterministic, reproducible artifacts and provenance records.
- When to use it
- Worth adding when you work on quantum error correction in Claude Code or Claude Desktop and want local, offline decoding with machine-checkable verification of each correction. It suits research, teaching and reproducibility work on QEC codes and decoders rather than general-purpose tasks.
- Requirements
- Runs as a local process on the user's machine via stdio, installed as a Claude Desktop .mcpb bundle or a Claude Code marketplace plugin. Needs Python 3.9 through 3.13 (3.11 or 3.12 recommended; 3.14+ rejected), pip, and Claude Code 2.0+ or Claude Desktop 0.10.0+. The QECTOR_PYTHON variable can pin an interpreter path. No network access by default.
Installation
In SourceWeft
- Open QECTOR Quantum Error Correction in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
QECTOR Claude Plugin
Verified quantum error correction for Claude. Local, deterministic, and mathematically guaranteed on every machine you work on.
QECTOR integrates the published qector-decoder-v3==1.0.0 engine with
Claude Code and Claude Desktop, turning both into a production grade QEC
engineering environment. Every correction returned by an MCP server is
verified against the parity relation H c = s (mod 2) before it leaves
the process, every claim carries a machine checkable provenance class,
and the default configuration performs no network request of any kind.
4 MCP servers · 8 stable / 29 research / 3 admin tools · 11 commands · 5 agents · 28 skills · zero egress by default
Latest release — v1.0.6 · Claude.ai marketplace compliance (launchers to
scripts/, canonical manifests), environment-agnostic/qec-setup, deterministic artifacts. See the release announcement.
Why v1.0.6
Version 1.0.6 completes the portability and compliance story that 1.0.5
started, then layers on marketplace correctness and universal setup. Two
problems drove it: modern operating systems no longer hand you Python on a
predictable command name (macOS, Debian, Ubuntu, and Fedora ship python3
without bare python, while Windows adds its own resolver quirks), and the
claude.ai marketplace approval pipeline rejects plugins that ship
executables in bin/. This release retires both failure classes, permanently.
1. A universal, compliant launcher ships inside every artifact.
- The plugin archive, the source distribution, and the Desktop bundle all
carry
scripts/qector-python(POSIX sh) andscripts/qector-python.cmd(Windows). They live inscripts/, notbin/: claude.ai-hosted plugins may not shipbin/executables because they land on PATH without ever appearing on the admin approval surface. A validator now hard-fails any build that reintroducesbin/. - Resolution is governed, not guessed. An administrator pinned interpreter
wins first, then
python3, thenpython, with the Windowspylauncher tried ahead of them all. - The supported window is enforced, not documented. Only Python 3.9 through 3.13 executes, matching the published native wheel matrix; an out of range machine receives precise remediation guidance instead of a deep import crash.
- Pinning is first class on both surfaces. Set
QECTOR_PYTHONto an absolute interpreter path and every launcher honors it above discovery.
2. The marketplace surface is canonical.
Both plugin.json and marketplace.json use only documented fields and a
relative same-repo plugin source — the form every official marketplace uses
and the only form every sync path can resolve. The Desktop MCPB carries a
win32 platform override so Windows always selects the .cmd launcher.
3. Setup works in every environment.
/qec-setup detects sandboxed and remote environments (claude.ai code
execution, Cowork, containers without a project checkout) and falls back to
native diagnostics instead of dead ending on a missing local script — and it
reports honestly which path it used.
Platform support
Local stdio cannot reach web or mobile by architecture; the hosted connector is the engineered path to those surfaces and lands in 1.1.x.
Installation
Prerequisites
Python with spaces in path (e.g.
Anthropic Skills and agents) is now handled — the Desktop extension inv1.0.6usespythondirectly (no${__dirname}launcher) and the Code plugin usesscripts/qector-python. If you still seeServer disconnected, setQECTOR_PYTHON(see Troubleshooting).
Option A — Claude Code (marketplace, 30 s)
Option B — Claude Desktop (single click)
Via UI (recommended):
- Download
qector-claude-desktop-1.0.6.mcpbfrom the release page. - Claude Desktop → Settings → Extensions → Advanced settings → Install Extension → select the
.mcpb→ Enable. - Fully quit Claude Desktop (system tray → Quit) and reopen — the extension needs a full restart to load the 8-tool safe profile.
Via script (same result, auditable):
Verify Desktop:
C:\Users\<you>\AppData\Roaming\Claude\claude_desktop_config.jsoncontainsqector-library(if you used the script) andextensions-installations.jsoncontainsant.dir.gh.guillaumelessard.qector.C:\Users\<you>\AppData\Local\Claude\logs\mcp.logshowsQECTOR Server started and connected → initialize → tools/list → result(noServer disconnected).
Option C — From source (auditable, offline)
Troubleshooting
The QECTOR surface
Alongside the servers: 11 slash commands for setup, facts, theorems, reproduction, threshold sweeps, Wilson intervals, detector error models, code inspection, benchmarking, sinter templates, and validation; 5 specialized agents (researcher, developer, validator, sysadmin, hardware engineer); and 28 skills spanning math foundations, architecture, BP OSD, two stage CSS, space time codes, decoders deep dive, DEM pipelines, LER methodology, pymatching compatibility, batch decoding, reproducibility, testing strategy, deployment, release engineering, licensing, education, and operations.
Artifacts and integrity
The builder is deterministic: fixed timestamps make every rebuild bit identical, so the hashes below are stable forever.
Per artifact sidecars, a combined SHA256SUMS, an SPDX 2.3 SBOM, and
provenance records binding each file to its release commit and runtime
pins live under dist/. The MCP Registry descriptor in server.json
matches the Desktop bundle byte for byte.
System requirements
Security and privacy
The default installation exposes exactly eight stable tools over local stdio. Research and administrative servers require deliberate enabling, privileged operations demand per call confirmation, and every process enforces its own call budgets so a runaway agent hits a ceiling instead of your machine. Session hooks persist nothing beyond a tool name and a timestamp. Full trust boundaries, risk classifications, scanner guidance, and advisory posture are documented in SECURITY.md, with the network stance in PRIVACY.md.
Documentation
Development
CI enforces the same gates on every push to main. Tagging with v*
additionally builds all artifacts, publishes the GitHub release, and
updates the MCP Registry entry automatically.
License
Proprietary. Copyright © 2026 Guillaume Lessard / iD01t Productions. See
LICENSE.md. The qector-decoder-v3 backend is free for
personal, academic, educational, and non commercial research; commercial
use requires a license from
qector.store/pricing.
Contact
Website https://www.qector.store · Licensing [email protected] · Support [email protected] · Security disclosure [email protected] (private)
QECTOR Claude Plugin v1.0.6
Built on qector-decoder-v3 v1.0.0 · Rust / PyO3 core
Every correction verified against H c = s (mod 2)
Source: README.md at commit 4ff2854
Tools
0Version history
1- v1.0.6LatestSep 16, 2026
Score
40% 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
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.