Skip to main content
Glama
Sign In
iris-eval/mcp-server

iris-eval/mcp-server

by iris-eval
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to iris-eval/mcp-server

No user-submitted related servers found.

    Related Servers

    • guardrails-mcp-server

      ExpertVagabond
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.
      80 npm
      1
      MIT

    • mcp-context-inspector

      sohaibsohail98
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.
      8
      3
      MIT

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      2
      MIT

    • runmeter

      Aptica-Solutions
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that provides cost and reliability observability for LLM and agent workflows. It records model calls and allows querying and aggregating telemetry data through MCP tools.
      6
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Three evaluation entry points (evaluate_output, evaluate_with_llm_judge, evaluate_runs) and two comparison tools (compare_runs, compare_traces) superficially overlap, but each description states its scope and an explicit 'when not to use it' that routes to the sibling. The only genuinely soft boundary is compare_runs vs compare_traces (cross-run regression vs per-case reliability), which a careful agent can still resolve from the descriptions.

    Naming Consistency4/5

    Nearly everything follows verb_noun snake_case (log_trace, delete_trace, deploy_rule, list_rules, compare_runs, evaluate_output). Minor deviations: get_traces uses 'get' where the equivalent read for rules is 'list_rules', and evaluate_with_llm_judge is a long outlier pattern. Readable and predictable overall.

    Tool Count5/5

    12 tools for an eval/observability server: traces (log/get/delete), rules (deploy/list/delete-toggle), evaluation (deterministic/LLM/re-run), analysis (compare runs/traces), and citation verification. Each tool occupies a distinct slot with no filler.

    Completeness4/5

    Trace lifecycle, rule lifecycle (create/replace/disable/enable/delete), evaluation, and regression analysis are all covered; immutability and replace-via-deploy are documented rather than gaps. Minor gaps: no list_runs or run-listing tool (run ids must be discovered through get_traces), and data retention/export is only reachable via configuration, not a tool.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources