F
licenseA
qualityD
maintenanceEnables autonomous prompt improvement for voice AI agents through feedback analysis, test generation, and iterative testing.
10
-
standard-vocal-mcp
Related Servers
Alternatives to standard-vocal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables evidence-first regression testing for AI agents by turning production traces into reviewed, replayable cases that gate releases. It supports reproducible, auditable agent evaluation with controlled tool execution, evidence-based judging, and versioned quality gates.MIT
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5810 npm1MIT
movoice-mcpofficial
AlicenseAqualityCmaintenanceCreate and manage voice AI agents using natural language from Claude Desktop or Cursor. Enables agent creation, listing, updating, deletion, and viewing call logs.78 npmMIT- AlicenseAqualityAmaintenanceProvides coding agents with visibility into test health through tools for flaky test detection, test quality linting, and LLM evaluation harness, enabling them to triage failures, review test quality, and check prompt changes for regressions.9Apache 2.0
Pinecall MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables coding agents to build, test, and deploy production voice agents with real phone numbers directly from the editor, including live call monitoring and sandboxed development.23 npmMIT
TDQS
A3.6/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct responsibility: listing, deploying, evaluating, analyzing audio, diffing prompts, and gating regressions. Even run_eval and regression_gate are clearly separated, with the former generating scores and the latter comparing against a baseline.
Naming Consistency2/5
The first three tools follow a verb_noun pattern (list_agents, deploy_agent, run_eval), while the last three are noun-centric (audio_forensics, prompt_diff, regression_gate). This split in grammatical structure makes the naming convention inconsistent and harder to predict.
Tool Count5/5
Six tools is well-scoped for a specialized server focused on voice agent lifecycle and evaluation. Every tool earns its place, and the count is neither too small nor bloated.
Completeness4/5
The set covers the core workflow: discover agents, deploy new ones, run tests, analyze call audio, version prompts, and gate updates. Minor gaps include no delete_agent or direct update_agent, but these are not critical for the server's apparent purpose.
Maintenance
ActivitySlowing
ResponsivenessNo issues