MCP server for Japanese labor and social insurance law — e-Gov API, MHLW rulings, JAISH safety and health rulings
Nothing to run from here
Privi Quantum is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
49
tools declared
remote
at its publisher
—
calls last 7d
What it does
Quantum on IonQ/IBM/Braket: spending mandates, signed benchmarks, paid PQC CBOM, advantage receipts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http privi-quantum-mcp https://privi-quantum.onrender.com/mcp
# 2 — ask your agent for something these tools do
# quantum_status, quantum_pricing, quantum_problems and 46 more
Privi Quantum costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CCAll 5 servers
canoydario847-cloud5 servers
5 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http privi-quantum-mcp https://privi-quantum.onrender.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
49 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
What this server runs: algorithm, qubit limit, quantum backends, signing keys, and anchoring.
No parameter schema on file.
Which tools are paid, their price per call, how to pay (x402: USDC on Base, or the PRIVI token), and the payout wallet. Everything else on this server is free. Failed calls are never charged.
No parameter schema on file.
The ready-made problems quantum_optimize accepts and the data each one needs, with an example.
No parameter schema on file.
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). Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| data | object | yes | Problem data in the shape quantum_problems describes |
| layers | integer | no | QAOA depth p (1-4). Deeper finds better answers more often but runs longer. |
| shots | integer | no | Measurements to sample from the trained circuit (1-100000) |
| include_qasm | boolean | no | Also return the trained circuit as OpenQASM 2.0 for real quantum hardware |
Check both post-quantum signatures, the body hash, and the on-chain anchor of a result. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attestation_id | no | An attestation id (qa_...) issued by this server | |
| attestation | no | Or a full attestation object (from GET /attestations/<id>) to check offline |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Source code or config text to scan (max 200 KB) |
| filename | string | no | Optional file name, used in the report |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization | string | yes | Agency, office or company name |
| assets | no | 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), | |
| files | no | Code or config files to scan: [{name, content}] (up to 50 files, 1 MB) | |
| profile | string | no | agency (OMB M-26-15) | contractor (EO 14409 FAR items) | nss_vendor (NSA CNSA 2.0) |
| pqc_lead | string | no | Name of the PQC Migration Lead (M-26-15 governance) |
| system_name | string | no | System the scanned files belong to |
| impact | string | no | FIPS 199 impact of that system: high | moderate | low |
| hva | boolean | no | Is that system a High Value Asset (M-19-03)? |
| endpoints | no | Public hostnames to check live for TLS 1.3 and hybrid post-quantum key exchange (up to 20), e.g. ['www.agency.gov'] |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoints | array | yes | Public hostnames or URLs (up to 20), optionally with a TLS port, e.g. ['www.irs.gov', 'login.gov:443'] |
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. Free.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| data | object | yes | Problem data in the shape quantum_problems describes |
| layers | integer | no | QAOA depth p (1-4) |
| shots | integer | no | Measurements from the trained circuit (1-100000) |
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. Free.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| data | object | yes | Problem data in the shape quantum_problems describes |
| backend | string | no | 'auto' or a backend id from quantum_backends (e.g. ionq:simulator, ionq:qpu.forte-1, ibm:ibm_brisbane) |
| policy | string | no | With backend='auto': cheapest | fastest | hardware (real QPUs only) |
| layers | integer | no | QAOA depth p (1-4) |
| shots | integer | no | Shots on the backend (1-10000) |
| max_cost_usd | no | Refuse if the estimated price is above this | |
| mandate_id | no | qm_... Quantum Mandate your human signed; required for any paid backend | |
| privi_pass | no | Your Privi pass (ppass_...); required with a mandate |
Status of a quantum hardware job; once done, the decision, measurement statistics, the signed attestation and the Quantum Advantage Receipt. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | hw_... id from quantum_run_hardware |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| budget_usd | number | yes | Total the agent may spend on paid quantum hardware under this mandate |
| purpose | string | yes | What the runs are for, in plain words (shown to the person who signs) |
| max_per_job_usd | no | Most one job may cost (default: the whole budget) | |
| backends | no | Allowed backend ids from quantum_backends (default: any paid backend) | |
| problems | no | Allowed problems (default: any) | |
| max_shots | integer | no | Most shots per job (1-10000) |
| days | integer | no | How long the mandate lasts once signed (1-365) |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
A Quantum Mandate's terms, status (draft, active, expired, revoked), spend, remaining budget and every charge and refund. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | qm_... id |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | qm_... id |
| problem | string | no | Problem you plan to run |
| backend | string | no | 'auto' or a backend id |
| policy | string | no | cheapest | fastest | hardware |
| shots | integer | no | — |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | qm_... id |
| reason | string | no | Why |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qasm | string | yes | OpenQASM 2.0 or 3.0 text, e.g. from Qiskit: qiskit.qasm2.dumps(circuit) or qiskit.qasm3.dumps(circuit) |
| backend | string | no | 'auto' or a backend id from quantum_backends (local, ionq:simulator, ionq:qpu.forte-1, ibm:<name>, braket:<name>) |
| policy | string | no | With backend='auto': cheapest | fastest | hardware (real QPUs only) |
| shots | integer | no | Shots (1-10000) |
| label | string | no | Optional short name for the run (kept in the sealed record) |
| max_cost_usd | no | Refuse if the estimated price is above this | |
| mandate_id | no | qm_... Quantum Mandate (required for paid backends) | |
| privi_pass | no | Your Privi pass (ppass_...); required with a mandate |
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_prici
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization | string | yes | Company or agency name |
| domains | no | Public hostnames to test live for TLS 1.3 and hybrid post-quantum key exchange (up to 20) | |
| repos | no | Public GitHub repositories to scan, e.g. ['https://github.com/acme/api', 'acme/web'] (up to 5) | |
| files | no | Extra code or config files: [{name, content}] (up to 50 files, 1 MB) | |
| assets | no | Known cryptographic assets (same shape as pqc_readiness_package) | |
| profile | string | no | company (NIST IR 8547 dates) | agency | contractor | nss_vendor |
| long_lived_data | boolean | no | Do these systems protect data that must stay secret past 2030? Raises priority (harvest now, decrypt later) |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| suite | string | no | X25519+ML-KEM-768 (default) | X25519+ML-KEM-1024 (CNSA 2.0 KEM level) |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| public_key | object | yes | Recipient public key from vault_keygen |
| text | no | Text to protect | |
| data_base64 | no | Or bytes to protect, base64 (up to 5 MB) | |
| label | string | no | What this is, e.g. 'supplier contract 2026' (kept in the envelope and receipt) |
Decrypt a Privi Vault envelope. Nothing is stored; for sensitive data prefer opening locally with python -m privi_quantum.vault open. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelope | object | yes | A Privi Vault envelope |
| private_key | object | yes | The recipient private key from vault_keygen |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| envelope | no | An envelope sealed locally (checked for structure; nothing is decrypted) | |
| envelope_sha256 | no | Or only the envelope's SHA-256, so the envelope never leaves your machine | |
| label | string | no | What this protects |
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. Free.
No parameter schema on file.
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo (see quantum_problems) |
| data | object | yes | Problem data in the shape quantum_problems describes |
| mode | string | no | first = fastest valid answer wins; best = best answer by the deadline |
| fanout | integer | no | How many realms to use (1-8), fastest first |
| hedge_ms | integer | no | 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 | no | QAOA depth p (1-4) |
| shots | integer | no | Measurements (1-100000) |
| deadline_s | number | no | Give up after this many seconds (1-120) |
| realms | no | Only these realm_ids (from privilege_directory) | |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
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). Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | A name for your workspace, e.g. 'Plant 2 scheduling' |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
Run a quantum job in your Dream Scape through Dream Weaver and keep the result there. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scape_id | string | yes | Your Dream Scape id (scape_...) |
| scape_key | string | yes | Its key (dsk_...) |
| problem | string | yes | balance_lines | select_lots | split_conflicts | qubo |
| data | object | yes | Problem data (see quantum_problems) |
| mode | string | no | first or best |
| fanout | integer | no | — |
| hedge_ms | integer | no | — |
| layers | integer | no | — |
| shots | integer | no | — |
| deadline_s | number | no | — |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
Your Dream Scape's recent jobs, or one job with its full result. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scape_id | string | yes | Your Dream Scape id |
| scape_key | string | yes | Its key |
| job_id | no | One job in full; omit for the recent list | |
| limit | integer | no | — |
| privi_pass | no | Your Privi pass (ppass_...) from inspector_pass; the quantum realm requires one |
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. Free.
No parameter schema on file.
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
| homepage | string | no | Optional https:// page about the agent |
| listed | boolean | no | Show this agent in the public Quantum Agent Directory |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your agent_id (qagent_...) |
| agent_token | string | yes | Your agent_token |
| code | no | Your agent's code or config (max 200 KB) for Q1 | |
| endpoints | no | Your public hostnames for Q3 (all must use hybrid post-quantum TLS) |
Get a one-time message to sign with your ML-DSA private key (valid 10 minutes).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
Send the signed challenge. A valid signature proves you hold the key in the directory: step Q2.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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) |
Your assigned quantum job. Run it exactly with dreamweaver_run or dreamscape_submit, then send the attestation id to qagent_quantum_proof.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
Complete step Q4 with the signed result of your assigned quantum job.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
Look up agents that upgraded to quantum agents: level, operator, post-quantum key fingerprint and certificate. Use it before trusting or paying another agent. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | no | Only this level: quantum_agent_plus, quantum_agent, quantum_safe_identity, quantum_aware, enrolled | |
| query | string | no | Search by agent or operator name |
| limit | integer | no | — |
One agent's public profile: level, steps passed, post-quantum public key, certificate. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | An agent_id (qagent_...) |
Check that a message really came from this agent's enrolled post-quantum key, and see its level. Free; no key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your Quantum Agent id (qagent_...) |
| ts | integer | yes | Current unix time in seconds |
| 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) |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | The agent's Quantum Agent id |
| ts | integer | yes | The unix time it signed |
| nonce | string | yes | The nonce it signed |
| signature | string | yes | Its base64 ML-DSA signature over 'privi-inspector:v1:<agent_id>:<ts>:<nonce>' |
| min_level | no | Level you require: enrolled, quantum_aware, quantum_safe_identity, quantum_agent, quantum_agent_plus |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | A Quantum Agent id |
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. Free.
No parameter schema on file.
What the checkpoint did: inspections, interceptions by reason, the latest interceptions, and the policy in force. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | Look-back window |
Re-check every enrolled agent now and rebuild the watchlist (also runs automatically every hour). At most once every 5 minutes. Free.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your agent_id |
| agent_token | string | yes | Your agent_token |
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. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | A Quantum Agent id |
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. Free.
No parameter schema on file.
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Privi Quantum or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.9.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest67dd7995001aec345a1b3fa6895380fd259754ae7a98507204b95e6c77a5556b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| quantum_status | no tags | |
| quantum_pricing | no tags | |
| quantum_problems | no tags | |
| quantum_optimize | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| quantum_verify | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pqc_scan_code | no tags | |
| pqc_readiness_package | state-write | state-write: declares readOnlyHint: false |
| pqc_endpoint_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pqc_federal_deadlines | no tags | |
| quantum_advantage_receipt | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| quantum_backends | no tags | |
| quantum_run_hardware | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| quantum_hardware_job | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| quantum_mandate_request | state-write | state-write: declares readOnlyHint: false |
| quantum_mandate_status | no tags | |
| quantum_mandate_check | no tags | |
| quantum_mandate_revoke | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| quantum_run_circuit | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pqc_crypto_inventory | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| vault_keygen | no tags | |
| vault_seal | state-write | state-write: declares readOnlyHint: false |
| vault_open | no tags | |
| vault_receipt | state-write | state-write: declares readOnlyHint: false |
| privilege_directory | no tags | |
| privilege_benchmark | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| dreamweaver_run | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| dreamscape_open | state-write | state-write: declares readOnlyHint: false |
| dreamscape_submit | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| dreamscape_jobs | no tags | |
| accelerator_info | no tags | |
| qagent_enroll | state-write | state-write: declares readOnlyHint: false |
| qagent_scan | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| qagent_challenge | state-write | state-write: declares readOnlyHint: false |
| qagent_prove | state-write | state-write: declares readOnlyHint: false |
| qagent_quantum_task | no tags | |
| qagent_quantum_proof | state-write | state-write: declares readOnlyHint: false |
| qagent_directory | no tags | |
| qagent_status | no tags | |
| qagent_verify | no tags | |
| inspector_pass | state-write | state-write: declares readOnlyHint: false |
| inspector_check | state-write | state-write: declares readOnlyHint: false |
| inspector_status | no tags | |
| inspector_watchlist | no tags | |
| inspector_report | no tags | |
| inspector_patrol | state-write | state-write: declares readOnlyHint: false |
| qagent_human_request | state-write | state-write: declares readOnlyHint: false |
| inspector_grade | no tags | |
| quantum_benchmarks | no tags | |
| quantum_leaderboard | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest67dd7995001aec34
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.9.0.
0.9.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Privi Quantum can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.