Skip to main content
Glama
evidence-readiness

io.github.BrienBounded/evr

by evidence-readiness
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.BrienBounded/evr

No user-submitted related servers found.

    Related Servers

    • ProofGate

      yuzhiyang1
      A
      license
      Not graded
      quality
      C
      maintenance
      Evidence-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

    • flameox

      morluto
      A
      license
      C
      quality
      A
      maintenance
      Enables coding agents to query, compare, and audit local profiler traces, benchmarks, memory captures, and execution evidence without uploading code or data, using CLI and MCP interfaces.
      111
      121
      MIT

    • AgentInspect MCP Server

      rajudandigam
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only local MCP server for inspecting AgentInspect TypeScript AI-agent traces. Lists runs, exposes bounded causal-failure and TraceFacts evidence, evaluates TraceContract checks, compares runs, and creates share-checked evidence without mutating traces or invoking agent tools.
      6,644
      593
      MIT

    • CodexPro Runtime

      Menglook
      A
      license
      B
      quality
      B
      maintenance
      A local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.
      33
      MIT

    • agent-eval-gate

      dxwss
      A
      license
      Not graded
      quality
      C
      maintenance
      Serves MCP tools to inspect agent trace JSONL files and evaluate them against golden-case constraints, returning structured metrics and gate results.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources