Qiskit Code Assistant MCP Server
A collection of MCP servers to allow LLMs to use the qiskit,qiskit-ibm-runtime library, qiskit-ibm-transpiler, qiskit-c
Compare Qiskit Code Assistant MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Qiskit Code Assistant MCP Server safe? Qiskit Code Assistant MCP Server scores 61.3/100 (Grade C), ranked #312 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 39% of recent commits are signed; last pushed 2026-07-13. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in MCP Servers
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs MCP Servers
61.3 / 100 · 100.0% confidenceQiskit Code Assistant MCP Server MCP Servers average (761 agents)
Activity Inputs
47.0 / 100Supply Chain Trust
Is Qiskit Code Assistant MCP Server safe?
Does Qiskit Code Assistant MCP Server publish package provenance?
Does Qiskit Code Assistant MCP Server have an OpenSSF Scorecard?
Is Qiskit Code Assistant MCP Server actively maintained?
What license does Qiskit Code Assistant MCP Server use?
Are Qiskit Code Assistant MCP Server's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Qiskit Code Assistant MCP Server?
For maintainers
HVTrust scores Qiskit Code Assistant MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/qiskit-code-assistant-mcp-server)
<a href="https://hvtracker.net/agents/qiskit-code-assistant-mcp-server"><img src="https://hvtracker.net/badge/qiskit-code-assistant-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON