Model Context Protocol server for Rollbar
Nothing to run from here
Privi Ledger is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
22
tools declared
remote
at its publisher
—
calls last 7d
What it does
Tamper-evident audit logs for AI agents. Auditors verify integrity, paid per call via x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http privi-ledger-mcp https://privi-ledger-production.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# ledger_pricing, ledger_check_receipt, ledger_audit_stream and 19 more
Privi Ledger costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CCAll 3 servers
canoydario847-cloud3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http privi-ledger-mcp https://privi-ledger-production.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Privi Ledger tools, what each costs, and how to get an organization key.
No parameter schema on file.
Confirm that an action receipt exists in the ledger and when it was recorded. Reveals no action contents. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entry_hash | string | yes | 64-character hex entry_hash returned when the action was recorded |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| org_id | string | yes | Organization ID, e.g. org_1a2b3c4d5e6f7a8b |
| stream_id | string | yes | Stream ID, usually the agent's name |
Append an action to the organization's tamper-evident log. Returns the entry with its entry_hash receipt. Requires the organization API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stream_id | string | yes | Stream to append to, usually the agent's name, e.g. 'billing-agent' |
| actor | string | yes | Who acted: agent name, model, or user on whose behalf |
| action_type | string | yes | One of: tool_call, data_access, data_change, payment, message, decision, approval, error, other |
| summary | string | yes | One-line description of what was done |
| resource | string | no | What was acted on: URL, file, record ID, account |
| outcome | string | no | One of: success, failure, pending, blocked |
| details | no | Optional structured details (JSON object, under 16 KB) |
Read your organization's entries in a stream, oldest first, with an integrity check of the whole stream. Requires the organization API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stream_id | string | yes | Stream ID |
| after_seq | integer | no | Return entries after this sequence number |
| limit | integer | no | Max entries to return |
List your organization's streams with entry counts. Requires the organization API key.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | no | Start of period, ISO 8601 UTC (e.g. 2026-10-01T00:00:00Z). Omit for all history | |
| until | no | End of period, ISO 8601 UTC. Omit for now | |
| streams | no | Only these streams; omit for all |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | report_id returned by ledger_compliance_report |
Check that a compliance report is unaltered: recomputes its hash, confirms Privi Ledger issued it, and checks the anchor on the Privi blockchain. Free; no key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report | object | yes | The 'report' object exactly as received from ledger_compliance_report |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization_name | string | yes | Your company or project name |
Your plan, entries used this month, the limit, and when a Pro plan renews. Requires your organization API key.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | object | yes | AI 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), involves |
| actor | string | yes | Who is making the change (person or agent) |
| merge | boolean | no | Merge into the existing record (true) or replace it (false) |
Your agency's AI use case inventory: the current version of each record. Requires the organization API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case_id | no | One use case; omit for all |
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
No parameter schema on file.
Machine-readable CSV of your publicly releasable AI use cases (for publishing at agency.gov/ai), with its SHA-256 sealed on the Privi blockchain so the published file can be proven unaltered. Requires the organization API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_withheld | boolean | no | Include use cases marked withhold_from_public (internal copy) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| csv_text | string | yes | The exact CSV file contents as published |
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 the Privi chain. Requires your organization API key; the other company must also use Privi Ledger.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| counterparty_org_id | string | yes | org_id of the other company (must be on Privi Ledger) |
| stream_id | string | yes | Your stream to record it in, usually your agent's name |
| actor | string | yes | Who is acting on your side |
| action_type | string | yes | One of: tool_call, data_access, data_change, payment, message, decision, approval, error, other |
| summary | string | yes | What is being agreed or done between the two companies |
| resource | string | no | Invoice, order, dataset, contract or other reference |
| details | no | Terms as structured data (amounts, quantities, dates) | |
| expires_hours | number | no | Hours the other company has to respond |
Handshakes sent to and from your organization, newest first, with their terms and status. Requires your organization API key.
No parameter schema on file.
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 the Privi chain. Requires your organization API key. Read the terms first with ledger_handshake_inbox.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handshake_id | string | yes | hs_... ID from the offer |
| stream_id | string | yes | Your stream to record it in |
| actor | string | yes | Who is accepting on your side |
Reject a handshake addressed to your organization; the other company's log records the rejection. Requires your organization API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handshake_id | string | yes | hs_... ID from the offer |
| reason | string | no | Why it is rejected (shared with the other company) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handshake_id | string | yes | hs_... handshake ID |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Privi Ledger or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest3d3fa97b60239773f3c7643f0c534b0fb62465dadd41a67627d6418abf71c088
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ledger_pricing | no tags | |
| ledger_check_receipt | no tags | |
| ledger_audit_stream | no tags | |
| ledger_record_action | state-write | state-write: declares readOnlyHint: false |
| ledger_read_stream | no tags | |
| ledger_list_streams | no tags | |
| ledger_compliance_report | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| ledger_report_pdf | no tags | |
| ledger_verify_report | no tags | |
| ledger_signup | state-write | state-write: declares readOnlyHint: false |
| ledger_plan | no tags | |
| ledger_upgrade_pro | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| gov_ai_usecase_save | state-write | state-write: declares readOnlyHint: false |
| gov_ai_inventory | no tags | |
| gov_ai_inventory_check | no tags | |
| gov_ai_inventory_export | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| gov_ai_verify_export | no tags | |
| ledger_handshake_offer | state-write | state-write: declares readOnlyHint: false |
| ledger_handshake_inbox | no tags | |
| ledger_handshake_accept | state-write | state-write: declares readOnlyHint: false |
| ledger_handshake_reject | state-write | state-write: declares readOnlyHint: false |
| ledger_handshake_verify | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3d3fa97b60239773
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Privi Ledger can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.