loopgrid-mcp
Related Servers
Alternatives to loopgrid-mcp
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityCmaintenanceEnables preserving, querying, and managing engineering decisions with reasoning and evidence through CLI, HTTP API, and MCP tools.16-
- AlicenseNot gradedqualityDmaintenanceEvidence-first delivery audit MCP server that evaluates task requirements against delivery evidence and returns a reproducible pass/needs_review/fail decision with a deterministic receipt.MIT
- AlicenseAqualityAmaintenanceEnables agents to create, append to, search, validate, withdraw, export, and summarize JSON Lines evidence ledgers through MCP tools, including full, masked, or locator exports and printable HTML summaries.14MIT
- 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
- AlicenseAqualityDmaintenanceTamper-evident audit logging for AI decisions. Three tools (record_decision, verify_decision, list_decisions) write to a regulator-grade ledger built on AWS S3 Object Lock with 7-year retention. Designed for EU AI Act Article 12 and FCA SS1/23 evidence requirements. Try zero-config: npx audit-ledger-mcp boots in sandbox mode against a public hosted tenant.331 npm1Apache 2.0
TDQS
Scored across 6 tools
Each tool targets a distinct stage in the evidence lifecycle: decision, review, action, outcome, retrieval, and verification. The descriptions clearly separate recording evidence from executing actions, so there is no real ambiguity between tools.
All tool names follow a consistent snake_case verb_noun pattern with a uniform loopgrid. prefix. The record_* tools form a clear family, while get_evidence and verify_evidence follow the same predictable convention.
Six tools is well-scoped for a focused governance/evidence server. Each tool earns its place and covers a necessary function without redundancy or bloat.
The tool set covers the full evidentiary workflow: capture decisions, record reviews, log actions, record outcomes, retrieve portable evidence, and verify integrity. There are no obvious dead ends for the stated purpose.