Privi Quantum Ledger
REMOTE · PRIVI-LEDGER.ONRENDER.COM
Quantum-sealed audit logs for AI agents (ML-DSA-87, SHA3-512), plus Privi Guard and trust passports.
Available components
Last scanned (16 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 (passport_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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 11762 tokens (~97/item across 121 items; 121 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
- 98% of tool parameters carry a description.Partial
- Structured output schemas are declared (7% 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 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 122 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 28 Oct 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.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “seal_revoke”, which the server declares destructive security
- New tool “supplier_cert_revoke”, which the server declares destructive security
- Schema quality: 9472 → 11762 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.12.0 → 0.12.1 functional
- Server version: 0.10.1 → 0.12.0 functional
- New tool “ai_act_check” functional
- New tool “ai_act_export” functional
- New tool “ai_act_register” functional
- New tool “ai_act_system_save” functional
- New tool “ai_act_verify_export” functional
- New tool “qledger_block” functional
- New tool “qledger_entry_proof” functional
- New tool “qledger_seal” functional
- New tool “qledger_status” functional
- New tool “qledger_verify_chain” functional
- New tool “seal_content” functional
- New tool “seal_list” functional
- New tool “seal_verify” functional
- New tool “supplier_cert_verify” functional
- New tool “supplier_certs” functional
- New tool “supplier_proof_decide” functional
- New tool “supplier_proof_inbox” functional
- New tool “supplier_proof_submit” functional
- New tool “supplier_requirement_create” functional
- New tool “supplier_requirement_get” functional
- 26 Oct 26 64
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 5 Nov 2026 · Probed https://privi-ledger.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 | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| 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-ledger.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-ledger.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://privi-ledger.onrender.com/mcp | HTTPS enforced | 301 | https://privi-ledger.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 →
scan_owner_listing Show or hide your server's listing ~62
Verified owners only: hide the server from the directory (opt-out) or show it again. History already in the transparency log cannot be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| listed | boolean | yes | – |
| server | string | yes | mcp_... id or endpoint URL |
No output schema declared.
No examples provided.
scan_rescan Rescan an MCP server now ~50
Probe the server immediately instead of waiting for the next crawl (every ~6 hours). For the verified owner or Pro organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | mcp_... id or endpoint URL |
No output schema declared.
No examples provided.
scan_search Search the MCP trust registry ~125
Search Privi Scan, the public directory of remote MCP servers from the official MCP Registry, each with a safety grade, verdict, tool count and change history. Use it to find a trustworthy server for a job. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| grade | string | – | Only this grade: A, B, C, D or F |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | Words to match in name, description or URL; empty lists everything |
| sort | string | – | name, score, risk, changed or new |
Structured output declared, but exposes no named fields.
No examples provided.
scan_server Privi Scan: one server in full ~85
Full report for one MCP server: every tool definition with its hash, all findings with evidence, the change history (what was added, removed or modified, and when) and the transparency-log proof. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| include_history | boolean | – | – |
| server_id | string | yes | mcp_... id from scan_search or mcp_server_check, or the endpoint URL |
No output schema declared.
No examples provided.
scan_stats Privi Scan: totals ~37
How many MCP servers Privi Scan tracks, by status and grade, tools indexed, changes recorded and how to verify the evidence. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
scan_unwatch Stop watching an MCP server ~37
Remove a server from your watchlist. Needs the org key.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | mcp_... id or endpoint URL |
No output schema declared.
No examples provided.
scan_watch Watch an MCP server (pin its tools) ~95
Pin the server's current tools as approved and get a real-time event on your private Live 'org' channel the moment they change, a risk appears or the server goes down. Free plan: 3 servers; Pro: 500. Needs the org key.
| Name | Type | Req | Description |
|---|---|---|---|
| repin | boolean | – | Pin the current tools_hash as approved (default true) |
| server | string | yes | mcp_... id or endpoint URL |
No output schema declared.
No examples provided.
scan_watchlist Your watched MCP servers ~34
Your watched servers with their pinned tools_hash and whether each has drifted since you pinned it. Needs the org key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seal_content Content Seal: seal files or text ~150
Seal content your company publishes (documents, images, video, press releases, invoices, AI output) with who made it and whether AI was involved. Each seal is anchored on chain; anyone can check a file for free at the returned verify_url or with seal_verify. Counts toward your plan's monthly entries. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 1-50 items: {sha256: '<64-hex of the file>' (or text: 'exact text'), origin: human|ai_assisted|ai_edited|ai_generated, ai_tool (required unless human), title, author, media_type, note}. Only the fing… |
No output schema declared.
No examples provided.
seal_list Content Seal: your seals ~31
Your most recent content seals. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 1-200 |
No output schema declared.
No examples provided.
seal_revoke Content Seal: revoke a seal ~59
Withdraw one of your seals (e.g. sealed by mistake). Checks then show it as revoked. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Why it is revoked |
| seal_id | string | yes | Seal ID (seal_...) |
No output schema declared.
No examples provided.
seal_verify Content Seal: check a file ~77
Is this exact file or text sealed, by whom, since when, and did they declare AI involvement? Any change to the content (one pixel, one character) means no match. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | – | – | SHA-256 (64 hex) of the file |
| text | – | – | Or the exact text |
No output schema declared.
No examples provided.
supplier_cert_revoke Supplier Proof: revoke a certificate ~60
Revoke a certificate you issued (as the buyer). Verification shows it as revoked at once. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| cert_id | string | yes | Certificate ID (spc_...) |
| reason | string | yes | Why it is revoked |
No output schema declared.
No examples provided.
supplier_cert_verify Supplier Proof: verify a certificate ~90
Check a Privi supplier certificate: untampered, not revoked, not expired, which buyer approved which supplier, and (optionally) whether a document is one it covers. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| cert_id | string | yes | Certificate ID (spc_...) |
| document_sha256 | – | – | Optional: SHA-256 of a document to check it is the one the certificate covers |
No output schema declared.
No examples provided.
supplier_certs Supplier Proof: your certificates ~28
Certificates you issued (as buyer) or hold (as supplier). Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
supplier_proof_decide Supplier Proof: approve or reject ~99
Approve a supplier's proof (issues a certificate naming both companies and the evidence fingerprints, sealed on chain, with a public verify page and badge) or reject it with a reason. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true issues the certificate; false rejects |
| reason | string | – | Required when rejecting, so the supplier can fix it |
| sub_id | string | yes | Submission ID (sub_...) |
No output schema declared.
No examples provided.
supplier_proof_inbox Supplier Proof: inbox ~43
Supplier submissions waiting for your decision (as the buyer). Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | pending | approved | rejected | superseded |
No output schema declared.
No examples provided.
supplier_proof_submit Supplier Proof: submit proof to a buyer ~121
Answer a buyer's supplier requirement with fingerprints of your evidence documents. The buyer reviews and, if approved, Privi issues a certificate sealed on chain. Requires your organization API key (sign up free with ledger_signup).
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | object | yes | One entry per requirement item: {item_key: {sha256: '<64-hex of the document>', note: '...', valid_until: 'YYYY-MM-DD'}}. Only fingerprints are sent; keep the documents yourself. |
| req_id | string | yes | The buyer's requirement ID (req_...) |
No output schema declared.
No examples provided.
supplier_requirement_create Supplier Proof: require proof from suppliers ~155
Publish a requirement your suppliers must meet. Share the returned invite_url with them: they answer it from their own Privi organization (free sign-up) and you approve or reject in supplier_proof_inbox. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | What each supplier must prove: [{key: 'iso_9001', label: 'ISO 9001 certificate', document_required: true}, {key: 'ai_act_register', label: 'Sealed Privi AI Act register'}]. 1-30 items. |
| title | string | yes | e.g. 'Approved supplier 2027' |
| valid_days | integer | – | How long an approved certificate lasts (1-1095 days) |
No output schema declared.
No examples provided.
supplier_requirement_get Supplier Proof: view a requirement ~37
See what a buyer requires of its suppliers. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| req_id | string | yes | Requirement ID (req_...) |
No output schema declared.
No examples provided.
trust_events Trust feed: recent events ~103
The latest trust-change events: passports issued, revoked or re-scored, wallets bound or unbound, mandates activated or revoked, transparency-log heads anchored. Without a Pro key the feed is delayed (see live_info); use the WebSocket or SSE stream for real time. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Only events about this 0x wallet |
| limit | integer | – | 1-200 |
| passport_id | – | – | Only events about this passport |
No output schema declared.
No examples provided.
How do I install the Privi Quantum Ledger MCP server?
Privi Quantum Ledger is a hosted endpoint at https://privi-ledger.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-ledger.onrender.com
claude mcp add --transport http canoydario847-cloud-privi-ledger 'https://privi-ledger.onrender.com/mcp'
What is the Privi Quantum Ledger MCP server?
Privi Quantum Ledger is an MCP server listed in the public MCP registry as io.github.canoydario847-cloud/privi-ledger. Quantum-sealed audit logs for AI agents (ML-DSA-87, SHA3-512), plus Privi Guard and trust passports. This page covers its hosted endpoint (https://privi-ledger.onrender.com/mcp).
Is the Privi Quantum Ledger MCP server safe to use?
Privi Quantum Ledger scores 68 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 Ledger MCP server expose?
Privi Quantum Ledger exposes 121 tools: privi_token_market, ledger_pricing, ledger_check_receipt, ledger_audit_stream, ledger_record_action, and 116 more. Their descriptions and schemas cost roughly 10,443 tokens of context every time the server is loaded.
Does the Privi Quantum Ledger MCP server require authentication?
No. We connected to Privi Quantum Ledger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Privi Quantum Ledger MCP server still maintained?
Privi Quantum Ledger is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Privi Quantum Ledger MCP server?
VerifyMCP ran 13 checks on Privi Quantum Ledger, 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.