Qiskit IBM Runtime MCP Server
PYPI · QISKIT-IBM-RUNTIME-MCP-SERVER · SCANNED SEP 20
MCP server for IBM Quantum computing services through Qiskit IBM Runtime
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 5 of 48 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3156 tokens (~126/item across 25 items; 20 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_saved_account_tool" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Qiskit IBM Runtime MCP Server server?
Qiskit IBM Runtime MCP Server runs locally as a PyPI package, launched with uvx qiskit-ibm-runtime-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · qiskit-ibm-runtime-mcp-server
claude mcp add qiskit-qiskit-ibm-runtime-mcp-server -- uvx qiskit-ibm-runtime-mcp-server
{
"mcpServers": {
"qiskit-qiskit-ibm-runtime-mcp-server": {
"command": "uvx",
"args": [
"qiskit-ibm-runtime-mcp-server"
]
}
}
} {
"servers": {
"qiskit-qiskit-ibm-runtime-mcp-server": {
"command": "uvx",
"args": [
"qiskit-ibm-runtime-mcp-server"
]
}
}
} codex mcp add qiskit-qiskit-ibm-runtime-mcp-server -- uvx qiskit-ibm-runtime-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qiskit-qiskit-ibm-runtime-mcp-server": {
"type": "local",
"command": [
"uvx",
"qiskit-ibm-runtime-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add qiskit-qiskit-ibm-runtime-mcp-server --command uvx --arg qiskit-ibm-runtime-mcp-server
mcp_servers:
qiskit-qiskit-ibm-runtime-mcp-server:
command: "uvx"
args: ["qiskit-ibm-runtime-mcp-server"] {
"McpServers": {
"qiskit-qiskit-ibm-runtime-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"qiskit-ibm-runtime-mcp-server"
]
}
}
} assistant mcp add qiskit-qiskit-ibm-runtime-mcp-server -t stdio -c uvx -a qiskit-ibm-runtime-mcp-server
{
"mcpServers": {
"qiskit-qiskit-ibm-runtime-mcp-server": {
"command": "uvx",
"args": [
"qiskit-ibm-runtime-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/qiskit-ibm-runtime-mcp-server@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 48 packages
| Packages resolved | 48 |
|---|---|
| Stale | 5 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
active_account_info_tool ~57
Get information about the currently active IBM Quantum account. Returns details about the account being used in the current session, including channel, instance, and name. This is the account used for all quantum operations. Tokens are masked for security.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
active_instance_info_tool ~49
Get the Cloud Resource Name (CRN) of the currently active instance. Returns the instance identifier determining which quantum backends and resources are accessible. Important for users with access to multiple instances.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
available_instances_tool ~64
List all IBM Quantum instances available to the active account. Returns information about all instances (organizations, projects, or service plans) the user has access to, including CRN, plan type, and name. Each instance provides access to different quantum backends with different quotas.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
cancel_job_tool ~22
Cancel a specific job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_saved_account_tool ~97
Delete a saved IBM Quantum account from disk. WARNING: This permanently removes credentials from ~/.qiskit/qiskit-ibm.json. The operation cannot be undone. Use list_saved_accounts_tool() first to verify the account name before deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | yes | Name of the saved account to delete (e.g., 'ibm_quantum_platform'). Use list_saved_accounts_tool() to find available names. |
Structured output declared, but exposes no named fields.
No examples provided.
find_optimal_qubit_chains_tool ~196
Find optimal linear qubit chains for quantum experiments. Algorithmically identifies the best qubit chains based on coupling map connectivity and calibration data. Essential for experiments requiring linear qubit arrangements (e.g., variational algorithms, error correction).
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | string | yes | Name of the backend (e.g., 'ibm_brisbane') |
| chain_length | integer | – | Number of qubits in the chain (default: 5, range: 2-20) |
| metric | string | – | Scoring metric to optimize: - "two_qubit_error": Minimize sum of CX/ECR gate errors (default) - "readout_error": Minimize sum of measurement errors - "combined": Weighted combination of gate errors,… |
| num_results | integer | – | Number of top chains to return (default: 5, max: 20) |
Structured output declared, but exposes no named fields.
No examples provided.
find_optimal_qv_qubits_tool ~205
Find optimal qubit subgraphs for Quantum Volume experiments. Unlike linear chains, Quantum Volume benefits from densely connected qubit sets where qubits can interact with minimal SWAP operations. This tool finds connected subgraphs and ranks them by connectivity and calibration quality.
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | string | yes | Name of the backend (e.g., 'ibm_brisbane') |
| metric | string | – | Scoring metric to optimize: - "qv_optimized": Balanced scoring for QV (connectivity + errors + coherence) - "connectivity": Maximize internal edges and minimize path lengths - "gate_error": Minimize… |
| num_qubits | integer | – | Number of qubits in the subgraph (default: 5, range: 2-10) |
| num_results | integer | – | Number of top subgraphs to return (default: 5, max: 20) |
Structured output declared, but exposes no named fields.
No examples provided.
get_backend_calibration_tool ~83
Get calibration data for a backend including T1, T2 times and error rates.
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | string | yes | Name of the backend (e.g., 'ibm_brisbane') |
| qubit_indices | – | – | Optional list of specific qubit indices to get data for. If not provided, returns data for the first 10 qubits. |
Structured output declared, but exposes no named fields.
No examples provided.
get_backend_properties_tool ~40
Get detailed properties of a specific backend.
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | string | yes | Name of the backend (e.g., 'ibm_brisbane') |
Structured output declared, but exposes no named fields.
No examples provided.
get_coupling_map_tool ~116
Get the coupling map (qubit connectivity) for an IBM Quantum backend. Supports both real backends (requires credentials) and fake backends (no credentials). Use 'fake_' prefix for offline testing without IBM Quantum credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | string | yes | Name of the backend. Examples: - Real backends: 'ibm_brisbane', 'ibm_fez' (requires credentials) - Fake backends: 'fake_brisbane', 'fake_sherbrooke' (no credentials needed) |
Structured output declared, but exposes no named fields.
No examples provided.
get_job_results_tool ~102
Get measurement results from a completed quantum job. Retrieves the measurement outcomes (counts) from a job that has finished execution. The job must be in DONE status to retrieve results. Use this tool after a job submitted with run_sampler_tool has completed. First check the job status with get_job_status_tool, then retrieve results when the job status is DONE.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | ID of the completed job (returned by run_sampler_tool) |
Structured output declared, but exposes no named fields.
No examples provided.
get_job_status_tool ~25
Get status of a specific job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
least_busy_backend_tool ~17
Find the least busy operational backend.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_backends_tool ~17
List available IBM Quantum backends.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_my_jobs_tool ~22
List user's recent jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_saved_accounts_tool ~63
List all IBM Quantum accounts saved on disk. Returns account information from ~/.qiskit/qiskit-ibm.json including account names and channels. Useful for checking available accounts before initializing the service or before deleting an account. Tokens are masked for security.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
run_estimator_tool ~686
Run a quantum circuit using the Qiskit Runtime EstimatorV2 primitive. The Estimator primitive computes expectation values of observables for quantum circuits. This is essential for variational quantum algorithms (VQE, QAOA), quantum chemistry simulations, and any application requiring expectation value estimation.
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | – | – | Name of the IBM Quantum backend (e.g., 'ibm_brisbane'). If not provided, uses the least busy operational backend. |
| circuit | string | yes | The quantum circuit to execute. Accepts multiple formats: - OpenQASM 3.0 string (recommended): ``` OPENQASM 3.0; include "stdgates.inc"; qubit[2] q; h q[0]; cx… |
| circuit_format | string | – | Format of the circuit input. Options: - "auto" (default): Automatically detect format - "qasm3": OpenQASM 3.0/2.0 text format - "qpy": Base64-encoded QPY binary format |
| observables | – | yes | Observable(s) to measure expectation values. Accepts: - Single Pauli string: "IIXY" (identity on qubits 0,1; X on 2; Y on 3) - List of Pauli strings: ["IIXY", "ZZII", "XXYY"]… |
| optimization_level | integer | – | Qiskit transpilation optimization level (0-3). Default is 1. Higher levels may produce better circuits but take longer. - 0: No optimization - 1: Light op… |
| parameter_values | – | – | Values for parameterized circuits. If the circuit has parameters (e.g., rotation angles), provide a list of float values in the same order as circuit.parameters. Optional if… |
| resilience_level | integer | – | Error mitigation resilience level (0-2). Default is 1. - 0: No error mitigation - 1: Light error mitigation (default, recommended) - 2: Heavy error mitigation (… |
| zne_mitigation | boolean | – | Enable Zero Noise Extrapolation (ZNE). Default is True. ZNE extrapolates results to the zero-noise limit for better accuracy. |
| zne_noise_factors | – | – | Noise amplification factors for ZNE. Default is (1, 1.5, 2). Only used if zne_mitigation is True. |
Structured output declared, but exposes no named fields.
No examples provided.
run_sampler_tool ~501
Run a quantum circuit using the Qiskit Runtime SamplerV2 primitive. The Sampler primitive executes quantum circuits and returns measurement outcome samples. This is the primary way to run quantum circuits on IBM Quantum hardware. Error Mitigation (enabled by default): - Dynamical Decoupling: Suppresses decoherence during idle periods - Twirling: Randomizes errors into stochastic noise for better results
| Name | Type | Req | Description |
|---|---|---|---|
| backend_name | – | – | Name of the IBM Quantum backend (e.g., 'ibm_brisbane'). If not provided, uses the least busy operational backend. |
| circuit | string | yes | The quantum circuit to execute. Accepts multiple formats: - OpenQASM 3.0 string (recommended): ``` OPENQASM 3.0; include "stdgates.inc"; qubit[2] q; bit[2] c;… |
| circuit_format | string | – | Format of the circuit input. Options: - "auto" (default): Automatically detect format - "qasm3": OpenQASM 3.0/2.0 text format - "qpy": Base64-encoded QPY binary format |
| dd_sequence | string | – | Dynamical decoupling pulse sequence. Options: - "XX": Basic X-X sequence - "XpXm": X+/X- sequence - "XY4": 4-pulse XY sequence (default, most robust) |
| dynamical_decoupling | boolean | – | Enable dynamical decoupling to suppress decoherence during idle periods. Default is True (recommended). |
| measure_twirling | boolean | – | Enable twirling on measurements for readout error mitigation. Default is True (recommended). |
| shots | integer | – | Number of measurement shots (repetitions). Default is 4096. Higher values give more statistical accuracy. |
| twirling | boolean | – | Enable Pauli twirling on 2-qubit gates to convert coherent errors into stochastic noise. Default is True (recommended). |
Structured output declared, but exposes no named fields.
No examples provided.
setup_ibm_quantum_account_tool ~70
Set up IBM Quantum account with credentials. If token is not provided, will attempt to use QISKIT_IBM_TOKEN environment variable or saved credentials from ~/.qiskit/qiskit-ibm.json
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | – |
| token | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
usage_info_tool ~51
Get usage statistics and quota information for the active instance. Returns detailed metrics including job counts, quantum runtime consumption, quota limits, and billing period information. Useful for monitoring resource utilization and planning job submissions.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the Qiskit IBM Runtime MCP Server server?
Qiskit IBM Runtime MCP Server is listed in the public MCP registry as io.github.Qiskit/qiskit-ibm-runtime-mcp-server. MCP server for IBM Quantum computing services through Qiskit IBM Runtime. This page covers its PyPI package (qiskit-ibm-runtime-mcp-server).
Is the Qiskit IBM Runtime MCP Server server safe to use?
Qiskit IBM Runtime MCP Server scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Qiskit IBM Runtime MCP Server server expose?
Qiskit IBM Runtime MCP Server exposes 20 tools: setup_ibm_quantum_account_tool, list_backends_tool, least_busy_backend_tool, get_backend_properties_tool, get_backend_calibration_tool, and 15 more. Their descriptions and schemas cost roughly 2,483 tokens of context every time the server is loaded.
Is the Qiskit IBM Runtime MCP Server server still maintained?
Qiskit IBM Runtime MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Qiskit IBM Runtime MCP Server server under?
Qiskit IBM Runtime MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.