Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 68 Trust /100

Last scanned (2 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 categories)

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
Transport & Reachability100
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
Changelog

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.

Diagnostics

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. present 19718 13 Verified
onrender.com. absent 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
MCP tools · 121 exposed · ~10,443 tokens

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 →

Tool Tokens
ai_act_check ~73

What a customer's due-diligence or a regulator would flag today: prohibited practices, incomplete Article 5 screens, obligations already in force without evidence (critical), obligations due within 180 days (medium), upcoming high-risk duties, and high-risk systems with no recent log. Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ai_act_export ~57

Export your AI Act register as JSON to hand to customers, auditors or regulators, with its SHA-256 sealed on chain so anyone can prove it was not edited afterwards (check with ai_act_verify_export). Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ai_act_register ~45

Your EU AI Act register: each AI system's current record, tier and applicable obligations. Requires the organization API key.

NameTypeReqDescription
system_id––One system; omit for all

No output schema declared.

No examples provided.

ai_act_system_save ~512

Add or update an AI system in your company's EU AI Act register. Privi screens it against the Article 5 bans, classifies it (prohibited / high-risk / transparency / general-purpose / minimal), and lists the obligations that apply to your role with their dates. Every change is versioned and written to your tamper-evident 'ai-act' log. Requires the organization API key.

NameTypeReqDescription
actorstringyesWho is making the change (person or agent)
mergeboolean–Merge into the existing record (true) or replace it (false)
systemobjectyesAI system record. Required: system_id. Recommended: name, owner, role (provider|deployer|provider_and_deployer|importer|distributor), intended_purpose, used_in_eu, vendor_name. Risk flags: annex_iii_…

No output schema declared.

No examples provided.

ai_act_verify_export ~61

Check that an AI Act register a supplier or partner sent you is exactly what they exported from Privi, and return its on-chain seal. Free; no key needed.

NameTypeReqDescription
register_jsonstringyesThe exact register_json a company shared with you

No output schema declared.

No examples provided.

approval_cancel ~48

Withdraw an approval request (or revoke an approval not yet used). Your key cannot approve, only cancel. Requires the organization API key.

NameTypeReqDescription
approval_idstringyesapr_... ID

No output schema declared.

No examples provided.

approval_list ~36

Your organization's approval requests, newest first. Requires the organization API key.

NameTypeReqDescription
status––pending, approved, denied, expired or cancelled

No output schema declared.

No examples provided.

approval_policy_set ~94

Make mandate_spend pause for a human on large payments: any payment over the threshold creates an approval request that the mandate's principal must sign with their wallet before the agent can spend. Requires the organization API key.

NameTypeReqDescription
approve_over_usdc––Payments above this need a live human approval; omit to remove the rule
stream_idstringyesThe agent (stream), or '*' for all of them

No output schema declared.

No examples provided.

approval_request ~235

Ask a human to approve (or deny) an action. Returns approve_url for them: they read the request and sign with their wallet (free, no transaction). Your agent then calls approval_wait, or watches your live channel for approval.approved. Only the named wallet can decide; your API key can only cancel. Requires the organization API key.

NameTypeReqDescription
actionstringyesPlain-English action the human is approving, e.g. 'Wire 4,800 USDC to Acme for invoice 1042'
amount_usdc––Amount, if money is involved
approver_wallet––0x wallet of the human who decides (if no mandate_id)
mandate_id––mdt_... : the mandate's principal decides
payeestring–Payee address or domain, if money is involved
reasonstring–Why the agent wants to do this
referencestring–Invoice or order reference
stream_idstringyesThe agent asking
ttl_sinteger–Seconds the request stays open (60-86400)

No output schema declared.

No examples provided.

approval_status ~49

Status of an approval request: pending, approved, denied, expired or cancelled, with the human's wallet signature once they decide. Free.

NameTypeReqDescription
approval_idstringyesapr_... ID

No output schema declared.

No examples provided.

approval_wait ~68

Block until the human decides (or timeout_s passes). Returns the current status; if still pending, call again. Free.

NameTypeReqDescription
approval_idstringyesapr_... ID
timeout_sinteger–How long to wait (1-55 seconds); call again to keep waiting

No output schema declared.

No examples provided.

fortress_keys ~56

Privi's public signing keys: Ed25519 and ML-DSA-87 (NIST FIPS 204, CNSA 2.0 post-quantum). Pin these to verify Privi signatures offline. Free.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

fortress_tpi_execute ~47

Consume a two-person authorization right before performing the action. Single use; refused unless authorized. Requires the organization API key.

