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 Ledger — Recovery Evaluation

REMOTE · PRIVI-LEDGER-AQE5.ONRENDER.COM

Evaluation-only ledger MCP. Temporary storage; not durable audit evidence. Payments disabled.

66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 13497 tokens (~99/item across 136 items; 136 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
  • Structured output schemas are declared (6% 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 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 137 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
What we tested

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 →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 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.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 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 21 Nov 2026 · Probed https://privi-ledger-aqe5.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 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 8d72a13c2c41648513b9d014eb5e0339
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-aqe5.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-aqe5.onrender.com/mcp Verified 200
http (plaintext) http://privi-ledger-aqe5.onrender.com/mcp HTTPS enforced 301 https://privi-ledger-aqe5.onrender.com/mcp
MCP tools · 136 exposed · ~12,073 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
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.

ledger_handshake_accept ~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.

NameTypeReqDescription
actorstringyesWho is accepting on your side
handshake_idstringyeshs_... ID from the offer
stream_idstringyesYour stream to record it in

No output schema declared.

No examples provided.

ledger_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 ~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.

NameTypeReqDescription
action_typestringyesOne of: tool_call, data_access, data_change, payment, message, decision, approval, error, other
actorstringyesWho is acting on your side
counterparty_org_idstringyesorg_id of the other company (must be on Privi Ledger)
details––Terms as structured data (amounts, quantities, dates)
expires_hoursnumber–Hours the other company has to respond
resourcestring–Invoice, order, dataset, contract or other reference
stream_idstringyesYour stream to record it in, usually your agent's name
summarystringyesWhat is being agreed or done between the two companies

No output schema declared.

No examples provided.

ledger_handshake_reject ~65

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

NameTypeReqDescription
handshake_idstringyeshs_... ID from the offer
reasonstring–Why it is rejected (shared with the other company)

No output schema declared.

No examples provided.

ledger_handshake_verify ~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.

NameTypeReqDescription
handshake_idstringyeshs_... handshake ID

No output schema declared.

No examples provided.

ledger_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.

NameTypeReqDescription
entry_hashstringyes64-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 ~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 ~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 ~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 ~71

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

NameTypeReqDescription
after_seqinteger–Return entries after this sequence number
limitinteger–Max entries to return
stream_idstringyesStream ID

No output schema declared.

No examples provided.

ledger_record_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.

NameTypeReqDescription
action_typestringyesOne of: tool_call, data_access, data_change, payment, message, decision, approval, error, other
actorstringyesWho acted: agent name, model, or user on whose behalf
details––Optional structured details (JSON object, under 16 KB)
outcomestring–One of: success, failure, pending, blocked
resourcestring–What was acted on: URL, file, record ID, account
stream_idstringyesStream to append to, usually the agent's name, e.g. 'billing-agent'
summarystringyesOne-line description of what was done

No output schema declared.

No examples provided.

ledger_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.

NameTypeReqDescription
report_idstringyesreport_id returned by ledger_compliance_report

No output schema declared.

No examples provided.

ledger_signup ~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.

NameTypeReqDescription
organization_namestringyesYour company or project name

No output schema declared.

No examples provided.

ledger_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 ~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 ~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.

NameTypeReqDescription
reportobjectyesThe 'report' object exactly as received from ledger_compliance_report

No output schema declared.

No examples provided.

live_info ~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 ~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.

NameTypeReqDescription
reasonstring–Why (shown in your log and on your live channel)
stream_idstring–The agent (stream) to stop, or '*' for every agent in your organization

No output schema declared.

No examples provided.

live_resume ~39

Lift a kill switch set with live_kill. Requires the organization API key.

NameTypeReqDescription
stream_idstring–The agent to resume, or '*'

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
amount_usdcstringyesPayment amount in USDC
mandate_idstringyesmdt_... ID the agent presented
payeestringyesWho is being paid: your 0x address or domain

No output schema declared.

No examples provided.

mandate_create ~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.

NameTypeReqDescription
agent_wallet––0x wallet the agent pays from (optional)
daysinteger–Days until the mandate expires (1-365)
max_per_payment_usdc––Cap per payment; defaults to the total
max_total_usdcstringyesTotal budget in USDC, e.g. '250'
payees––Allowed payees (0x addresses or domains); omit for any
principal_walletstringyes0x wallet of the human who authorizes the spending
purposestringyesWhat the agent may spend on, in plain words
stream_idstringyesThe agent (stream) that will spend, e.g. 'shopping-agent'

No output schema declared.

No examples provided.

mandate_get ~47

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

NameTypeReqDescription
mandate_idstringyesmdt_... ID

No output schema declared.

No examples provided.

mandate_list ~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 ~57

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

NameTypeReqDescription
mandate_idstringyesmdt_... ID
reasonstring–Why

No output schema declared.

No examples provided.

mandate_spend ~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.

NameTypeReqDescription
amount_usdcstringyesPayment amount in USDC
approval_id––apr_... : the human's live approval, if this payment is over the agent's approval threshold
mandate_idstringyesmdt_... ID
payeestringyesWho is being paid: 0x address or domain
referencestring–Order, invoice or transaction reference

No output schema declared.

No examples provided.

mcp_server_check ~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.

NameTypeReqDescription
expected_tools_hash––The tools_hash you approved earlier; Privi tells you if the tools changed since then (rug-pull check)
urlstringyesThe server's streamable-HTTP MCP endpoint, e.g. https://example.com/mcp

No output schema declared.

No examples provided.

passport_gate ~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.

NameTypeReqDescription
min_grade––Minimum grade A-E (alternative to min_score)
min_scoreinteger–Minimum current score 0-1000
passport_idstringyespp_... ID presented by the other agent
purposestring–What you are about to do with this counterparty (recorded in your log if you send your key)
require_anchoredboolean–Require the passport to be anchored on chain (Base)

No output schema declared.

No examples provided.

passport_issue ~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.

NameTypeReqDescription
stream_id––Issue for one agent (stream). Omit for the whole organization

No output schema declared.

No examples provided.

passport_list ~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 ~63

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

NameTypeReqDescription
passport_idstringyespp_... ID
reasonstring–Why (shown to verifiers)

No output schema declared.

No examples provided.

passport_verify ~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.

NameTypeReqDescription
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.

policy_acknowledge ~96

Record that a person read and accepted the current version of a policy. The fingerprint must match the current version, so nobody signs off on an old document. Requires the organization API key.

NameTypeReqDescription
document_sha256stringyesSHA-256 fingerprint of the document (64 hex characters); the file stays with you
personstringyesName or email of the person acknowledging
policy_idstringyes–

No output schema declared.

No examples provided.

policy_publish ~103

Publish a policy (or a new version of one) by its document fingerprint. People then acknowledge that exact version. Requires the organization API key.

NameTypeReqDescription
actorstringyesWho is doing this (person or agent)
document_sha256stringyesSHA-256 fingerprint of the document (64 hex characters); the file stays with you
policy_idstringyesYour short ID, e.g. acceptable-use
titlestringyes–

No output schema declared.

No examples provided.

policy_status ~63

Who acknowledged the current version of a policy and who is still missing. This is the evidence auditors ask for. Requires the organization API key.

NameTypeReqDescription
policy_idstringyes–
required_people––Everyone who must sign; Privi lists who is missing

No output schema declared.

No examples provided.

privi_payment_options ~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 ~48

Off-chain PRVI_TEST quote. Requires organization key and explicit test mode. Never takes money.

NameTypeReqDescription
skustringyesExisting priced tool to model; NO service will be unlocked

No output schema declared.

No examples provided.

privi_test_payment_simulate ~57

Consume a test quote once. Receipt is NOT payment, on-chain proof or entitlement.

NameTypeReqDescription
acknowledgementstringyesMust equal VALUELESS TEST ONLY
quote_idstringyesShort-lived PRVI_TEST quote ID

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
amountstring–Amount to swap in (USDC for buy, PRIVI for sell), e.g. '25'
sidestring–Optional swap quote: 'buy' (USDC -> PRIVI) or 'sell' (PRIVI -> USDC)

Structured output declared, but exposes no named fields.

No examples provided.

qledger_block ~41

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

NameTypeReqDescription
heightintegeryesBlock height (0 = genesis)

No output schema declared.

No examples provided.

qledger_entry_proof ~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.

NameTypeReqDescription
entry_hashstringyesentry_hash from ledger_record_action

No output schema declared.

No examples provided.

qledger_seal ~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.

Install

How do I install the Privi Ledger — Recovery Evaluation MCP server?

Privi Ledger — Recovery Evaluation is a hosted endpoint at https://privi-ledger-aqe5.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-aqe5.onrender.com

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

What is the Privi Ledger — Recovery Evaluation MCP server?

Privi Ledger — Recovery Evaluation is an MCP server listed in the public MCP registry as io.github.canoydario847-cloud/privi-ledger. Evaluation-only ledger MCP. Temporary storage; not durable audit evidence. Payments disabled. This page covers its hosted endpoint (https://privi-ledger-aqe5.onrender.com/mcp).

Is the Privi Ledger — Recovery Evaluation MCP server safe to use?

Privi Ledger — Recovery Evaluation scores 66 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 Ledger — Recovery Evaluation MCP server expose?

Privi Ledger — Recovery Evaluation exposes 136 tools: privi_token_market, ledger_pricing, ledger_check_receipt, ledger_audit_stream, agent_proof_verify, and 131 more. Their descriptions and schemas cost roughly 12,073 tokens of context every time the server is loaded.

Does the Privi Ledger — Recovery Evaluation MCP server require authentication?

No. We connected to Privi Ledger — Recovery Evaluation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Privi Ledger — Recovery Evaluation MCP server still maintained?

Privi Ledger — Recovery Evaluation is still listed as active in the MCP registry. We last reached this channel on 21 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 Ledger — Recovery Evaluation MCP server?

VerifyMCP ran 13 checks on Privi Ledger — Recovery Evaluation, 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.