Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

Privi Quantum Ledger

von canoydario847-cloudVersion 0.12.1i★ –iLäuft in der Cloud
Name in der Registryio.github.canoydario847-cloud/privi-ledger

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Quantum-sealed audit logs for AI agents (ML-DSA-87, SHA3-512), plus Privi Guard and trust passports.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Buchhaltung, Finanzen & Steuern

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 60 Dinge (Tools) privi_token_market, ledger_pricing, ledger_check_receipt, ledger_audit_stream …
  • Die Registry nennt keinen Schlüssel zum Eintragen.

Du brauchst

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://privi-ledger.onrender.com/mcp

Führe das in deinem Terminal aus

claude mcp add --transport http privi-ledger https://privi-ledger.onrender.com/mcp

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "privi-ledger": {
      "url": "https://privi-ledger.onrender.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "privi-ledger": {
      "type": "http",
      "url": "https://privi-ledger.onrender.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

ChatGPT verbindet sich nur mit Servern im Internet:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://privi-ledger.onrender.com/mcp

Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 7. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • privi_token_market

    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.

  • ledger_pricing

    List Privi Ledger tools, what each costs, and how to get an organization key.

  • ledger_check_receipt

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

  • ledger_audit_stream

    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.

  • ledger_record_action

    Append an action to the organization's tamper-evident log. Returns the entry with its entry_hash receipt. Requires the organization API key.

  • ledger_read_stream

    Read your organization's entries in a stream, oldest first, with an integrity check of the whole stream. Requires the organization API key.

  • ledger_list_streams

    List your organization's streams with entry counts. Requires the organization API key.

  • ledger_compliance_report

    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

  • ledger_report_pdf

    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/ .pdf with the organization key. Requires the organization API key.

  • ledger_verify_report

    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.

  • ledger_signup

    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.

  • ledger_plan

    Your plan, entries used this month, the limit, and when a Pro plan renews. Requires your organization API key.

  • ledger_upgrade_pro

    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.

  • gov_ai_usecase_save

    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.

  • gov_ai_inventory

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

  • gov_ai_inventory_check

    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 train

  • gov_ai_inventory_export

    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.

  • gov_ai_verify_export

    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.

  • gov_pqc_classify

    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.

  • gov_pqc_system_save

    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.

  • gov_pqc_inventory

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

  • gov_pqc_plan

    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

  • gov_pqc_export

    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.

  • gov_pqc_verify_export

    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.

  • ledger_handshake_offer

    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 org

  • ledger_handshake_inbox

    Handshakes sent to and from your organization, newest first, with their terms and status. Requires your organization API key.

  • ledger_handshake_accept

    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.

  • ledger_handshake_reject

    Reject a handshake addressed to your organization; the other company's log records the rejection. Requires your organization API key.

  • ledger_handshake_verify

    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.

  • passport_issue

    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 v

  • passport_verify

    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.

  • passport_gate

    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.

  • passport_list

    Your organization's issued passports with score, grade, expiry and revocation. Requires the organization API key.

  • passport_revoke

    Revoke one of your passports (e.g. an agent was retired or compromised). Verifiers see it immediately. Requires the organization API key.

  • kya_check

    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

  • kya_challenge

    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.

  • kya_bind_wallet

    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.

  • kya_wallets

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

  • kya_unbind_wallet

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

  • mandate_create

    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

  • mandate_check

    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 att

  • mandate_spend

    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 thre

  • mandate_get

    Public view of a mandate: terms, status, the human's signature, spent and remaining budget, and recent spends. Free.

  • mandate_list

    Your organization's mandates with status and remaining budget. Requires the organization API key.

  • mandate_revoke

    Stop an agent from spending under a mandate (the human can also revoke from the sign_url page). Requires the organization API key.

  • fortress_keys

    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.

  • ledger_tree_head

    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.

  • ledger_inclusion_proof

    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.

  • ledger_consistency_proof

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

  • fortress_tpi_policy

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

  • fortress_tpi_request

    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.

  • fortress_tpi_status

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

  • fortress_tpi_execute

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

  • qledger_status

    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.

  • qledger_block

    One quantum-sealed block with its signatures, settlement on chain and a validity check. Free.

  • qledger_verify_chain

    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.

  • qledger_entry_proof

    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.

  • qledger_seal

    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.

  • fortress_tpi_list

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

  • ledger_evidence_bundle

    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

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto canoydario847-cloud bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 264 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 60 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Buchhaltung, Finanzen & Steuerni

  • Mehr Sterne als 0 % der anderen 2949 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 71 % der anderen 2949 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 2949 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Privi Quantum Ledger sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.12.1) kam vor 12 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Finance Toolkit, SolidInvoice, Korea Tax Calculator

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Finance Toolkit

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

