qector vs io.github.Ranshiv/noether-physics
qector is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
qector is a plugin bundle for AI coding tools published by Guillaume Lessard. No marketplace we read lists it any more. io.github.Ranshiv/noether-physics is an MCP server published by Ranshiv. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace guillaumelessard/qector-claude-plugin | Removed on 2026-10-15 Version: 1.0.6 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (PyPI): 578 Downloads/week (PyPI): 28 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | qectorno longer listed · | io.github.Ranshiv/noether-physics |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (noether-physics) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 47 | Not a bundle |
| Licence (differs) | Proprietary | Not stated |
| Repository (differs) | github.com/guillaumelessard/qector-claude-plugin | github.com/ranshiv/noether-physics |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of qector
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Qiskit Documentation MCP Server
MCP server for querying and retrieving Qiskit documentation, guides, and API references
-
IBM Quantum OpenQASM 2.0 MCP — list backends, submit QASM, poll jobs, get histograms.
-
AI triage for quantum computing POC proposals. Screens before budget is allocated.
-
Qiskit IBM Transpiler MCP Server
MCP server for AI Transpiler IBM Quantum services
-
Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.
-
Find the right NVIDIA skill for GPU acceleration, CUDA, AI agents, data loading, training, inference, robotics, Physical AI, Omniverse, simulation, and other NVIDIA-powered…
What each says it does
qector
Local QECTOR quantum error correction plugin for Claude Code and Claude Desktop with strict math skills, focused agents, and qector-decoder-v3 MCP servers.
io.github.Ranshiv/noether-physics
Physics assistant: checked equations, live simulations, claims verified against arXiv papers
How to run each
qector
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.Ranshiv/noether-physics As a local MCP server: PyPI package
claude mcp add --transport stdio noether-physics -- uvx noether-physics
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.Ranshiv/noether-physics publish no settings it asks for, so we do not compare settings.
What it can do: qector · What it can do: io.github.Ranshiv/noether-physics · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.