io.github.datumline/agent-guard
OfficialRelated Servers
Alternatives to io.github.datumline/agent-guard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify claims against evidence through MCP tools, returning approved, rejected, or needs_review verdicts with replayable receipts.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to submit AI agent claims for verification, read verdicts, and fetch or offline-verify signed receipts.735 npm2Apache 2.0
- AlicenseAqualityCmaintenanceEnables agents and clients to fact-check factual claims against live web sources, returning citable verdicts with source details and cryptographically signed receipts for downstream verification.1102 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and orchestrators to deterministically verify sub-agent outputs inside the loop, catching placeholders, unbacked claims, stale state, count mismatches, and missing components before acting on claimed completion. It also supports failure reports and hash-chained verification receipts.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.MIT
- AlicenseNot gradedqualityBmaintenanceEnables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.4 npmApache 2.0
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing it with another operation. Its purpose is clearly scoped to verifying an agent's completion claim against artifacts.
The single tool name follows a clear verb_noun convention: verify_completion_claim. With only one tool there are no conflicting naming styles or inconsistent patterns.
The server has a very narrow purpose, so one focused tool is defensible, but a single-tool surface is thin for an MCP server. It lacks companion operations such as listing or retrieving prior verification receipts.
The tool covers several artifact types and clear verdicts, which addresses the core verification workflow well. Minor gaps remain around receipt retrieval, history, or manifest management, but agents can work around them.