NameTypeReqDescription
request_idstringyestpi_... ID

No output schema declared.

No examples provided.

fortress_tpi_list ~22

Your organization's two-person requests. Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fortress_tpi_policy ~97

Define a Two-Person Integrity policy: which officers can approve, and how many distinct approvals an action needs. Requires the organization API key.

NameTypeReqDescription
namestringyesPolicy name, e.g. 'treasury-transfers'
officer_walletsarrayyes0x wallets of the officers who may approve (at least 2)
requiredintegeryesApprovals needed (2..number of officers)

No output schema declared.

No examples provided.

fortress_tpi_request ~129

Ask officers to authorize a sensitive action under a two-person policy. Returns approve_url for the officers; each signs with their wallet. Do not act until fortress_tpi_status shows 'authorized', then call fortress_tpi_execute. Requires the organization API key.

NameTypeReqDescription
details––Exact parameters; their hash is what officers sign
hoursinteger–Hours until the request expires (1-168)
policystringyesPolicy name
stream_idstringyesThe agent asking
summarystringyesExactly what will be done, in plain words

No output schema declared.

No examples provided.

fortress_tpi_status ~47

Status of a two-person request (pending, authorized, vetoed, expired, executed) and who approved. Free.

NameTypeReqDescription
request_idstringyestpi_... ID

No output schema declared.

No examples provided.

gateway_create ~244

Put your MCP server behind Privi. You get an HTTP URL and a WebSocket URL that forward to it unchanged (x402 payments keep working) while Privi rate-limits callers, optionally requires a Privi Passport, meters every tool call and writes each call to your tamper-evident log. The kill switch stops the gateway instantly. Upstream must be public HTTPS. Requires the organization API key.

NameTypeReqDescription
guardstring–Privi Guard on every tool result: off, tag (add the verdict in _meta) or block (withhold injected results). Each check uses your Guard allowance or credits
min_scoreinteger–0 = open to everyone. >0 = callers must prove a KYA wallet whose Passport scores at least this (0-1000)
namestringyesA name for this gateway, e.g. 'acme-search-mcp'
rate_per_mininteger–Requests per minute per caller (1-1200)
upstream_urlstringyesThe MCP server's public https URL (streamable HTTP), e.g. https://api.acme.com/mcp

No output schema declared.

No examples provided.

gateway_delete ~44

Turn a gateway off. Its URLs stop working at once; history stays in your log. Requires the organization API key.

NameTypeReqDescription
gw_idstringyesgw_... ID

No output schema declared.

No examples provided.

gateway_info ~47

Public description of a gateway: where it forwards, whether callers need a Passport, its rate limit and its call counts. Free.

NameTypeReqDescription
gw_idstringyesgw_... ID

No output schema declared.

No examples provided.

gateway_list ~18

Your organization's gateways. Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gateway_set_guard ~101

Turn Privi Guard on for every tool result that passes through your gateway: tag adds the verdict and a receipt id in result._meta['privi/guard']; block also replaces injected results with an error before your agents see them. Each result is one Guard check (free allowance, then credits). Requires the organization API key.

NameTypeReqDescription
gw_idstringyesgw_... ID
modestringyesoff | tag | block

No output schema declared.

No examples provided.

gateway_stats ~53

Calls, errors, denials and x402 payment prompts per tool and per day for one of your gateways, plus your monthly quota. Requires the organization API key.

NameTypeReqDescription
gw_idstringyesgw_... ID

No output schema declared.

No examples provided.

gov_ai_inventory ~44

Your agency's AI use case inventory: the current version of each record. Requires the organization API key.

NameTypeReqDescription
use_case_id––One use case; omit for all

No output schema declared.

No examples provided.

gov_ai_inventory_check ~94

Flags what an OMB M-25-21 review would flag before you submit: missing required fields, PII without a Privacy Impact Assessment, and high-impact AI in pilot or deployment missing any minimum risk practice (testing, impact assessment, independent review, monitoring, operator training, fail-safe, appeals, public feedback) or without a recently active activity log as monitoring evidence. Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gov_ai_inventory_export ~89

Machine-readable CSV of your publicly releasable AI use cases (for publishing at agency.gov/ai), with its SHA-256 sealed on chain (Base, until the Privi chain mainnet) so the published file can be proven unaltered. Requires the organization API key.

NameTypeReqDescription
include_withheldboolean–Include use cases marked withhold_from_public (internal copy)

No output schema declared.

No examples provided.

gov_ai_usecase_save ~273

Add or update an entry in your agency's AI use case inventory (OMB M-25-21). Every change creates a new version and is written to your tamper-evident 'ai-inventory' log. Requires the organization API key.

