Home / MCP registry index / io.github.canoydario847-cloud/privi-ledger
Privi Quantum Ledger
io.github.canoydario847-cloud/privi-ledger in the official MCP registry.
Endpoint https://privi-ledger.onrender.com/mcp. Source: github.com/canoydario847-cloud/Privi-Network.
The registry describes it as: Quantum-sealed audit logs for AI agents (ML-DSA-87, SHA3-512), plus Privi Guard and trust passports.
We read its 121 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
privi_token_market ledger_pricing ledger_check_receipt ledger_audit_stream ledger_record_action ledger_read_stream ledger_list_streams ledger_compliance_report ledger_report_pdf ledger_verify_report ledger_signup ledger_plan ledger_upgrade_pro gov_ai_usecase_save gov_ai_inventory gov_ai_inventory_check gov_ai_inventory_export gov_ai_verify_export gov_pqc_classify gov_pqc_system_save gov_pqc_inventory gov_pqc_plan gov_pqc_export gov_pqc_verify_export ledger_handshake_offer ledger_handshake_inbox ledger_handshake_accept ledger_handshake_reject ledger_handshake_verify passport_issue passport_verify passport_gate passport_list passport_revoke kya_check kya_challenge kya_bind_wallet kya_wallets kya_unbind_wallet mandate_create mandate_check mandate_spend mandate_get mandate_list mandate_revoke fortress_keys ledger_tree_head ledger_inclusion_proof ledger_consistency_proof fortress_tpi_policy fortress_tpi_request fortress_tpi_status fortress_tpi_execute qledger_status qledger_block qledger_verify_chain qledger_entry_proof qledger_seal fortress_tpi_list ledger_evidence_bundle and 61 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-canoydario847-cloud-privi-ledger)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.