gavel-mcp
Related Servers
Alternatives to gavel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to independently verify an AI agent's completion claim by checking its claimed files, JSON, URLs, and hashes, returning a receipt verdict such as VERIFIED, FAILED, FALSE_DONE, or UNVERIFIABLE.11MIT
- AlicenseNot gradedqualityBmaintenanceFailLoud is a deterministic verification harness for LLM agent outputs — it catches silent failures agents ship as 'done.' Six checks: FL001 placeholder_shipped, FL002 unbacked_claim, FL003 stale_state, FL004 count_mismatch, FL005 missing_components, FL006 unsupported_answer. No LLM in the verdict path. CLI, library, GitHub Action, MCP server (11 tools). MIT.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables spec-driven development acceptance gate with structured receipts, audit logs, and reviewer-ready evidence.-
- AlicenseNot gradedqualityBmaintenanceEnables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables coding agents to submit a public preview URL and acceptance stories for independent QA, returning pass/fail evidence packs with screenshots and supporting human notes on failures.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify claims against evidence through MCP tools, returning approved, rejected, or needs_review verdicts with replayable receipts.MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another. Its purpose is clearly distinct by default.
With a single tool there are no conflicting conventions to penalize. The name gavel_acceptance is clear and follows snake_case, though it is noun-oriented rather than a verb_noun pattern.
One tool is minimal, but the server appears purpose-built for a single acceptance action, so the count is slightly under the typical range yet reasonable for the stated scope.
The tool fully covers the server's apparent purpose: running an acceptance command and returning a mechanical verdict with well-specified exit-code and output handling. No obvious operations are missing for this narrow domain.