NameTypeReqDescription
actorstringyesWho is making the change (person or agent)
mergeboolean–Merge into the existing record (true) or replace it (false)
use_caseobjectyesAI use case record in OMB M-25-21 reporting fields. Required: use_case_id, name, stage (pre_deployment|pilot|deployed|retired), high_impact, purpose, outputs, sourcing (in_house|vendor|both), involve…

No output schema declared.

No examples provided.

gov_ai_verify_export ~57

Check that a published AI inventory file is exactly what the agency exported from Privi Ledger, and return its on-chain seal. Free; no key needed.

NameTypeReqDescription
csv_textstringyesThe exact CSV file contents as published

No output schema declared.

No examples provided.

gov_pqc_classify ~115

Classify cryptographic algorithms as quantum-vulnerable (RSA, ECDH, ECDSA, EdDSA, DH, DSA, MQV), post-quantum (ML-KEM, ML-DSA, SLH-DSA), hybrid, symmetric/hash, or unknown. Free.

NameTypeReqDescription
algorithmsarrayyesAlgorithm or cipher-suite names, e.g. 'RSA-2048', 'ECDHE-RSA-AES256-GCM', 'X25519MLKEM768'

No output schema declared.

No examples provided.

gov_pqc_export ~63

Export the full cryptographic inventory (CBOM) and migration plan as one JSON document for OMB, the CIO or auditors, with its SHA-256 sealed on chain (Base, until the Privi chain mainnet). Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gov_pqc_inventory ~36

Current cryptographic inventory of your systems. Requires the organization API key.

NameTypeReqDescription
system_id––One system; omit for all

No output schema declared.

No examples provided.

gov_pqc_plan ~105

Prioritized post-quantum migration plan: every quantum-vulnerable asset ranked (High Value Assets, high-impact systems and long-lived sensitive data first; key establishment before signatures), with its deadline (key establishment Dec 31 2030, signatures Dec 31 2031), recommended NIST replacement, progress metrics, and findings (missed deadlines, TLS below 1.3, no target dates, unrecognized algorithms). Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gov_pqc_system_save ~202

Record the cryptographic inventory (CBOM) of one system for post-quantum migration. Every change creates a new version and is written to the agency's tamper-evident 'pqc-inventory' log. Scanners and agents can submit results directly. Requires the organization API key.

