Coval MCP Server
OfficialRelated Servers
Alternatives to Coval MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an agent to discover and run LLM eval suites against a configured model, inspect saved run scores and failures, and compare two runs item by item with paired intervals, better/worse counts, and noise-floor verdicts.285 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to run evals mid-task, providing tools to validate suites, execute model comparisons, and inspect calibration and win-rate reports.MIT
- AlicenseAqualityCmaintenanceProvides read-only tools to generate test plans for AI agents, score agent runs, and produce reusable evaluation scorecards.3MIT

@avala-ai/mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceLets AI assistants interact with Avala's Physical AI data platform to browse and manage sensor datasets, annotation projects, exports, tasks, and storage connections through tool calls.MIT- AlicenseNot gradedqualityCmaintenanceEnables LLM evaluation and observability by uploading documents, building test sets, running RAG pipelines, and automatically scoring answers for groundedness, hallucination risk, retrieval quality, latency, and cost, with tools exposed to MCP-compatible clients.1MIT

VerifyAX MCPofficial
AlicenseAqualityBmaintenanceEnables conversational access to the VerifyAX agent-evaluation platform, exposing tools for agent evaluation workflows through natural language.141Apache 2.0
TDQS
Scored across 34 tools
Most tools target a clearly distinct resource+action pair (agents, runs, test sets/cases, metrics, personas, reports, schedules), and descriptions make the boundaries readable. There is some crowding around the 'run' family (list_runs, list_run_templates, list_scheduled_runs, get_run, get_scheduled_run) and consult_sofia acts as a read-only catch-all that overlaps with nearly every read tool, which can invite misselection.
Every tool follows a snake_case verb_noun pattern (get_agent, create_test_case, cancel_python_metric_preview, list_scheduled_runs). The only stylistic outliers (read_transcript_export, consult_sofia) still fit the verb_noun convention, so the pattern is predictable throughout.
At 34 tools the surface is heavy for a single evaluation platform, and several tools exist only to support narrow sub-workflows (the four-step python metric draft/preview/publish lifecycle). While each tool has a real function, the set exceeds the 25-tool threshold where scoping starts to feel unwieldy for an agent.
Core create/read/update paths exist for agents, test cases, and schedules, but deletion and some update operations are missing across the board (no delete_agent, delete_test_case, delete_test_set, update_test_set, create/update_persona, delete_report, cancel_run). Metrics and personas are especially thin on the write side, leaving agents with dead ends on cleanup and persona management.