Evidence MCP
Related Servers
Alternatives to Evidence MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables capturing a tamper-evident, hash-chained local record of every AI agent tool call — both the decision before a tool runs and its outcome — so you can review what the agent actually did in order, detect edits, deletions, or reordering at the exact index, and export a signed evidence pack any third party can verify with no installs.30 PyPI2MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to capture and hash-register browser evidence, enforce cite-or-fail claim checks against registered bytes, and export Merkle-rooted evidence bundles that other agents can re-verify fully offline.10 npm-
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to sign action records locally, publish them to a public log, and retrieve tamper-evident proofs that anyone can verify offline.411 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and manage a Git-native decision ledger, providing tools for querying decisions, evidence, cross-repository workspaces, validation, and commit tracing, all operating locally and without a cloud service.MIT
- AlicenseNot gradedqualityCmaintenanceEnables recording agent proposals, executions, redactions and annotations into an append-only, hash-linked evidence chain, then exporting a self-contained range and verifying offline from the export's own bytes alone so a third party can check history without trusting the agent runtime or its storage.MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct action in the evidence lifecycle: create bundle, capture Git state, snapshot files, record command results, add assertions, verify evidence, and export reports. The closest overlap is capture_git_evidence versus verify_evidence_bundle, but one captures live Git state while the other re-checks stored evidence against the workspace, so the boundary is clear.
All tool names use snake_case with a verb-first pattern: add_assertion, verify_evidence_bundle, export_evidence_report, create_evidence_bundle, capture_git_evidence, record_command_result, and snapshot_files. The convention is consistent throughout, with only natural variation in object length.
Seven tools is well within the ideal range for a focused server and each tool supports a clear stage of the evidence workflow. There are no obviously redundant or filler tools.
The surface covers bundle creation, evidence capture from Git, files, and command results, assertion linking, verification, and report export. Minor gaps remain: there is no list/get operation for existing bundles or stored evidence/assertions, and no update/delete/archive path, which may limit discovery and maintenance for long-lived or multiple bundles.