io.github.Blite-HQ/qnexus-mcp
PYPI · QNEXUS-MCP
MCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum.
Available components
Last scanned (9 hours ago)
Scores higher than 94% of PyPI servers
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
- 3 of 49 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Blite-HQ/qnexus-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 105 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1269 tokens (~126/item across 10 items; 10 tools + 0 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.87 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: 0.77 → 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 5 Nov 2026 · Analysed pypi/qnexus-mcp@0.2.0
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 | Blite-HQ/qnexus-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Blite-HQ/qnexus-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0 |
| Rekor log index | 2223487547 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9933627fb669a1b697281bce893e71817cf370fe1490b95ed88798a060421df5 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 49 packages
| Packages resolved | 49 |
|---|---|
| Stale | 3 |
| 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 →
nexus_auth_status ~17
Report whether a valid Nexus session exists.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
nexus_device_status ~33
Report whether a device is online. Emulators/syntax checkers are always available.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_get_quota ~17
Return remaining compilation/simulation quotas.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
nexus_get_results ~79
Return measurement counts for a completed job by id. Counts are capped at the top --max-outcomes outcomes by frequency; total_outcomes / omitted_outcomes / omitted_shots report any truncation. Multi-circuit (batch) jobs return one entry per circuit under `items`, in submission order.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_job_cost ~29
Return the HQC cost of an existing job by id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_job_status ~26
Return the status of a job by id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_list_devices ~17
List available backends and their status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
nexus_list_jobs ~118
List jobs visible to the user (one page of up to `limit`, plus the total count). Optional filters: exact `project` name, `status` (e.g. COMPLETED, RUNNING, ERROR), and a `name_like` substring. Occasionally returns a Nexus-side server error unrelated to your request; if so, use nexus_job_status / nexus_get_results by id instead of retrying this call.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name_like | – | – | – |
| project | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_list_projects ~69
List Nexus projects visible to the user (one page of up to `limit`, plus the total count). Optional `name_like` substring filter; set `archived` to list archived projects instead.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| limit | integer | – | – |
| name_like | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
nexus_whoami ~16
Return the authenticated Nexus user.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.Blite-HQ/qnexus-mcp server?
io.github.Blite-HQ/qnexus-mcp runs locally as a PyPI package, launched with uvx qnexus-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 · qnexus-mcp
claude mcp add blite-hq-qnexus-mcp -- uvx qnexus-mcp
What is the io.github.Blite-HQ/qnexus-mcp server?
io.github.Blite-HQ/qnexus-mcp is listed in the public MCP registry as io.github.Blite-HQ/qnexus-mcp. MCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum. This page covers its PyPI package (qnexus-mcp).
Is the io.github.Blite-HQ/qnexus-mcp server safe to use?
io.github.Blite-HQ/qnexus-mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.Blite-HQ/qnexus-mcp server expose?
io.github.Blite-HQ/qnexus-mcp exposes 10 tools: nexus_auth_status, nexus_whoami, nexus_list_devices, nexus_device_status, nexus_list_projects, and 5 more. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Is the io.github.Blite-HQ/qnexus-mcp server still maintained?
io.github.Blite-HQ/qnexus-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.Blite-HQ/qnexus-mcp server under?
io.github.Blite-HQ/qnexus-mcp 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.
What did VerifyMCP test on the io.github.Blite-HQ/qnexus-mcp server?
VerifyMCP ran 16 checks on io.github.Blite-HQ/qnexus-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.