NameTypeReqDescription
actorstringyesWho made the change (person, scanner or agent)
systemobjectyesSystem record: system_id, name, bureau, owner, high_value_asset, high_impact, sensitive_until_year, fedramp_cloud, notes, assets [{asset_id, kind (key_establishment|signature|encryption|symmetric|has…

No output schema declared.

No examples provided.

gov_pqc_verify_export ~58

Check that a CBOM and migration-plan document is exactly what was exported from Privi Ledger and return its on-chain seal. Free; no key needed.

NameTypeReqDescription
documentobjectyesThe 'document' object exactly as exported

No output schema declared.

No examples provided.

guard_balance ~24

Your free checks left this month and your prepaid credits. Needs the organization key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

guard_buy_credits ~92

Buy prepaid Privi Guard checks in USDC on Base via x402. Credits never expire and are used after the free monthly allowance. Needs the organization key.

NameTypeReqDescription
packstringyes1k = 1,000 checks for 7 USDC; 10k = 10,000 for 50 USDC; 100k = 100,000 for 300 USDC

No output schema declared.

No examples provided.

guard_check ~216

Check content for prompt injection (inbound) or leaked secrets and personal data (outbound) before an agent acts on it or sends it. Returns allow / warn / block, the findings, a redacted copy for outbound secrets, and an Ed25519-signed receipt anchored on-chain, which proves the check happened. Privi does not store the text. Free for 1,000 checks a month with an organization key; otherwise 1 cent per check in USDC via x402.

NameTypeReqDescription
directionstring–inbound = untrusted content coming in (prompt injection, hidden instructions); outbound = content going out (API keys, card numbers, data smuggled in URLs)
source––Optional label for the receipt, e.g. the page URL or tool name
textstringyesThe content to check: a web page, email, document or tool result the agent is about to act on (inbound), or what the agent is about to send (outbound)

No output schema declared.

No examples provided.

guard_check_many ~88

Check up to 50 texts in one call (for example every tool result in a step). Each item is billed as its own check against your free allowance or credits and gets its own receipt. Needs an organization key.

NameTypeReqDescription
itemsarrayyesUp to 50 items {"text": "...", "direction": "inbound"|"outbound", "source": "optional label"}

No output schema declared.

No examples provided.

guard_pricing ~26

What Privi Guard checks, what it costs, and how receipts work. Free.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

guard_receipt ~62

Verify a Privi Guard receipt: the signed body, signature validity and its Merkle proof into the anchored transparency log. Free; anyone holding the id can verify it.

NameTypeReqDescription
check_idstringyesgc_... id from a guard_check receipt

No output schema declared.

No examples provided.

kya_bind_wallet ~144

Step 2: bind the wallet to your organization's Privi Passport so its transactions pass KYA checks. With a wallet signature the binding is *proven*; without one it is only *declared* (most checkers require proven). Requires the organization API key.

NameTypeReqDescription
addressstringyes0x wallet address
challenge_id––From kya_challenge
labelstring–Friendly name, e.g. 'treasury-agent hot wallet'
signature––65-byte hex signature of the challenge message by the wallet
stream_id––The agent (stream) that uses this wallet; omit for the whole organization

No output schema declared.

No examples provided.

kya_challenge ~65

Step 1 of binding a wallet to your Privi Passport: get a message to sign with that wallet (EIP-191 personal_sign). Valid 30 minutes. Requires the organization API key.

NameTypeReqDescription
addressstringyes0x wallet address your agent controls

No output schema declared.

No examples provided.

kya_check ~194

Know-Your-Agent for blockchains: is this wallet operated by an audited AI agent, and how trustworthy is it right now? Resolves the address to its organization and live Privi Passport and returns allow/deny with reasons, plus a Privi-signed attestation (valid 60 min) you can cache. For chains, DeFi protocols, exchanges, stablecoin issuers and x402 facilitators. Free; send your organization key to log the check as evidence.

NameTypeReqDescription
addressstringyes0x wallet address about to send or receive a transaction
min_grade––Minimum grade A-E
min_scoreinteger–Minimum current Passport score 0-1000
purposestring–What the transaction is for (recorded in your log if you send your key)
require_signedboolean–Require wallet ownership proven by signature (not just declared)

No output schema declared.

No examples provided.

kya_unbind_wallet ~48

Remove a wallet from your Passport (rotated or compromised key). KYA checks deny it immediately. Requires the organization API key.

NameTypeReqDescription
addressstringyes0x wallet address

No output schema declared.

No examples provided.

kya_wallets ~27

Wallets bound to your organization and how each was proven. Requires the organization API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ledger_audit_stream ~111

Check whether an agent's action log is intact: entry count, time span, action and failure counts, head hash, and where tampering broke the chain if it did. Does not reveal the actions themselves. Paid per call via x402.

NameTypeReqDescription
org_idstringyesOrganization ID, e.g. org_1a2b3c4d5e6f7a8b
stream_idstringyesStream ID, usually the agent's name

No output schema declared.

No examples provided.

ledger_check_receipt ~53

Confirm that an action receipt exists in the ledger and when it was recorded. Reveals no action contents. Free.

NameTypeReqDescription
entry_hashstringyes64-character hex entry_hash returned when the action was recorded

No output schema declared.

No examples provided.

ledger_compliance_report ~155

Audit-ready report of your AI agents' activity for a period (SOC 2 evidence, security questionnaires, AI-regulation record keeping): actions by type, failures, human approvals, log integrity, on-chain status, and findings. The report's hash is anchored on the Privi blockchain so it cannot be edited later without detection. Requires the organization API key.

NameTypeReqDescription
since––Start of period, ISO 8601 UTC (e.g. 2026-10-01T00:00:00Z). Omit for all history
streams––Only these streams; omit for all
until––End of period, ISO 8601 UTC. Omit for now

No output schema declared.

No examples provided.

ledger_consistency_proof ~68

Proof that Privi's log only grew between two signed tree heads: nothing recorded earlier was edited, removed or reordered (RFC 9162). Free.

NameTypeReqDescription
firstintegeryesOlder signed tree size
second––Newer signed tree size; omit for latest

No output schema declared.

No examples provided.

ledger_evidence_bundle ~103

Export a self-contained evidence package for auditors, courts or air-gapped systems: every entry, the hash chain, an RFC 9162 inclusion proof, the signed tree head, on-chain checkpoint and Privi's keys, signed with Ed25519 and ML-DSA-87. Verify offline with verify_bundle.py (GET /tools/verify_bundle.py). Requires the organization API key.

NameTypeReqDescription
stream_idstringyesStream to export

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http canoydario847-cloud-privi-ledger 'https://privi-ledger.onrender.com/mcp'
Common questions

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.