von JerBoumaWeit verbreitet↓ 15.541/Wo.★ 5496Aktualisiert vorgestern

Computer oder Cloud

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

von SolidInvoiceWachsend★ 981Aktualisiert vor 9 Tagen

Läuft in der Cloud✓ solidinvoice.co

Korea Tax Calculator

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

von UpstageAIWachsend↓ 3172/Wo.★ 97Aktualisiert heute

Läuft auf deinem Computer

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

Privi Quantum Ledger MCP

*(formerly Privi Ledger)*

Quantum-sealed, tamper-evident audit logs for AI agents. Every company running agents needs to prove what those agents did: what data they touched, what they paid for, what they changed, and that nobody rewrote the record afterwards. Privi Ledger gives any MCP-capable agent a place to log each action, and gives auditors a way to verify the log, paid per check in USDC on Base via x402.

Works with Claude, ChatGPT, Cursor, VS Code and custom agents. Built by Privi World Co on the same record technology as Privi Verify.

Live (testnet): https://privi-ledger.onrender.com/mcp

Tools

Real-time tools (live_*, approval_*, trust_events, gateway_*, room_*) are described under *Privi Live* below.

ToolAccessWhat it does
ledger_pricingfreePrices, network, action types, how to get a key
ledger_check_receiptfreeConfirms an action receipt (entry_hash) exists and when; reveals no contents
ledger_audit_stream$0.02 (x402)Integrity audit of an agent's log: intact or not, where it broke, counts, time span, head hash. No action contents
ledger_record_actionorg keyAppend an action; returns the entry and its entry_hash receipt
ledger_read_streamorg keyRead your own entries with an integrity check
ledger_list_streamsorg keyYour streams and entry counts
ledger_compliance_reportorg keyAudit-ready report of agent activity for a period, sealed on the Privi chain
ledger_report_pdforg keyThe sealed report as a finished PDF (also at GET /reports/ .pdf with the org key)
ledger_handshake_offer / _accept / _reject / _inboxorg keyPrivi Handshake: two-sided records of dealings between companies
ledger_handshake_verifyfreePublic check of a handshake and its on-chain seal; never reveals terms
ledger_verify_reportfreeProves a report is unaltered and was issued by Privi Ledger; checks its on-chain seal

Action types: tool_call, data_access, data_change, payment, message, decision, approval, error, other. Outcomes: success, failure, pending, blocked.

How the log stays honest

Each entry's SHA-256 fingerprint covers its contents and the previous entry's fingerprint in the same stream. Editing, deleting or reordering any entry breaks the chain from that point, and audits report the exact entry where it broke. Organizations only ever see their own streams; API keys are stored as hashes.

Stream heads are anchored on the Privi blockchain every few minutes (see On-chain checkpoints), so integrity can be proven without trusting Privi.

Plans (self-serve)

PlanHowIncludes
Freeledger_signup (no key needed)Every tool, up to 500 entries per month
Proledger_upgrade_pro, $29 USDC per 30 days via x402Unlimited entries; each payment adds 30 days
EnterpriseCreated by Privi (/admin/orgs)Unlimited; billed by agreement

