evidence-ledger-mcp
Related Servers
Alternatives to evidence-ledger-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server providing an append-only, hash-chained evidence ledger for agent actions, where every record is a tamper-evident receipt cryptographically bound to all prior records and persisted as human-readable JSONL local state. It exposes tools to append records, verify chain integrity (pinpointing tampering), query records by actor/action/target/time, and fetch ledger stats—with no update or delete capabilities by design.1Apache 2.0
- AlicenseBqualityBmaintenanceEnables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.73Apache 2.0
- AlicenseAqualityBmaintenanceFree seven-tool proof loop for MCP agents: scoped sessions, bounded authorization, typed outcomes, evidence-bound claims, and tamper-evident local closure. Upgrade to Complete Local for durable memory, recovery, signed traces, release verification, and multi-agent workflows.7Apache 2.0

operations-pulseofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to run local-first operations checks, review evidence, and manage durable tickets in a SQLite-backed ledger through self-describing MCP tools.MIT- AlicenseNot gradedqualityAmaintenanceProvides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents and gateways to seal each action into a tamper-evident W3C PROV record backed by a signed Merkle transparency log, and to fetch tree heads, inclusion and consistency proofs, verify records, and trace artifact lineage through six typed MCP tools.Apache 2.0
TDQS
Scored across 14 tools
Most tools target distinct lifecycle stages: record operations, ledger creation/validation, export/summary/embedding, and PDF linking. The main potential confusion is between check_ledger and validate_ledger, and between resolve_links and relink_html, but their descriptions clarify different inputs and outputs. An agent can generally select correctly, though a few boundaries require careful reading.
Nearly all tools use a consistent snake_case verb_noun pattern: add_record, find_records, get_record, validate_record, export_ledger, and so on. The only clear deviation is schema_info, which is noun-based rather than verb_noun, but the naming remains predictable overall.
Fourteen tools is well within the expected 3-15 range and fits a complex evidence-ledger workflow that includes record management, validation, export, embedding, and PDF linking. Each tool appears to earn its place without obvious duplicates.
The surface covers ledger creation, record addition, lookup, withdrawal, validation, export, summarizing, embedding, and source linking. The main gap is a direct record update/edit operation, though the append-plus-withdraw model may make this intentional. Overall the lifecycle is substantially covered with minor workarounds.