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 (15 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 →
ledger_handshake_accept Accept a handshake ~105
Accept a handshake addressed to your organization: records the same terms in your log, confirms it in the other company's log, and seals the matched pair on chain (Base). Requires your organization API key. Read the terms first with ledger_handshake_inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | Who is accepting on your side |
| handshake_id | string | yes | hs_... ID from the offer |
| stream_id | string | yes | Your stream to record it in |
No output schema declared.
No examples provided.
ledger_handshake_inbox Handshake inbox ~36
Handshakes sent to and from your organization, newest first, with their terms and status. Requires your organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_handshake_offer Offer a handshake ~236
Start a Privi Handshake: a two-sided record of a dealing with another company's agent (payment, data transfer, delivery, agreement). Recorded in your log now; when the other company accepts, both logs hold matching entries and the pair is sealed on chain (Base). Requires your organization API key; the other company must also use Privi Ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | One of: tool_call, data_access, data_change, payment, message, decision, approval, error, other |
| actor | string | yes | Who is acting on your side |
| counterparty_org_id | string | yes | org_id of the other company (must be on Privi Ledger) |
| details | – | – | Terms as structured data (amounts, quantities, dates) |
| expires_hours | number | – | Hours the other company has to respond |
| resource | string | – | Invoice, order, dataset, contract or other reference |
| stream_id | string | yes | Your stream to record it in, usually your agent's name |
| summary | string | yes | What is being agreed or done between the two companies |
No output schema declared.
No examples provided.
ledger_handshake_reject Reject a handshake ~65
Reject a handshake addressed to your organization; the other company's log records the rejection. Requires your organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| handshake_id | string | yes | hs_... ID from the offer |
| reason | string | – | Why it is rejected (shared with the other company) |
No output schema declared.
No examples provided.
ledger_handshake_verify Verify a handshake ~61
Public check of a handshake: both companies, status, whether both matching log entries still exist, and the on-chain seal. Never reveals the terms. Free; useful for disputes and audits.
| Name | Type | Req | Description |
|---|---|---|---|
| handshake_id | string | yes | hs_... handshake ID |
No output schema declared.
No examples provided.
ledger_inclusion_proof Inclusion proof ~87
Merkle audit path proving an entry is in Privi's append-only transparency log (RFC 9162). Verifiable offline against the signed tree head. Reveals no entry contents. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_hash | string | yes | 64-hex entry_hash (an action receipt) |
| tree_size | – | – | Prove against this signed tree head size; omit for latest |
No output schema declared.
No examples provided.
ledger_list_streams List streams ~24
List your organization's streams with entry counts. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_plan Plan and usage ~33
Your plan, entries used this month, the limit, and when a Pro plan renews. Requires your organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_pricing Ledger pricing ~27
List Privi Ledger tools, what each costs, and how to get an organization key.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ledger_read_stream Read a stream ~71
Read your organization's entries in a stream, oldest first, with an integrity check of the whole stream. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | Return entries after this sequence number |
| limit | integer | – | Max entries to return |
| stream_id | string | yes | Stream ID |
No output schema declared.
No examples provided.
ledger_record_action Record an agent action ~181
Append an action to the organization's tamper-evident log. Returns the entry with its entry_hash receipt. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | One of: tool_call, data_access, data_change, payment, message, decision, approval, error, other |
| actor | string | yes | Who acted: agent name, model, or user on whose behalf |
| details | – | – | Optional structured details (JSON object, under 16 KB) |
| outcome | string | – | One of: success, failure, pending, blocked |
| resource | string | – | What was acted on: URL, file, record ID, account |
| stream_id | string | yes | Stream to append to, usually the agent's name, e.g. 'billing-agent' |
| summary | string | yes | One-line description of what was done |
No output schema declared.
No examples provided.
ledger_report_pdf Compliance report PDF ~77
A finished PDF of a sealed compliance report, for auditors and customers. Returned as base64 (pdf_base64) and as an embedded PDF resource; also downloadable at /reports/<report_id>.pdf with the organization key. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | report_id returned by ledger_compliance_report |
No output schema declared.
No examples provided.
ledger_signup Sign up ~73
Create a Privi Ledger organization on the free plan and get its API key (shown once; store it). Free plan: up to the monthly entry limit, all tools included. Upgrade any time with ledger_upgrade_pro. No key needed to sign up.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_name | string | yes | Your company or project name |
No output schema declared.
No examples provided.
ledger_tree_head Signed tree head ~60
The latest signed tree head of Privi's transparency log: an RFC 9162 Merkle root over every entry ever recorded, signed with Ed25519 and ML-DSA-87, and periodically anchored on chain (Base). Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_upgrade_pro Upgrade to Pro ~51
Buy 30 days of Privi Ledger Pro (unlimited entries) for your organization, paid in USDC on Base via x402. Each call adds 30 days. Requires your organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_verify_report Verify a report ~75
Check that a compliance report is unaltered: recomputes its hash, confirms Privi Ledger issued it, and checks the anchor on chain (Base, until the Privi chain mainnet). Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| report | object | yes | The 'report' object exactly as received from ledger_compliance_report |
No output schema declared.
No examples provided.
live_info Privi Live: how to connect ~71
Real-time Privi: WebSocket and server-sent-event streams (trust changes, your own audit tail, approvals), a kill switch, human approvals, a metered MCP gateway and paid agent-to-agent rooms. Returns the endpoints, channels, frames and what each plan gets. Free; no key needed.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
live_kill Kill switch: stop an agent ~101
Stop an agent at once: mandate_spend, your gateways and your room messages are refused until live_resume. Takes effect on the next call, and is pushed to your live channel immediately. Audit logging keeps working. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Why (shown in your log and on your live channel) |
| stream_id | string | – | The agent (stream) to stop, or '*' for every agent in your organization |
No output schema declared.
No examples provided.
live_resume Kill switch: resume an agent ~39
Lift a kill switch set with live_kill. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| stream_id | string | – | The agent to resume, or '*' |
No output schema declared.
No examples provided.
live_status Live status ~35
Your kill switches, live-approval thresholds, pending approvals, gateways, rooms and usage this month. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandate_check Check a payment against a mandate ~127
For merchants, payment facilitators and counterparties: did a human authorize this AI agent to pay you this amount? Verifies the human's wallet signature, status, expiry, per-payment cap, remaining budget and payee list, and returns allow/deny with reasons plus a Privi-signed attestation. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string | yes | Payment amount in USDC |
| mandate_id | string | yes | mdt_... ID the agent presented |
| payee | string | yes | Who is being paid: your 0x address or domain |
No output schema declared.
No examples provided.
mandate_create Create a spending mandate ~232
Draft a Privi Mandate: the human's signed permission for your agent to spend, with a budget, per-payment cap, allowed payees and expiry. Returns sign_url: send it to the human, who reads the plain-English terms and signs once with their wallet (free, no transaction). Nothing can be spent until they sign. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_wallet | – | – | 0x wallet the agent pays from (optional) |
| days | integer | – | Days until the mandate expires (1-365) |
| max_per_payment_usdc | – | – | Cap per payment; defaults to the total |
| max_total_usdc | string | yes | Total budget in USDC, e.g. '250' |
| payees | – | – | Allowed payees (0x addresses or domains); omit for any |
| principal_wallet | string | yes | 0x wallet of the human who authorizes the spending |
| purpose | string | yes | What the agent may spend on, in plain words |
| stream_id | string | yes | The agent (stream) that will spend, e.g. 'shopping-agent' |
No output schema declared.
No examples provided.
mandate_get Get a mandate ~47
Public view of a mandate: terms, status, the human's signature, spent and remaining budget, and recent spends. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| mandate_id | string | yes | mdt_... ID |
No output schema declared.
No examples provided.
mandate_list List your mandates ~23
Your organization's mandates with status and remaining budget. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandate_revoke Revoke a mandate ~57
Stop an agent from spending under a mandate (the human can also revoke from the sign_url page). Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| mandate_id | string | yes | mdt_... ID |
| reason | string | – | Why |
No output schema declared.
No examples provided.
mandate_spend Spend under a mandate ~185
Call before each payment: checks the mandate and, if allowed, deducts the amount from the budget and records the payment in the agent's tamper-evident log. Refused payments are logged as blocked. Refused at once if the kill switch is on. Over the organization's live-approval threshold it returns approval_required with an approve_url for the human; call again with approval_id once they approve. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string | yes | Payment amount in USDC |
| approval_id | – | – | apr_... : the human's live approval, if this payment is over the agent's approval threshold |
| mandate_id | string | yes | mdt_... ID |
| payee | string | yes | Who is being paid: 0x address or domain |
| reference | string | – | Order, invoice or transaction reference |
No output schema declared.
No examples provided.
mcp_server_check Check an MCP server before connecting ~206
Free safety check for any remote MCP server, before an agent connects to it or after it was approved. Privi reads the server's tool list (it never calls a tool) and returns a verdict: ok, caution, danger (tool poisoning: hidden instructions, concealment from the user, requests for keys or private files, tool shadowing, invisible characters), changed (tools differ from expected_tools_hash), unverified (tools behind auth) or unreachable. Also returns the tools_hash to pin, a grade A-F and a link to the server's public history. Every first observation and change is recorded in Privi's on-chain-anchored transparency log. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_tools_hash | – | – | The tools_hash you approved earlier; Privi tells you if the tools changed since then (rug-pull check) |
| url | string | yes | The server's streamable-HTTP MCP endpoint, e.g. https://example.com/mcp |
No output schema declared.
No examples provided.
passport_gate Gate on a Privi Passport ~166
One-call allow/deny decision before transacting with another AI agent: verifies its Privi Passport and applies your minimums, returning the reasons. If you send your organization API key the decision is recorded in your own tamper-evident log as due-diligence evidence. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| min_grade | – | – | Minimum grade A-E (alternative to min_score) |
| min_score | integer | – | Minimum current score 0-1000 |
| passport_id | string | yes | pp_... ID presented by the other agent |
| purpose | string | – | What you are about to do with this counterparty (recorded in your log if you send your key) |
| require_anchored | boolean | – | Require the passport to be anchored on chain (Base) |
No output schema declared.
No examples provided.
passport_issue Issue a Privi Passport ~130
Issue a Privi Passport: a signed, on-chain-anchored trust credential for your agent or organization, scored 0-1000 (grade A-E) from verified history, integrity, anchoring, reliability, human oversight, compliance reports and confirmed handshakes. Show it to counterparties; they verify it free with passport_verify / passport_gate. Valid 30 days. Free on Pro/enterprise; free-plan organizations pay per passport via x402. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| stream_id | – | – | Issue for one agent (stream). Omit for the whole organization |
No output schema declared.
No examples provided.
passport_list List your passports ~28
Your organization's issued passports with score, grade, expiry and revocation. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
passport_revoke Revoke a passport ~63
Revoke one of your passports (e.g. an agent was retired or compromised). Verifiers see it immediately. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| passport_id | string | yes | pp_... ID |
| reason | string | – | Why (shown to verifiers) |
No output schema declared.
No examples provided.
passport_verify Verify a Privi Passport ~99
Check an AI agent's Privi Passport before trusting it: Privi signature, content unaltered, not expired or revoked, anchor on chain (Base), and a live re-score of the agent right now (so tampering after issue is caught). Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| passport | – | – | The 'passport' object exactly as issued |
| passport_id | – | – | pp_... ID, or omit and pass the passport document |
No output schema declared.
No examples provided.
privi_payment_options Privi: payment methods ~29
See existing USDC/x402 service billing and separately gated valueless PRVI_TEST development mode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
privi_test_payment_quote Privi: create a valueless test-payment quote ~48
Off-chain PRVI_TEST quote. Requires organization key and explicit test mode. Never takes money.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | Existing priced tool to model; NO service will be unlocked |
No output schema declared.
No examples provided.
privi_test_payment_simulate Privi: simulate a valueless test payment ~57
Consume a test quote once. Receipt is NOT payment, on-chain proof or entitlement.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgement | string | yes | Must equal VALUELESS TEST ONLY |
| quote_id | string | yes | Short-lived PRVI_TEST quote ID |
No output schema declared.
No examples provided.
privi_token_market PRIVI token market ~126
PRIVI on Base: price, how much PRIVI and USDC the Privi swap desk holds (so whether a swap can fill), any Uniswap v3 / Aerodrome pools, and optionally a swap quote. Every paid Privi tool also accepts PRIVI. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Amount to swap in (USDC for buy, PRIVI for sell), e.g. '25' |
| side | string | – | Optional swap quote: 'buy' (USDC -> PRIVI) or 'sell' (PRIVI -> USDC) |
Structured output declared, but exposes no named fields.
No examples provided.
qledger_block Quantum Ledger block ~41
One quantum-sealed block with its signatures, settlement on chain and a validity check. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Block height (0 = genesis) |
No output schema declared.
No examples provided.
qledger_entry_proof Quantum proof for an entry ~71
Prove an entry (by its receipt hash) is sealed in a quantum block: the block, its post-quantum signatures, its on-chain settlement and the Merkle inclusion proof. Reveals no entry contents. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_hash | string | yes | entry_hash from ledger_record_action |
No output schema declared.
No examples provided.
qledger_seal Seal a quantum block now ~47
Seal your newest entries into a quantum block now instead of waiting for the next scheduled block (every few minutes). Does nothing if no entries are waiting. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qledger_status Quantum Ledger status ~60
Privi Quantum Ledger: latest quantum-sealed block (SHA3-512, ML-DSA-87 + Ed25519), entries waiting for the next block, the Privi Foundation chain it is fused with, and signing keys. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qledger_verify_chain Verify the Quantum Ledger ~80
Verify the whole Quantum Ledger: SHA3-512 block hashes, hash links, both signatures on every block, and for recent blocks the log roots, entry roots and RFC 9162 consistency proofs. Free; anyone can run it.
| Name | Type | Req | Description |
|---|---|---|---|
| deep_last | integer | – | Re-derive log roots and consistency proofs for this many most recent blocks |
No output schema declared.
No examples provided.
room_close Rooms: close and seal ~70
Close a room and seal its transcript: the hash is signed (Ed25519 + ML-DSA-87), anchored on chain (Base) and written to both organizations' logs. Either party can close. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | rm_... ID |
No output schema declared.
No examples provided.
room_info Rooms: info ~47
Public facts about a room: parties, price, message count, head hash and its seal once closed. No message text. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | rm_... ID |
No output schema declared.
No examples provided.
room_list Rooms: list yours ~21
Rooms your organization owns or joined. Requires the organization API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
room_open Rooms: open a live room ~197
Open a live, hash-chained conversation room for two organizations' agents. Both connect over WebSocket (ws_url), authenticate with their API keys and talk in real time; closing the room seals the transcript on the Privi chain. Optionally charge per message, paid under the guest's human-signed Mandate. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty_org_id | – | – | org_... that may join; omit to get a one-time join_code instead |
| hours | integer | – | Hours the room stays open (1-168) |
| max_messages | integer | – | Message cap (2-10000) |
| payee | – | – | Who is paid for messages: 0x address or domain |
| price_per_message_usdc | – | – | Charge the guest this much per message (needs payee) |
| title | string | yes | What the room is for, e.g. 'Negotiate delivery of lot 4471' |
No output schema declared.
No examples provided.
room_transcript Rooms: transcript ~42
Every message in a room you are part of, with the chain check. Requires the organization API key.
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | rm_... ID |
No output schema declared.
No examples provided.
room_verify Rooms: verify a sealed transcript ~75
Check a closed room's seal (signature, on-chain anchor) and, if you pass the transcript, that it is complete and unaltered. Free; no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| messages | – | – | The transcript's 'messages' array exactly as room_transcript returned it |
| room_id | string | yes | rm_... ID |
No output schema declared.
No examples provided.
scan_changes Privi Scan: recent tool changes ~53
The latest MCP servers whose tool definitions changed after they were first observed (possible rug pulls), newest first. Subscribe to the Live channel 'scan' for these as they happen. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
scan_claim_start Claim your MCP server's listing ~90
Start proving you operate an MCP server listed in Privi Scan. Returns a token to publish at https://<your host>/.well-known/privi-scan.txt. Verified owners get an owner-verified badge, unlimited rescans, change alerts and control over the listing. Needs the org key (create_org is free).
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | mcp_... id or endpoint URL |
No output schema declared.
No examples provided.
scan_claim_verify Finish claiming your MCP server ~45
Check the token at /.well-known/privi-scan.txt and mark your organization as the verified owner.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | mcp_... id or endpoint URL |
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.