Any company, or an AI agent acting for one, can sign up, start logging, and upgrade without talking to anyone. Payments go straight to LEDGER_PAY_TO, and each purchase is recorded in the organization's own privi-billing stream. ledger_plan shows usage and renewal. Set LEDGER_FREE_MONTHLY and LEDGER_PRICE_PRO_MONTH to change the limits.

Onboarding a customer

Create an organization with the admin key (set LEDGER_ADMIN_KEY):

curl -X POST https://<host>/admin/orgs \

-H "Authorization: Bearer $LEDGER_ADMIN_KEY" -H 'Content-Type: application/json' \ -d '{"name": "Acme Robotics"}'

-> {"org_id": "org_...", "api_key": "plk_...", ...} (the key is shown once)

The customer adds the server to their agent with header Authorization: Bearer plk_..., and tells it to call ledger_record_action after each meaningful action. They share their org_id and stream names with auditors, who call ledger_audit_stream.

Compliance reports

ledger_compliance_report turns an organization's agent logs into evidence for SOC 2 reviews, customer security questionnaires and AI-regulation record keeping. For any period it reports actions by type, actors, failures, blocked actions, human approvals, log integrity and on-chain status. It also lists findings an auditor would raise, such as broken integrity, logs not yet anchored, failed actions, or payments and data changes with no human approval recorded. The result comes as JSON plus a ready-to-share Markdown version.

Each report is sealed. Its SHA-256 hash, taken over canonical JSON, is anchored on the Privi blockchain through Privi Anchor. Anyone holding the report can run ledger_verify_report, which recomputes the hash, confirms Privi Ledger issued exactly that content, and checks the anchor on chain. Editing even one number, such as hiding a failure, makes verification fail.

Privi Gov AI Inventory (OMB M-25-21)

Federal agencies must keep an inventory of their AI use cases, publish the releasable ones as a machine-readable file, and show minimum risk practices for high-impact AI. That requirement comes from OMB Memorandum M-25-21 and OMB's guidance on 2025 agency AI reporting. Privi Ledger covers the whole loop:

ToolWhat it does
gov_ai_usecase_saveAdd or update a use case in the guidance's reporting fields. Every change is a new version, written to the agency's tamper-evident ai-inventory log
gov_ai_inventoryCurrent inventory
gov_ai_inventory_checkFlags what a review would flag: missing required fields, PII without a Privacy Impact Assessment, and high-impact AI in pilot or deployment missing any minimum practice (testing, impact assessment, independent review, monitoring, operator training, fail-safe, appeals, public feedback) or without a recently active activity log as monitoring evidence. Practices waived by a written CAIO determination are respected
gov_ai_inventory_exportCSV of releasable use cases for agency.gov/ai, with its SHA-256 sealed on the Privi chain
gov_ai_verify_export (free)Proves a published inventory file is exactly what the agency exported

The inventory links to agents' Privi Ledger activity logs (monitoring_streams), so "ongoing monitoring" is backed by real, tamper-evident records.

Field names follow OMB's published reporting fields. Confirm them against OMB's current template before submitting. This tool supports compliance work; it is not legal advice or an OMB-approved system.

Privi Quantum-Ready (post-quantum migration)

Executive Order 14409 (June 2026) requires federal key establishment to move to post-quantum cryptography by Dec 31, 2030, and digital signatures by Dec 31, 2031. OMB M-26-15 asks every agency for a migration plan built on a cryptographic inventory (CBOM), prioritizing High Value Assets, high-impact systems and data that must stay sensitive past 2030, plus TLS 1.3 support by Jan 2, 2030.

ToolWhat it does
gov_pqc_classify (free)Classifies algorithms and cipher suites: quantum-vulnerable (RSA, ECDH, ECDSA, EdDSA, DH, DSA, MQV), post-quantum (ML-KEM, ML-DSA, SLH-DSA), hybrid, symmetric/hash, or unknown
gov_pqc_system_saveRecords one system's cryptographic assets (from people, scanners or agents). Versioned and written to a tamper-evident pqc-inventory log
gov_pqc_inventoryCurrent inventory
gov_pqc_planRanked migration queue with per-asset deadlines and NIST replacements, progress metrics, and findings: targets past the deadline, TLS below 1.3, priority assets with no target date, unrecognized algorithms
gov_pqc_exportThe CBOM plus plan as one JSON document, sealed on the Privi chain
gov_pqc_verify_export (free)Proves an exported document is unaltered

