CUDA-Q Docs
PYPI · CUDAQ-DOCS-MCP
CUDA-Q docs, API reference, and runnable examples for AI agents, pinned to your installed version.
Available components
Last scanned (7 minutes ago)
Scores higher than 98% of PyPI servers
Category Code Search and Documentation
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rogerawong/cudaq-docs-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 52 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 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
- Tool/resource definitions use about 700 tokens (~100/item across 7 items; 5 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 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.
- 13 Oct 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 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 83.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 90. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −4
- Stability: pass → 0.77 functional
- 2 Oct 26 +1
- Stability: 0.97 → pass security
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 17 Oct 2026 · Analysed pypi/cudaq-docs-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | rogerawong/cudaq-docs-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rogerawong/cudaq-docs-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 2429306902 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4f52f48b46071a828d0e7556c963c87d2ee851b21b9c429bf1f17ea422fa5a5f |
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 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| 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 →
find_api ~99
Resolve a CUDA-Q API symbol to its canonical definition and doc URL. Args: name: Symbol name, full or partial: "sample", "cudaq.observe", "qvector", "set_target". language: "python" or "cpp" to filter; omit for both. version: Docs version. Defaults to the installed cudaq version.
| Name | Type | Req | Description |
|---|---|---|---|
| language | – | – | – |
| name | string | yes | – |
| version | – | – | – |
No output schema declared.
No examples provided.
get_page ~76
Fetch one documentation page as clean markdown. Args: path: Page path as returned by search_docs, for example "using/quick_start" or "using/backends/sims/svsims". version: Docs version. Defaults to the installed cudaq version.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| version | – | – | – |
No output schema declared.
No examples provided.
list_targets ~101
List CUDA-Q execution targets (backends) with guidance on choosing. Covers simulators (CPU, GPU state vector, tensor network, noisy, dynamics), quantum hardware providers, and cloud aggregators, each with selection snippets and doc URLs. Call this when deciding where to run a kernel or when the user names a provider. Args: category: Optional filter: "simulator", "hardware", or "cloud".
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
No output schema declared.
No examples provided.
search_docs ~149
Search the NVIDIA CUDA-Q documentation and return ranked excerpts. Use this before answering any CUDA-Q question from memory: the platform moves quickly and memorized APIs are often stale. Each result carries a breadcrumb, an excerpt, and the canonical doc URL to cite. Args: query: Natural language or keywords, for example "run kernel on GPU state vector" or "quantinuum credentials". version: Docs version such as "0.15.0" or "latest". Defaults to the installed cudaq version. limit: Maximum number of results (default 5).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| version | – | – | – |
No output schema declared.
No examples provided.
search_examples ~144
Find complete, runnable CUDA-Q example programs. Sources are the example, snippet, and application files shipped in the CUDA-Q repository at the matching release. Prefer adapting these over writing kernels from memory. Args: query: What the example should show, for example "GHZ state", "VQE", or "noise model". language: "python" or "cpp" to filter; omit for both. version: Docs version. Defaults to the installed cudaq version. limit: Maximum number of examples (default 3).
| Name | Type | Req | Description |
|---|---|---|---|
| language | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| version | – | – | – |
No output schema declared.
No examples provided.
How do I install the CUDA-Q Docs MCP server?
CUDA-Q Docs runs locally as a PyPI package, launched with uvx cudaq-docs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cudaq-docs-mcp
claude mcp add rogerawong-cudaq-docs-mcp -- uvx cudaq-docs-mcp
What is the CUDA-Q Docs MCP server?
CUDA-Q Docs is an MCP server listed in the public MCP registry as io.github.rogerawong/cudaq-docs-mcp. CUDA-Q docs, API reference, and runnable examples for AI agents, pinned to your installed version. This page covers its PyPI package (cudaq-docs-mcp).
Is the CUDA-Q Docs MCP server safe to use?
CUDA-Q Docs scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. 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 CUDA-Q Docs MCP server expose?
CUDA-Q Docs exposes 5 tools: search_docs, get_page, find_api, search_examples, list_targets. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.
Is the CUDA-Q Docs MCP server still maintained?
CUDA-Q Docs is still listed as active in the MCP registry. We last reached this channel on 17 October 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 CUDA-Q Docs MCP server under?
CUDA-Q Docs 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.