Arquestra — Scientific Computing Orchestration vs FlagQuantum MCP Server
Arquestra — Scientific Computing Orchestration is an MCP server published by Apertura-AI. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). FlagQuantum MCP Server is an MCP server published by FlagQuantum. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Arquestra — Scientific Computing Orchestration |  FlagQuantum MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.1 Downloads/month (PyPI): 1 051 Downloads/week (PyPI): 214 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Not listed | Listed Version: 0.3.1 Downloads/month (PyPI): 1 051 Downloads/week (PyPI): 214 Forks (GitHub): 0 Stars (GitHub): 0 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 | Arquestra — Scientific Computing Orchestration | FlagQuantum MCP Server |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Remote server (api.apertura-ai.de/mcp/orchestration) | On your machine (flagquantum-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Proprietary | Apache-2.0 |
| Repository (differs) | github.com/apertura-ai/arquestra-claude-plugin | github.com/flagquantum/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-17 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Arquestra — Scientific Computing Orchestration
AI orchestration for computational chemistry and HPC workflows.
FlagQuantum MCP Server
Build, compile, run and export FlagQuantum circuits locally. No credentials or outbound network.
How to run each
Arquestra — Scientific Computing Orchestration As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install arquestra@claude-communityFlagQuantum MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio flagquantum-mcp-server -- uvx flagquantum-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Arquestra — Scientific Computing Orchestration has a remote endpoint we check. How we check endpoints
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 Arquestra — Scientific Computing Orchestration publish no settings it asks for, so we do not compare settings.
What it can do: Arquestra — Scientific Computing Orchestration · What it can do: FlagQuantum MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.