Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/shahidh68/audit-ledger-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/shahidh68/audit-ledger-mcp/audit-ledger-mcp)<a href="https://agentmods.dev/mcp/shahidh68/audit-ledger-mcp/audit-ledger-mcp"><img src="https://agentmods.dev/badge/mcp/shahidh68/audit-ledger-mcp/audit-ledger-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/shahidh68/audit-ledger-mcp/audit-ledger-mcp"><img src="https://agentmods.dev/badge/mcp/shahidh68/audit-ledger-mcp/audit-ledger-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
audit-ledger-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"audit-ledger-mcp": {
"command": "npx",
"args": [
"-y",
"audit-ledger-mcp"
],
"env": {
"AUDIT_API_URL": "",
"AUDIT_WRITE_KEY": "",
"AUDIT_READ_KEY": "",
"AUDIT_TIMEOUT_MS": "",
"AUDIT_RETRY_ATTEMPTS": "",
"AUDIT_HMAC_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 17 lines scan A 9acd8a36a908
audit-ledger-mcp is an MCP server published in the GitHub repository shahidh68/audit-ledger-mcp (1 stars, last pushed 2mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
ai-bom-mcp
AI Bill of Materials (AI-BOM) generator + auditor MCP — CycloneDX ML-BOM, SPDX 3.0 AI profile, EU AI Act Annex IV mapping, NIST AI RMF alignment, US EO 14028 federal procurement. By MEOK AI Labs. Runs locally from the ai-bom-mcp Python package.
dingdawg-legal-agent
AI contract review, clause drafting, compliance checklists & legal research. Runs locally from the dingdawg-legal-agent npm package. Needs 1 environment variable to run.
vitna-compliance-preflight
Pre-action allow/deny for AI agents. 24 statutes, 13 jurisdictions: EU AI Act, GDPR, DPDP. Runs locally from the @costrinity/vitna-compliance-mcp npm package. Needs 4 environment variables to run.
dingdawg-governance
Governance receipts for AI agents — universal, MCP-native, fail-closed governance layer compliant with EU AI Act Art. 12, Colorado AI Act (SB 24-205), and NIST AI RMF. LNN interpretability, IPFS audit proofs, and rollback for any agent in any framework. Runs locally from the dingdawg-governance npm package. Needs 1…
meok-attestation-verify
Tiny zero-dependency verifier for MEOK AI Labs compliance attestations (DORA, NIS2, CRA, EU AI Act, CSRD, AI-BOM, Gods Eye). Pipe a signed cert on stdin, get VALID/INVALID back. HMAC-SHA256. By MEOK AI Labs. Runs locally from the meok-attestation-verify Python package.
ai-incident-reporting-mcp
AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU AI Act Article 73, DORA Article 19, NIS2 Article 23, GDPR Article 33, ISO/IEC 42001 clause 9, and UK AISI voluntary frontier-model reporting. One incident → all regime clocks in parallel. HMAC-signed post-incident…