io.github.shahidh68/audit-ledger-mcp
NPM · AUDIT-LEDGER-MCP
Record AI decisions to a tamper-evident audit ledger from any MCP-compatible agent.
Available components
Last scanned (4 hours ago)
Scores higher than 58% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 144 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 768 tokens (~192/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
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 5 Nov 2026 · Analysed npm/audit-ledger-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
list_decisions ~139
List recorded AI decisions for the calling tenant within a time window. Returns newest first. The read key scopes the result to the caller's tenant — cross-tenant reads require an admin read key. Use this for compliance review, audit prep, or agent self-inspection of recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 start of the time window (inclusive). Defaults to 7 days before now. |
| limit | number | – | Maximum number of records to return (default 100, max 500). Returned newest-first. |
| to | string | – | ISO 8601 end of the time window (inclusive). Defaults to now. |
No output schema declared.
No examples provided.
record_decision ~351
Record an AI decision to the audit ledger. Stores model version, hashed inputs, structured output, and human-review flag. The record is immutably sealed in S3 Object Lock for 7 years and queryable for the lifetime of the decision. Use this immediately after any AI decision that may need to be audited later — credit, hiring, fraud, customer routing, content moderation.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_decision_output | object | yes | The structured decision the model produced. Stored verbatim. Should NOT contain raw PII — only the decision itself (score, classification, recommendation, reasoning summary). |
| event_id | string | – | Optional UUID v4 to identify this decision. Auto-generated if omitted. Useful when the calling system already has its own decision ID. |
| human_in_loop | boolean | yes | Whether a human reviewed or approved this decision before it took effect. Critical for EU AI Act Article 14 (human oversight) compliance. |
| model_version | string | yes | The model and version that produced the decision (e.g. 'claude-sonnet-4.7', 'gpt-4o-2024-08-06'). Required for traceability and model risk audits. |
| raw_system_prompt | string | yes | The system prompt used. Hashed locally before transit — the raw text never leaves this MCP server. |
| raw_user_input | string | yes | The user input the model decided on (CV text, transaction, customer message, etc.). Hashed locally before transit — raw PII never leaves this MCP server. |
| timestamp | string | – | Optional ISO 8601 timestamp of when the decision was made. Defaults to the current time. Use this only if recording a backfilled decision. |
No output schema declared.
No examples provided.
verify_completeness ~178
Detect whether any audit records have been deleted or omitted for the caller's tenant. Each successfully stored decision receives a per-tenant monotonic sequence number. This tool compares the ledger's counter against the rows actually present in DynamoDB and returns any sequence numbers that are missing. Use this when a regulator or compliance team asks 'can you prove the log is complete?' — verify_decision only proves an existing record was not altered; this proves no record has disappeared.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | – | Inclusive lower bound on sequence_no. Defaults to 1. |
| tenant_id | string | – | Required only when calling with the admin read key. Ignored when called with a regular tenant read key — the tenant is inferred from the key. |
| to | integer | – | Inclusive upper bound on sequence_no. Defaults to the tenant's current counter value. |
No output schema declared.
No examples provided.
verify_decision ~100
Verify a recorded AI decision has not been altered since it was written. The ledger fetches the queryable copy (DynamoDB) and the immutable copy (S3 Object Lock COMPLIANCE mode) independently and compares them. Returns integrity_verified=true if they match. Use this to satisfy a regulator request or to prove an audit trail to a compliance team.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The UUID v4 event ID of the decision to verify. |
No output schema declared.
No examples provided.
How do I install the io.github.shahidh68/audit-ledger-mcp server?
io.github.shahidh68/audit-ledger-mcp runs locally as an npm package, launched with npx -y audit-ledger-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · audit-ledger-mcp
claude mcp add shahidh68-audit-ledger-mcp -- npx -y audit-ledger-mcp
What is the io.github.shahidh68/audit-ledger-mcp server?
io.github.shahidh68/audit-ledger-mcp is listed in the public MCP registry as io.github.shahidh68/audit-ledger-mcp. Record AI decisions to a tamper-evident audit ledger from any MCP-compatible agent. This page covers its npm package (audit-ledger-mcp).
Is the io.github.shahidh68/audit-ledger-mcp server safe to use?
io.github.shahidh68/audit-ledger-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.shahidh68/audit-ledger-mcp server expose?
io.github.shahidh68/audit-ledger-mcp exposes 4 tools: record_decision, verify_decision, verify_completeness, list_decisions. Their descriptions and schemas cost roughly 768 tokens of context every time the server is loaded.
Is the io.github.shahidh68/audit-ledger-mcp server still maintained?
io.github.shahidh68/audit-ledger-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.shahidh68/audit-ledger-mcp server under?
io.github.shahidh68/audit-ledger-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.