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 →
accelerator_info Quantum Agent Accelerator: how it works ~69
The program that upgrades an AI agent into a certified quantum agent: the four steps (Q1-Q4), the levels, how to make an ML-DSA key in five lines, and the free directory checks. Paid per call via x402 when payments are on (see quantum_pricing).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
car_charge_plan Privi Car: cheapest EV charging plan ~185
Pick which time slots to charge in so the car has the energy it needs at the lowest cost. Runs on the CVaR-QAOA quantum simulator and against exact search; the signed receipt shows both and the plan is the proven best. Returns the slots, cost, and savings over charging right away. A plan only: nothing is sent to a charger.
| Name | Type | Req | Description |
|---|---|---|---|
| charger_kw | number | yes | Charger power in kW |
| energy_needed_kwh | number | yes | Energy to add before departure, in kWh |
| price_per_kwh | array | yes | Electricity price for each time slot before departure (2-16 slots) |
| slot_hours | number | – | Length of one slot in hours (default 1) |
| switch_penalty_usd | number | – | Cost charged for each start/stop, to favor one continuous session (default 0) |
No output schema declared.
No examples provided.
car_edge_job Privi Car: parked-car edge job gate (simulation) ~145
Research simulation of the admission gate for compute on a parked car's companion device. A job is admitted only with owner opt-in, vehicle parked, external power and safe temperature, a matching tenant, a fresh nonce and a short expiry; replays are rejected. Returns a digest receipt with zero credits. No job runs on any vehicle and no rewards are paid.
| Name | Type | Req | Description |
|---|---|---|---|
| job | object | yes | {tenant, nonce (32 hex), expiresAt (ms, within 60 s), payload (text up to 64 KB)} |
| policy | object | yes | {tenant, ownerOptIn, parked, externalPower, thermalSafe}; all four flags must be true |
No output schema declared.
No examples provided.
car_fleet_assign Privi Car: assign jobs to a fleet ~153
Give every job (delivery, pickup, service call) to a vehicle at the lowest total cost, with a limit per vehicle. Proven optimal classically (Hungarian method) for up to 60 jobs; small cases (16 qubits or fewer) also run on the quantum simulator and the signed receipt shows both.
| Name | Type | Req | Description |
|---|---|---|---|
| cost | – | – | Optional jobs x vehicles cost matrix (km, minutes or dollars) |
| jobs | array | yes | Jobs as {name, lat, lon} (or {name} with a cost matrix) |
| max_jobs_per_vehicle | – | – | Default: jobs divided evenly, rounded up |
| vehicles | array | yes | Vehicles as {name, lat, lon} (or {name}) |
No output schema declared.
No examples provided.
car_history Privi Car: signed vehicle history report ~136
The full signed history for a buyer, lender, insurer or the owner: every record, chain check, odometer timeline with rollback flags, accidents on record, service due, and cost of ownership. Private by default: the owner opens it with the owner_key or hands a buyer a 'history' key from car_key_issue. Built from what the owner recorded; Privi does not inspect the vehicle.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | The owner_key, or a key token (pck_...) with the 'history' scope |
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_info Privi Car: what it does ~32
Privi Car in one call: the tools, record types, key scopes, size limits, prices and safety boundaries.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
car_key_check Privi Car: check a digital key ~80
Is this key valid right now for this scope? Returns allowed true/false with the reason (expired, revoked, not yet valid, wrong scope), the vehicle_id and the signed attestation to verify offline.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Optional scope the holder wants to use |
| token | string | yes | The key token (pck_...) |
No output schema declared.
No examples provided.
car_key_issue Privi Car: issue a digital key ~221
Issue a time-limited, scope-limited key for a driver, valet, shop or buyer, signed Ed25519 + ML-DSA-87. Returns a token (shown once) for the grantee. A 'history' key opens car_history. unlock / drive / trunk / valet / service keys are credentials for hardware that checks them with car_key_check; Privi Car itself never opens or starts a vehicle.
| Name | Type | Req | Description |
|---|---|---|---|
| grantee | string | yes | Who the key is for (stored only as a hash) |
| hours | number | – | How long the key lasts, in hours (default 24, up to 366 days) |
| not_before | string | – | Optional ISO 8601 start time; default now |
| owner_key | string | yes | The owner_key (carkey_...) returned by car_register |
| scopes | array | yes | One or more of: history, unlock, drive, trunk, valet, service |
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_key_revoke Privi Car: revoke a digital key ~85
Revoke a digital key at once. Every later car_key_check answers 'revoked'.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The key_id (ck_...) to revoke |
| owner_key | string | yes | The owner_key (carkey_...) returned by car_register |
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_record_add Privi Car: add a sealed record ~195
Append one entry to the vehicle's hash chain: an odometer reading, service, repair, inspection, trip (distance and time only), fuel, charge, accident, title change or note. Each entry is hashed with the one before it, so history cannot be edited quietly. An odometer reading lower than an earlier one is recorded and flagged as a rollback.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Any of: odometer, unit (km|mi), distance, duration_min, liters, kwh, cost_usd, summary, date (YYYY-MM-DD). No location. |
| owner_key | string | yes | The owner_key (carkey_...) returned by car_register |
| type | string | yes | odometer | service | repair | inspection | trip | fuel | charge | accident | title | note |
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_register Privi Car: register a vehicle (passport) ~186
Create a Vehicle Passport: a post-quantum signed (Ed25519 + ML-DSA-87) identity for one vehicle, with a public verification page. Returns the vehicle_id and an owner_key (shown once) that controls its records and digital keys. One passport per VIN.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Manufacturer, e.g. Ford |
| model | string | yes | Model, e.g. F-150 |
| powertrain | string | – | gas | diesel | hybrid | plug_in_hybrid | electric | hydrogen | other |
| service_interval_km | number | – | Service every this many km (default 10000) |
| service_interval_months | integer | – | Service at least every this many months (default 12) |
| vin | string | – | Optional VIN; stored only as a fingerprint |
| year | integer | yes | Model year |
No output schema declared.
No examples provided.
car_route Privi Car: best route for a list of stops ~161
Order the stops for the shortest trip. The exact best order is proven classically (Held-Karp); with five stops or fewer the same problem also runs as a QUBO on the CVaR-QAOA quantum simulator, and the signed receipt shows both. Returns the order, distance, and how much it saves over the order given. Uses straight-line distance unless you pass distances_km. Stops are not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| distances_km | – | – | Optional n x n road distances or minutes; overrides straight-line distance |
| round_trip | boolean | – | Return to the start at the end (default true) |
| stops | array | yes | 2-12 stops as {name, lat, lon}; the first is the start |
No output schema declared.
No examples provided.
car_smartcar_sync Privi Car: import Smartcar mileage (pilot) ~112
Read mileage from the server-enrolled Smartcar vehicle. Requires the passport owner key, matching VIN and current Smartcar consent. Simulated data never writes real vehicle history. No location or vehicle commands. No recurring polling.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | – | Explicit consent for this one-time Smartcar mileage import |
| owner_key | string | yes | The owner_key (carkey_...) returned by car_register |
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_verify Privi Car: verify a vehicle's record chain ~62
Recompute the vehicle's hash chain: is it intact, how many records, how many odometer rollback flags, and the current head hash. Shows no record contents.
| Name | Type | Req | Description |
|---|---|---|---|
| vehicle | string | yes | vehicle_id (car_...) or the 17-character VIN |
No output schema declared.
No examples provided.
car_vin_check Privi Car: check a VIN ~82
Validate a VIN's format and its check digit (position 9, required in North America) and return the fingerprint Privi Car stores in place of the VIN. Catches typos and many made-up VINs. It does not look the vehicle up in any outside database.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | 17-character vehicle identification number |
No output schema declared.
No examples provided.
dreamscape_jobs Dream Scape: jobs ~114
Your Dream Scape's recent jobs, or one job with its full result. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | – | – | One job in full; omit for the recent list |
| limit | integer | – | – |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
| scape_id | string | yes | Your Dream Scape id |
| scape_key | string | yes | Its key |
No output schema declared.
No examples provided.
dreamscape_open Dream Scape: open a workspace ~104
Open a private Dream Scape: your own quantum environment that keeps every job and result. Returns scape_id and scape_key (shown once; keep it). Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A name for your workspace, e.g. 'Plant 2 scheduling' |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
No output schema declared.
No examples provided.
dreamscape_submit Dream Scape: run a job ~182
Run a quantum job in your Dream Scape through Dream Weaver and keep the result there. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Problem data (see quantum_problems) |
| deadline_s | number | – | – |
| fanout | integer | – | – |
| hedge_ms | integer | – | – |
| layers | integer | – | – |
| mode | string | – | first or best |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo |
| scape_id | string | yes | Your Dream Scape id (scape_...) |
| scape_key | string | yes | Its key (dsk_...) |
| shots | integer | – | – |
No output schema declared.
No examples provided.
dreamweaver_run Dream Weaver: race a quantum job across realms ~278
Run one quantum optimization on several realms at once and return the winning answer, every realm's timing, and a post-quantum signed attestation (Ed25519 + ML-DSA-87) anchored on chain. 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 |
| deadline_s | number | – | Give up after this many seconds (1-120) |
| fanout | integer | – | How many realms to use (1-8), fastest first |
| hedge_ms | integer | – | first mode: start the top realm alone, add the others after this many ms (or as soon as one fails). 0 = all at once |
| layers | integer | – | QAOA depth p (1-4) |
| mode | string | – | first = fastest valid answer wins; best = best answer by the deadline |
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| realms | – | – | Only these realm_ids (from privilege_directory) |
| shots | integer | – | Measurements (1-100000) |
No output schema declared.
No examples provided.
genius_stablecoin_check GENIUS Act stablecoin check ~174
Before accepting, paying with or listing a stablecoin: who issues it, what GENIUS Act license status has been recorded (with the regulator's source), and whether its latest monthly reserve report is sealed, current, examined, CEO/CFO-certified, 1:1 and matched to on-chain supply. Returns pass / pass_reserves_license_pending / caution / reject / unknown. The DASP rule (no non-permitted stablecoins for U.S. persons) starts 2028-07-18. Paid per call via x402 when payments are on (see quantum_pricing). Evidence, not a legal determination.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The stablecoin's token contract address (0x...) |
| chain | string | yes | base | ethereum | arbitrum | optimism | polygon |
No output schema declared.
No examples provided.
inspector_check Privi Inspector: check an agent's credential ~177
For any service: put the Privi Inspector in front of your own tools. Send the credential an agent gave you; get allowed or intercepted with reasons (unknown, revoked, uncertified, outdated, level, signature, replay). The nonce is consumed so the credential cannot be reused. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent's Quantum Agent id |
| min_level | – | – | Level you require: enrolled, quantum_aware, quantum_safe_identity, quantum_agent, quantum_agent_plus |
| nonce | string | yes | The nonce it signed |
| signature | string | yes | Its base64 ML-DSA signature over 'privi-inspector:v1:<agent_id>:<ts>:<nonce>' |
| ts | integer | yes | The unix time it signed |
No output schema declared.
No examples provided.
inspector_grade Privi Inspector: an agent's grade ~100
An agent's Privi trust grade (A+ to F, 0-100): quantum level, passkey approval by a verified human, ID verification, current certificate, key strength and clean record, minus penalties for revocation and impersonation. Shows what is missing and what the quantum realm requires. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | A Quantum Agent id |
No output schema declared.
No examples provided.
inspector_pass Privi Inspector: get a pass ~158
Pass the Privi Inspector checkpoint and get a one-hour pass into the quantum realm (Dream Weaver, Dream Scape). Intercepted if the agent is unknown, revoked, uncertified, outdated, below the required level, or the signature is wrong, stale or replayed; the answer says exactly what to fix.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your Quantum Agent id (qagent_...) |
| nonce | string | yes | A new random string, 16-64 letters, digits, _ or - |
| signature | string | yes | Base64 ML-DSA signature over 'privi-inspector:v1:<agent_id>:<ts>:<nonce>' (empty context) |
| ts | integer | yes | Current unix time in seconds |
No output schema declared.
No examples provided.
inspector_patrol Privi Inspector: run a patrol now ~51
Re-check every enrolled agent now and rebuild the watchlist (also runs automatically every hour). At most once every 5 minutes. Paid per call via x402 when payments are on (see quantum_pricing).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspector_report Privi Inspector: report ~56
What the checkpoint did: inspections, interceptions by reason, the latest interceptions, and the policy in force. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window |
No output schema declared.
No examples provided.
inspector_status Privi Inspector: would this agent pass? ~74
Whether an agent would pass the checkpoint right now and why not: revoked, certificate missing or outdated, level, key, and forged-signature attempts against it in the last hour. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | A Quantum Agent id |
No output schema declared.
No examples provided.
inspector_watchlist Privi Inspector: watchlist ~69
Agents the Inspector's patrol found revoked, outdated, expiring, never certified, using a weak key, or being impersonated (repeated forged signatures against them). Block them or demand a fresh inspector_check. Paid per call via x402 when payments are on (see quantum_pricing).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pqc_certificate_check Check certificates for quantum risk ~85
Read certificates and report, for each one, the key algorithm, whether a quantum computer could break it, when it expires, and whether it outlives the federal post-quantum dates. Nothing is contacted; the certificates are not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| pem | string | yes | One or more X.509 certificates in PEM form (a full chain is fine) |
No output schema declared.
No examples provided.
pqc_crypto_inventory Crypto inventory (CBOM) for a company ~290
Point Privi at a company's domains and GitHub repositories and get one cryptographic bill of materials: every algorithm quantum computers will break, where it is, a prioritized migration plan with dates, a CycloneDX 1.6 CBOM and a public report page, signed with ML-DSA-87 and anchored on chain. Repos are scanned in memory and not kept. Paid per call via x402 when payments are on (see quantum_pricing); failed calls are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | – | – | Known cryptographic assets (same shape as pqc_readiness_package) |
| domains | – | – | Public hostnames to test live for TLS 1.3 and hybrid post-quantum key exchange (up to 20) |
| files | – | – | Extra code or config files: [{name, content}] (up to 50 files, 1 MB) |
| long_lived_data | boolean | – | Do these systems protect data that must stay secret past 2030? Raises priority (harvest now, decrypt later) |
| organization | string | yes | Company or agency name |
| profile | string | – | company (NIST IR 8547 dates) | agency | contractor | nss_vendor |
| repos | – | – | Public GitHub repositories to scan, e.g. ['https://github.com/acme/api', 'acme/web'] (up to 5) |
No output schema declared.
No examples provided.
pqc_endpoint_check Check public endpoints for post-quantum TLS ~139
Test live public sites and services for TLS 1.3 and hybrid post-quantum key exchange (X25519MLKEM768, FIPS 203), the protection against 'harvest now, decrypt later'. Sends two TLS hellos per endpoint and no data. Returns a status and fix per endpoint plus CBOM-ready assets for pqc_readiness_package. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | Public hostnames or URLs (up to 20), optionally with a TLS port, e.g. ['www.irs.gov', 'login.gov:443'] |
No output schema declared.
No examples provided.
pqc_federal_deadlines Federal post-quantum deadlines ~80
The U.S. federal post-quantum timeline (EO 14409, OMB M-26-15, NIST IR 8547 draft, NSA CNSA 2.0), the approved replacement algorithms, and links to the sources. 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.
pqc_harvest_risk Harvest-now-decrypt-later risk ~179
Which of your data is exposed to "record now, decrypt later" attacks, under each planning scenario, and what to migrate first. Uses Mosca's inequality. Nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | yes | Kinds of data you send or store, each {"name": "patient records", "secrecy_years": 25, "protected_by": "RSA-2048"}. protected_by may be e.g. RSA-2048, ECDH P-256, X25519, ML-KEM-768, AES-256 |
| migration_years | number | yes | Years until your move to post-quantum encryption is finished |
| quantum_years | – | – | Planning scenarios for when today's key exchange can be broken. Default 2030, 2035, 2040 |
No output schema declared.
No examples provided.
pqc_readiness_package Post-quantum readiness package (government) ~411
Build a signed post-quantum readiness package: prioritized migration list with the federal deadline for each asset (EO 14409, OMB M-26-15, NIST IR 8547 draft, CNSA 2.0), the nine M-26-15 plan elements marked as evidence or gaps, and a CycloneDX 1.6 CBOM. Signed with ML-DSA-87, anchored on chain, public report URL. Paid per call via x402 when payments are on (see quantum_pricing); failed calls are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | – | – | Cryptographic assets: [{system, asset, algorithm, usage (key_establishment|signature|encryption|tls|ssh|vpn|code_signing|certificate|hash|other), protocol (e.g. 'TLS 1.2'), impact (high|moderate|low)… |
| endpoints | – | – | Public hostnames to check live for TLS 1.3 and hybrid post-quantum key exchange (up to 20), e.g. ['www.agency.gov'] |
| files | – | – | Code or config files to scan: [{name, content}] (up to 50 files, 1 MB) |
| hva | boolean | – | Is that system a High Value Asset (M-19-03)? |
| impact | string | – | FIPS 199 impact of that system: high | moderate | low |
| organization | string | yes | Agency, office or company name |
| pqc_lead | string | – | Name of the PQC Migration Lead (M-26-15 governance) |
| profile | string | – | agency (OMB M-26-15) | contractor (EO 14409 FAR items) | nss_vendor (NSA CNSA 2.0) |
| system_name | string | – | System the scanned files belong to |
No output schema declared.
No examples provided.
pqc_scan_code Scan code for quantum-vulnerable crypto ~96
Find RSA, elliptic-curve, Diffie-Hellman, DSA, weak hashes and 128-bit ciphers that quantum computers break or weaken; returns a 0-100 readiness score and a fix per finding. Nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code or config text to scan (max 200 KB) |
| filename | string | – | Optional file name, used in the report |
No output schema declared.
No examples provided.
pqc_size_impact Post-quantum size impact ~273
How many more bytes each handshake or signature costs after switching to a post-quantum algorithm, and the added traffic per day and year. Sizes come from FIPS 203, 204 and 205.
| Name | Type | Req | Description |
|---|---|---|---|
| current | string | yes | Today's algorithm. Key exchange: x25519, p-256, p-384, ml-kem-512, ml-kem-768, ml-kem-1024, x25519mlkem768, secp256r1mlkem768. Signature: ed25519, ecdsa-p256, ecdsa-p384, rsa-2048, rsa-3072, rsa-4096… |
| keys_per_operation | integer | – | Public keys sent per operation |
| kind | string | yes | key-exchange or signature |
| per_day | integer | – | Handshakes or signed operations per day |
| signatures_per_operation | integer | – | Signatures sent per operation (a TLS handshake with a two-certificate chain sends about 3) |
| target | string | yes | The algorithm you plan to move to (same lists) |
No output schema declared.
No examples provided.
pqc_supplier_score Score a supplier's post-quantum readiness ~135
Send a supplier Privi's ten post-quantum questions, then score the answers 0-100 with a letter grade and a ranked list of gaps. The scorecard is signed (Ed25519 + ML-DSA-87) so the supplier can show it to other customers. Call with no arguments to get the questions.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | – | – | Question id -> yes | partial | planned | no |
| evidence | – | – | Optional: question id -> SHA-256 fingerprint of the supplier's evidence document |
| supplier | – | – | Supplier's company name. Omit (with answers) to get the questionnaire |
No output schema declared.
No examples provided.
privilege_benchmark Privilege: benchmark the realms ~90
Run the standard 8-qubit benchmark on every active realm at once and update Privilege's speed rankings. At most once every 2 minutes for everyone. Requires a Privi pass. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| privi_pass | – | – | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
No output schema declared.
No examples provided.
privilege_directory Privilege: quantum realm directory ~67
Every quantum realm Privi can run a job on (engines on this server and other Privi Quantum nodes), ranked by expected time to the proven optimum, with latency, optimum rate, wins and status. Paid per call via x402 when payments are on (see quantum_pricing).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qagent_challenge Quantum Agent: get a signing challenge (Q2) ~53
Get a one-time message to sign with your ML-DSA private key (valid 10 minutes).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
No output schema declared.
No examples provided.
qagent_directory Quantum Agent Directory ~102
Look up agents that upgraded to quantum agents: level, operator, post-quantum key fingerprint and certificate. Use it before trusting or paying another agent. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| level | – | – | Only this level: quantum_agent_plus, quantum_agent, quantum_safe_identity, quantum_aware, enrolled |
| limit | integer | – | – |
| query | string | – | Search by agent or operator name |
No output schema declared.
No examples provided.
qagent_enroll Quantum Agent: enroll ~161
Join the Quantum Agent Accelerator. Returns agent_id and agent_token (shown once; keep it) and your upgrade plan. Your public key goes in the directory so other agents can verify what you sign. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| homepage | string | – | Optional https:// page about the agent |
| listed | boolean | – | Show this agent in the public Quantum Agent Directory |
| name | string | yes | Your agent's name |
| operator | string | yes | The company or person accountable for this agent |
| public_key | string | yes | Base64 of your raw ML-DSA-44/65/87 public key (FIPS 204). accelerator_info shows how to make one |
No output schema declared.
No examples provided.
qagent_human_request Quantum Agent: ask your human to approve you ~103
Get a one-time link (valid 30 minutes) for the person accountable for this agent. They open it, approve the agent with a passkey (Face ID, Touch ID, Windows Hello or screen lock; the biometric never leaves their device) and verify a government ID with a live selfie. Both are required for the quantum realm.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
No output schema declared.
No examples provided.
qagent_prove Quantum Agent: prove your post-quantum key (Q2) ~87
Send the signed challenge. A valid signature proves you hold the key in the directory: step Q2.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
| challenge_id | string | yes | From qagent_challenge |
| signature | string | yes | Base64 ML-DSA signature over the challenge message (empty context) |
No output schema declared.
No examples provided.
qagent_quantum_proof Quantum Agent: prove your quantum run (Q4) ~70
Complete step Q4 with the signed result of your assigned quantum job.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
| attestation_id | string | yes | The attestation id (qa_...) from your Dream Weaver run |
No output schema declared.
No examples provided.
qagent_quantum_task Quantum Agent: get your quantum task (Q4) ~66
Your assigned quantum job. Run it exactly with dreamweaver_run or dreamscape_submit, then send the attestation id to qagent_quantum_proof.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
No output schema declared.
No examples provided.
qagent_scan Quantum Agent: scan (Q1 code, Q3 endpoints) ~130
Q1: scan your code for quantum-vulnerable cryptography (passing means you ran the scan; the score and findings tell you what to fix). Q3: check that every public endpoint you run negotiates X25519MLKEM768.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent_id (qagent_...) |
| agent_token | string | yes | Your agent_token |
| code | – | – | Your agent's code or config (max 200 KB) for Q1 |
| endpoints | – | – | Your public hostnames for Q3 (all must use hybrid post-quantum TLS) |
No output schema declared.
No examples provided.
qagent_status Quantum Agent: profile ~60
One agent's public profile: level, steps passed, post-quantum public key, certificate. Paid per call via x402 when payments are on (see quantum_pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | An agent_id (qagent_...) |
No output schema declared.
No examples provided.
qagent_verify Quantum Agent: verify a signed message ~79
Check that a message really came from this agent's enrolled post-quantum key, and see its level. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent that claims to have signed |
| message | string | yes | The exact message |
| signature | string | yes | Base64 ML-DSA signature (empty context) |
No output schema declared.
No examples provided.
quantum_advantage_receipt Quantum Advantage Receipt ~191
Race the quantum answer against classical baselines (exhaustive search = proven optimum, and simulated annealing) on the same problem and seal the result as a signed, chain-anchored Quantum Advantage Receipt: answer quality and time for each side and a verdict (quantum_won / classical_won / tie), published whichever side wins. For a real-hardware receipt use quantum_run_hardware. Paid per call via x402 when payments are on (see quantum_pricing); failed calls are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Problem data in the shape quantum_problems describes |
| layers | integer | – | QAOA depth p (1-4) |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| shots | integer | – | Measurements from the trained circuit (1-100000) |
No output schema declared.
No examples provided.
quantum_backends Quantum hardware backends ~65
Every quantum backend this server can route to (local simulator, IonQ, IBM Quantum, Amazon Braket), whether it is usable now, its estimated price, measured turnaround, and the hardware budget. 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.
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.