Privi Quantum
REMOTE · PRIVI-QUANTUM-VVMJ.ONRENDER.COM
Quantum on IonQ/IBM/Braket: spending mandates, signed benchmarks, paid PQC CBOM, advantage receipts.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (quantum_mandate_revoke). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11050 tokens (~155/item across 71 items; 71 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (13% 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
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 72 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 21 Nov 26 +1
- New tool “quantum_hardware_evidence” functional
- New tool “quantum_evidence_lab” functional
- New tool “car_smartcar_sync” functional
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 62
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 21 Nov 2026 · Probed https://privi-quantum-vvmj.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of privi-quantum-vvmj.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://privi-quantum-vvmj.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://privi-quantum-vvmj.onrender.com/mcp | HTTPS enforced | 301 | https://privi-quantum-vvmj.onrender.com/mcp |
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 →
quantum_benchmarks Privi Quantum benchmarks ~102
The latest signed benchmark suite: Privi's quantum solver against exhaustive search and simulated annealing on a fixed set of factory problems (6-16 qubits), with each verdict, how often the circuit finds the optimum, and its lift over random guessing, plus finished real-hardware runs with their receipts. Published whichever side wins. Public page: /benchmarks. Paid per call via x402 when payments are on (see quantum_pricing).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quantum_circuit_stats Quantum circuit stats ~90
Qubits, gate counts, two-qubit gates and depth of a circuit after rewriting to basic gates, so you know what you are about to run before paying for hardware. The circuit is not run or stored.
| Name | Type | Req | Description |
|---|---|---|---|
| qasm | string | yes | The circuit as OpenQASM 2.0 or 3.0 text (Qiskit: qasm2.dumps(circuit)) |
No output schema declared.
No examples provided.
quantum_evidence_lab Quantum Evidence Lab ~180
Independent simulator evidence for QAOA vs QASM. Reproducible SHA-256 receipt, exact classical optimum and optional sampling diagnostics. This free scientific preview does NOT run an IBM QPU or prove quantum advantage.
| Name | Type | Req | Description |
|---|---|---|---|
| Q | array | yes | QUBO matrix Q; maximum 10x10. Minimize x^T Q x + offset. |
| betas | array | yes | Trained QAOA mixer angles, one per layer (1-4). |
| counts | – | – | Optional user-supplied bitstring counts, marked unverified. |
| gammas | array | yes | Trained QAOA cost angles, one per layer (1-4). |
| offset | number | – | QUBO additive constant. |
| qasm | – | – | Optional OpenQASM 2 circuit to audit; otherwise verify the exporter itself. |
Structured output declared, but exposes no named fields.
No examples provided.
quantum_hardware_evidence Quantum Hardware Evidence ~234
Offline analysis of QAOA, compiled QASM, and empirical samples. No provider calls, no QPU charges, no job verification or quantum advantage claim.
| Name | Type | Req | Description |
|---|---|---|---|
| Q | array | yes | QUBO matrix, max 10x10. |
| backend | string | yes | Self-reported backend identifier. |
| betas | array | yes | QAOA beta angles. |
| compiled_qasm | string | yes | Backend-compiled OpenQASM 2 in h/rx/rz/cx basis. |
| completed_utc | string | yes | ISO UTC completion timestamp. |
| counts | object | yes | Unverified bitstring count data. |
| gammas | array | yes | QAOA gamma angles. |
| offset | number | – | QUBO additive cost. |
| provider | string | yes | Self-reported provider identifier. |
| provider_job_id | string | yes | Self-reported provider job ID; not independently authenticated. |
| shots | integer | yes | Reported shot count. |
| source_qasm | string | yes | Original OpenQASM 2 circuit. |
| submitted_utc | string | yes | ISO UTC submission timestamp. |
Structured output declared, but exposes no named fields.
No examples provided.
quantum_hardware_job Quantum hardware job ~70
Status of a quantum hardware job; once done, the decision, measurement statistics, the signed attestation and the Quantum Advantage Receipt. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | hw_... id from quantum_run_hardware |
No output schema declared.
No examples provided.
quantum_leaderboard Privi Quantum Leaderboard ~76
Every quantum backend (IBM Quantum, IonQ, Amazon Braket, simulators) ranked only by runs Privi measured and sealed: share that found the proven optimum, jobs finished, median turnaround, median cost, and the quantum vs classical tally from Quantum Advantage Receipts. Free. Page: /leaderboard.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quantum_mandate_check Quantum Mandate: dry run ~116
Would this paid run be allowed under the mandate? Picks the backend the router would use, estimates the price and checks it against every term without spending anything. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | 'auto' or a backend id |
| mandate_id | string | yes | qm_... id |
| policy | string | – | cheapest | fastest | hardware |
| problem | string | – | Problem you plan to run |
| shots | integer | – | – |
No output schema declared.
No examples provided.
quantum_mandate_request Quantum Mandate: request one ~224
Draft a Quantum Mandate: the spending terms under which this agent may run paid quantum hardware jobs. Returns a sign_url for the person who approved the agent; they sign the exact terms with their passkey. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| backends | – | – | Allowed backend ids from quantum_backends (default: any paid backend) |
| budget_usd | number | yes | Total the agent may spend on paid quantum hardware under this mandate |
| days | integer | – | How long the mandate lasts once signed (1-365) |
| max_per_job_usd | – | – | Most one job may cost (default: the whole budget) |
| max_shots | integer | – | Most shots per job (1-10000) |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
| problems | – | – | Allowed problems (default: any) |
| purpose | string | yes | What the runs are for, in plain words (shown to the person who signs) |
No output schema declared.
No examples provided.
quantum_mandate_revoke Quantum Mandate: revoke (agent) ~117
The agent gives up its own mandate (the person can also revoke on the mandate page with their passkey). The revocation is signed and anchored. Paid per call via x402 when payments are on; the person who signed it can also revoke it on the mandate web page with their passkey.
| Name | Type | Req | Description |
|---|---|---|---|
| mandate_id | string | yes | qm_... id |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
| reason | string | – | Why |
No output schema declared.
No examples provided.
quantum_mandate_status Quantum Mandate: status ~67
A Quantum Mandate's terms, status (draft, active, expired, revoked), spend, remaining budget and every charge and refund. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| mandate_id | string | yes | qm_... id |
No output schema declared.
No examples provided.
quantum_optimize Quantum optimize ~196
Solve a factory decision with the Quantum Approximate Optimization Algorithm. Returns the decision in plain terms, how close it is to the proven optimum, and a post-quantum signed attestation (Ed25519 + ML-DSA-87) that is anchored on chain (Base). Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Problem data in the shape quantum_problems describes |
| include_qasm | boolean | – | Also return the trained circuit as OpenQASM 2.0 for real quantum hardware |
| layers | integer | – | QAOA depth p (1-4). Deeper finds better answers more often but runs longer. |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| shots | integer | – | Measurements to sample from the trained circuit (1-100000) |
No output schema declared.
No examples provided.
quantum_pricing Privi Quantum pricing ~54
Which tools are paid, their price per call, how to pay (x402: USDC on Base, or the PRIVI token), and the payout wallet ($0.001). Failed calls are never charged.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quantum_problems List optimization problems ~28
The ready-made problems quantum_optimize accepts and the data each one needs, with an example.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quantum_run_circuit Run your own circuit (Qiskit / OpenQASM) ~327
Bring your own quantum circuit. Paste the OpenQASM that Qiskit writes and Privi runs it on IBM Quantum, IonQ, Amazon Braket or its own simulator, picked by price or speed, then seals the measurement counts with a post-quantum signature anchored on chain. Standard Qiskit gates are rewritten exactly into h, rz, rx, cx; all qubits are measured at the end. Poll with quantum_hardware_job. Free on free backends; paid QPUs need a Quantum Mandate.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | 'auto' or a backend id from quantum_backends (local, ionq:simulator, ionq:qpu.forte-1, ibm:<name>, braket:<name>) |
| label | string | – | Optional short name for the run (kept in the sealed record) |
| mandate_id | – | – | qm_... Quantum Mandate (required for paid backends) |
| max_cost_usd | – | – | Refuse if the estimated price is above this |
| policy | string | – | With backend='auto': cheapest | fastest | hardware (real QPUs only) |
| privi_pass | – | – | Your Privi pass (ppass_...); required with a mandate |
| qasm | string | yes | OpenQASM 2.0 or 3.0 text, e.g. from Qiskit: qiskit.qasm2.dumps(circuit) or qiskit.qasm3.dumps(circuit) |
| shots | integer | – | Shots (1-10000) |
No output schema declared.
No examples provided.
quantum_run_hardware Run on quantum hardware ~360
Train the CVaR-QAOA circuit, route it to a quantum backend (IonQ, IBM Quantum, Amazon Braket or this server's simulator) by price or speed, and return a job id. When the run finishes, the answer is sealed with a post-quantum signed attestation and a Quantum Advantage Receipt against classical baselines. Poll with quantum_hardware_job. Paid per call via x402 when payments are on (a routing fee, see quantum_pricing). Paid QPUs also need a Quantum Mandate signed by the agent's human (quantum_mandate_request) and run only within the operator's configured budget. A call that is blocked or fails to submit is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | 'auto' or a backend id from quantum_backends (e.g. ionq:simulator, ionq:qpu.forte-1, ibm:ibm_brisbane) |
| data | object | yes | Problem data in the shape quantum_problems describes |
| layers | integer | – | QAOA depth p (1-4) |
| mandate_id | – | – | qm_... Quantum Mandate your human signed; required for any paid backend |
| max_cost_usd | – | – | Refuse if the estimated price is above this |
| policy | string | – | With backend='auto': cheapest | fastest | hardware (real QPUs only) |
| privi_pass | – | – | Your Privi pass (ppass_...); required with a mandate |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| shots | integer | – | Shots on the backend (1-10000) |
No output schema declared.
No examples provided.
quantum_status Privi Quantum status ~30
What this server runs: algorithm, qubit limit, quantum backends, signing keys, and anchoring.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quantum_verify Verify a Privi Quantum attestation ~89
Check both post-quantum signatures, the body hash, and the on-chain anchor of a result. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | Or a full attestation object (from GET /attestations/<id>) to check offline |
| attestation_id | – | – | An attestation id (qa_...) issued by this server |
No output schema declared.
No examples provided.
vault_keygen Privi Vault: new hybrid post-quantum key ~121
Create a hybrid X25519 + ML-KEM (FIPS 203) key pair for Privi Vault. The private key is returned once and not stored here; for the strongest setup generate it locally with `python -m privi_quantum.vault keygen`. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| suite | string | – | X25519+ML-KEM-768 (default) | X25519+ML-KEM-1024 (CNSA 2.0 KEM level) |
No output schema declared.
No examples provided.
vault_open Privi Vault: open an envelope ~84
Decrypt a Privi Vault envelope. Nothing is stored; for sensitive data prefer opening locally with `python -m privi_quantum.vault open`. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | A Privi Vault envelope |
| private_key | object | yes | The recipient private key from vault_keygen |
No output schema declared.
No examples provided.
vault_receipt Privi Vault: receipt for a locally sealed envelope ~112
Get a signed, chain-anchored protection receipt proving data was under hybrid post-quantum encryption by a given time, for envelopes sealed with the local Privi Vault tool. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | – | – | An envelope sealed locally (checked for structure; nothing is decrypted) |
| envelope_sha256 | – | – | Or only the envelope's SHA-256, so the envelope never leaves your machine |
| label | string | – | What this protects |
No output schema declared.
No examples provided.
vault_seal Privi Vault: seal data (harvest-now-decrypt-later protection) ~159
Re-wrap long-lived sensitive data under hybrid post-quantum encryption (X25519 + ML-KEM, AES-256-GCM) so data recorded today can't be decrypted by a future quantum computer. Returns the envelope and a signed protection receipt anchored on chain. Plaintext is not stored. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| data_base64 | – | – | Or bytes to protect, base64 (up to 5 MB) |
| label | string | – | What this is, e.g. 'supplier contract 2026' (kept in the envelope and receipt) |
| public_key | object | yes | Recipient public key from vault_keygen |
| text | – | – | Text to protect |
No output schema declared.
No examples provided.
How do I install the Privi Quantum MCP server?
Privi Quantum is a hosted endpoint at https://privi-quantum-vvmj.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · privi-quantum-vvmj.onrender.com
claude mcp add --transport http canoydario847-cloud-privi-quantum 'https://privi-quantum-vvmj.onrender.com/mcp'
What is the Privi Quantum MCP server?
Privi Quantum is an MCP server listed in the public MCP registry as io.github.canoydario847-cloud/privi-quantum. Quantum on IonQ/IBM/Braket: spending mandates, signed benchmarks, paid PQC CBOM, advantage receipts. This page covers its hosted endpoint (https://privi-quantum-vvmj.onrender.com/mcp).
Is the Privi Quantum MCP server safe to use?
Privi Quantum scores 65 out of 100 on VerifyMCP. 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 Privi Quantum MCP server expose?
Privi Quantum exposes 71 tools: quantum_status, quantum_pricing, quantum_problems, quantum_evidence_lab, quantum_hardware_evidence, and 66 more. Their descriptions and schemas cost roughly 9,289 tokens of context every time the server is loaded.
Does the Privi Quantum MCP server require authentication?
No. We connected to Privi Quantum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Privi Quantum MCP server still maintained?
Privi Quantum is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Privi Quantum MCP server?
VerifyMCP ran 13 checks on Privi Quantum, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.