EvidentTrail MCP
Related Servers
Alternatives to EvidentTrail MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
- AlicenseNot gradedqualityAmaintenanceTamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.348 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides an immutable, tamper-evident audit trail for AI agents, enabling event logging with cryptographic chaining, search, verification, and statistics.3MIT
- AlicenseAqualityAmaintenanceChange tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.8205 PyPI24MIT
- AlicenseNot gradedqualityFmaintenanceProvides tamper-proof audit logging for AI agents using SHA-256 hash chains, integrity verification, and compliance reporting for the EU AI Act.1MIT
- AlicenseNot gradedqualityCmaintenanceCaptures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.MIT
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection; the tool's purpose (logging an agent action as compliance evidence) is unambiguous and clearly stated. No overlap risk exists in the current surface.
The name et_log_action follows a clear, predictable snake_case verb_noun pattern with a consistent server prefix. Though there is only one tool, the convention is well-defined and would scale cleanly.
A single tool is extremely thin for a compliance-evidence server, which typically implies writing, querying, and verifying records. One write-only operation cannot cover the apparent scope of the domain.
The surface only supports appending evidence; there is no way to retrieve, search, list, verify, or export logged actions. These gaps would leave an agent unable to confirm or audit what was recorded, a dead end for a compliance workflow.