CUDA-Q Docs
PYPI · CUDAQ-DOCS-MCP · SCANNED AUG 18
CUDA-Q docs, API reference, and runnable examples for AI agents, pinned to your installed version.
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 →
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 33 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 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · cudaq-docs-mcp
claude mcp add rogerawong-cudaq-docs-mcp -- uvx cudaq-docs-mcp
codex mcp add rogerawong-cudaq-docs-mcp -- uvx cudaq-docs-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rogerawong-cudaq-docs-mcp": {
"type": "local",
"command": [
"uvx",
"cudaq-docs-mcp"
],
"enabled": true
}
}
} openclaw mcp add rogerawong-cudaq-docs-mcp --command uvx --arg cudaq-docs-mcp
mcp_servers:
rogerawong-cudaq-docs-mcp:
command: "uvx"
args: ["cudaq-docs-mcp"] {
"mcpServers": {
"rogerawong-cudaq-docs-mcp": {
"command": "uvx",
"args": [
"cudaq-docs-mcp"
]
}
}
} 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.
- 15 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Aug 26 68
First indexed and scored.
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 18 Aug 2026 · Analysed pypi/cudaq-docs-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
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.