io.github.BrienBounded/evr
Related Servers
Alternatives to io.github.BrienBounded/evr
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to verify claims against evidence, generate and validate tamper-evident receipts, and pre-filter prompt-injection attempts through stdio JSON-RPC tools.5Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP developers to trace conclusions back to supporting observations by checking evidence integrity and graph references while exposing redacted evidence metadata over stdio.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables agents to gather bounded, reproducible runtime evidence by coordinating local profilers, benchmark tools, and trace processors against explicit artifacts or captured commands. It exposes typed analysis and capture operations over MCP that return provenance-tracked results inline, with optional durable preservation and replay of prior evidence.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to check acceptance evidence against a specification and JUnit results, and to review structured AI proposals for current contract hash, coverage, and in-scope paths. Both tools are read-only, idempotent, content-based, and require no model credentials or filesystem access.MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to run bounded local profiling, benchmarking, and trace analysis on explicit artifacts or commands, returning typed evidence with provenance, coverage, limitations, and recovery actions. It also exposes optional evidence preservation and inspection through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to coordinate local profilers, benchmark tools, trace processors, and explicit targets into bounded runtime evidence, including observed inputs, execution provenance, typed findings, coverage, and limitations. It supports analysis and capture through named MCP tools without workspace setup or project configuration.-
TDQS
Scored across 3 tools
The three tools are largely distinct: check_trace_readiness evaluates a trace, get_requirement fetches a single requirement by ID, and list_class_requirements enumerates requirements for a class. The two retrieval tools overlap slightly in purpose, but their ID-vs-class parameters clearly separate them.
All three names follow a clean snake_case verb_noun pattern (check_trace_readiness, get_requirement, list_class_requirements), with verbs matching the operation. No mixed conventions.
Three tools is a bit lean but well-matched to a narrow read-only spec-inspection purpose. Each tool has a distinct role, though a broader server might warrant a tool to enumerate classes or list all requirements.
The surface covers the core lifecycle: evaluate a trace, look up a requirement, and list requirements per class (including 'universal'). Since the domain is inherently read-only, no create/update/delete is needed; only minor gaps like a global enumeration exist.