MCP.Market

QECTOR Quantum Error Correction MCP server

by GuillaumeLessard·io.github.GuillaumeLessard/qector-desktop·v1.0.6·1 stars

Local quantum error correction tools; decoder output verified against H c = s (mod 2).

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed QECTOR Quantum Error Correction yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

QECTOR Quantum Error Correction tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 69 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How QECTOR Quantum Error Correction compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install QECTOR Quantum Error Correction in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the QECTOR Quantum Error Correction repository's README, as published. We do not edit it. Read it on GitHub

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.

carry scripts/qector-python (POSIX sh) and scripts/qector-python.cmd (Windows). They live in scripts/, not bin/: claude.ai-hosted plugins may not ship bin/ executables because they land on PATH without ever appearing on the admin approval surface. A validator now hard-fails any build that reintroduces bin/.

  • The plugin archive, the source distribution, and the Desktop bundle all

wins first, then python3, then python, with the Windows py launcher tried ahead of them all.

  • Resolution is governed, not guessed. An administrator pinned interpreter

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.

  • The supported window is enforced, not documented. Only Python 3.9

absolute interpreter path and every launcher honors it above discovery.

  • Pinning is first class on both surfaces. Set QECTOR_PYTHON to an

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-01downgradeA → Bscore 78

QECTOR Quantum Error Correction: common questions

Is QECTOR Quantum Error Correction MCP server safe?
Mostly: it is graded B (78/100). Read the QECTOR Quantum Error Correction safety report
Does QECTOR Quantum Error Correction need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is QECTOR Quantum Error Correction maintained?
The last commit was 72 days ago (2026-08-24). The latest release is v1.0.6.
How does QECTOR Quantum Error Correction compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.