io.github.shahidh68/audit-ledger-mcp
Record AI decisions to a tamper-evident audit ledger from any MCP-compatible agent.
The current version, v0.3.1, was published to the official MCP registry on 2026-06-05. It is distributed as audit-ledger-mcp on npm, filed under Other by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using io.github.shahidh68/audit-ledger-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions found”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-01).
Contracts can change after screening, with no version bump. The gate pins io.github.shahidh68/audit-ledger-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for io.github.shahidh68/audit-ledger-mcp](https://mcpindex.ai/server/io-github-shahidh68-audit-ledger-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-shahidh68-audit-ledger-mcp">Independent trust record for io.github.shahidh68/audit-ledger-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-shahidh68-audit-ledger-mcp)<a href="https://mcpindex.ai/server/io-github-shahidh68-audit-ledger-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-shahidh68-audit-ledger-mcp" alt="mcpindex verdict" height="20" /></a>AUDIT_API_URLYour deployed audit-ledger API endpoint (e.g. https://<api-id>.execute-api.<region>.amazonaws.com/prod). Leave unset to run in sandbox mode against the public shared tenant.
AUDIT_WRITE_KEYTenant write key for your deployed ledger. Required if AUDIT_API_URL is set and you want to call record_decision.
AUDIT_READ_KEYTenant read key for your deployed ledger. Required if AUDIT_API_URL is set and you want to call verify_decision or list_decisions.
AUDIT_TIMEOUT_MSHTTP timeout in milliseconds. Defaults to 5000.
AUDIT_RETRY_ATTEMPTSNumber of retry attempts on transient failures. Defaults to 3.
AUDIT_HMAC_KEYTenant secret used to HMAC-SHA256 PII and prompts locally before sending. Generate once per tenant (e.g. node -e "console.log(require('crypto').randomBytes(32).toString('hex'))") and keep it in your environment. The key never leaves your process. If unset, the MCP falls back to plain SHA-256 for backwards compatibility and logs a one-time deprecation warning; set this to switch to keyed hashing, which regulators (ICO/EDPB) expect for pseudonymisation.
Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.
Give your AI agent a spending limit: approval controls and single-use virtual cards.
MCP server for natural-language queries against SAP CAP db-layer entities via real CQN/SQL JOINs.