The rules follow public summaries of EO 14409 and OMB M-26-15. Confirm them against the official texts and NIST IR 8547 before relying on them. This tool supports compliance work; it is not legal advice.

Privi Passport (trust credentials for AI agents)

The feature no one else can copy: a signed, on-chain-anchored credential that says how much an AI agent can be trusted, scored 0-1000 from evidence only Privi Ledger holds.

ComponentMaxEvidence
history300verified entries and days of activity
integrity250every hash chain still verifies (all or nothing)
anchoring150share of streams whose on-chain checkpoint matches the record
reliability1001 - failure rate
oversight50human approvals on sensitive actions
compliance100a sealed compliance report exists and is clean
handshakes50deals other Privi organizations confirmed

Grades: A >= 850, B >= 700, C >= 550, D >= 400, E below. Valid 30 days.

  • passport_issue (org key; free on Pro/enterprise, $LEDGER_PRICE_PASSPORT via x402 on the free plan) - Ed25519-signed by the server, hash anchored on the Privi chain, every component itemised.
  • passport_verify (free) - signature, content, expiry, revocation, chain anchor, and a live re-score: if the agent's history is tampered with after issue, the passport fails.
  • passport_gate (free) - one-call allow/deny with your minimums (min_score, min_grade, require_anchored); send your own key and the decision is written to your log as due-diligence evidence.
  • passport_list, passport_revoke (org key).
  • Public: GET /passports/ (JSON + live verification), GET /passports/ /badge.svg (embeddable badge), GET /.well-known/privi-passport.json (issuer public key).

Why it compounds: agents that gate on passports push their counterparties onto Privi Ledger; every logged action, report and handshake raises the score; a better score wins more deals. Set LEDGER_PASSPORT_SIGNING_KEY (32-byte hex Ed25519 seed) to pin the issuer key across redeploys; otherwise one is generated and stored in the database.

Privi KYA (Know-Your-Agent for blockchain wallets)

As AI agents become the main senders of on-chain transactions, every chain, DeFi protocol, exchange, stablecoin issuer and x402 facilitator needs one answer before accepting a transaction: is this wallet operated by an audited agent, and how trustworthy is it right now? Privi KYA answers it, and only Privi can, because the answer is the Passport.

  • kya_challenge + kya_bind_wallet (org key) - bind a wallet to your Passport by signing a Privi challenge with the wallet (EIP-191 personal_sign, recovered in pure Python; no web3 dependency). A binding without a signature is only *declared*.
  • kya_check (free) - resolves the wallet to its organization and live Passport; returns allow/deny with reasons, the current score and grade, and a Privi-signed KYA attestation valid 60 minutes that a facilitator can cache and verify offline. Send your key and the decision is logged as evidence.
  • kya_wallets, kya_unbind_wallet (org key) - rotated or compromised keys are denied immediately.
  • Connect wallet page: GET /kya/connect — paste the org key, connect MetaMask, sign once; done. No code needed.
  • Public: GET /kya/ (JSON verdict + attestation; ?min_score=&min_grade=&require_signed=), GET /kya/ /badge.svg.

Integration pattern for a chain or protocol: before accepting an agent transaction, GET /kya/ ; require allow: true (and optionally proof: "signature"); keep the attestation + signature as your compliance record.

Privi Quantum Ledger (quantum-sealed blocks, fused with the Privi Foundation chain)

The whole log is sealed into a chain of quantum blocks every few minutes (LEDGER_QBLOCK_INTERVAL, default 300 s):

  • Each block commits to the previous block, the signed tree head of the transparency log (size + Merkle root) and a

Nur der Anfang wird gezeigt; den Rest findest du im Repo

PopNx fragen