by bkuan001 · MCP Server · ★ 82
halo-record Tamper-evident runtime records for AI agents: the audit trail the vendor runs but cannot edit. Every action your agent takes (tool calls, model calls, data access, approvals) becomes one record in an append-only, hash-chained log. Any party can verify the log was never altered, without trusting whoever produced it. When a customer's security team asks "what did your agent do with our data?", you hand them a link instead of a paragraph. Security reviews already ask AI questions next to the SOC 2 checklist, and today a written assurance still passes.
| Stars | 82 |
| Forks | 10 |
| Language | Python |
| Category | MCP Server |
| License | Apache-2.0 |
| Quality Score | 41.25/100 |
| Last Updated | 2026-10-03 |
| Created | 2026-06-11 |
| Platforms | mcp, python |
| Est. Tokens | ~13k |
These tools work well together with halo-record for enhanced workflows:
Explore other popular mcp server tools:
halo-record is Tamper-evident audit trails for AI agents: hash-chained Runtime Records, dependency-free, verifiable by anyone.. It is categorized as a MCP Server with 82 GitHub stars.
halo-record is primarily written in Python. It covers topics such as agents, ai-agents, ai-governance.
You can find installation instructions and usage details in the halo-record GitHub repository at github.com/bkuan001/halo-record. The project has 82 stars and 10 forks, indicating an active community.
halo-record is released under the Apache-2.0 license, making it free to use and modify according to the license terms.