VerifyAX MCP
OfficialRelated Servers
Alternatives to VerifyAX MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching Verix records, retrieving record details, and running analysis workflows through natural language via the Verix API.MIT

Coval MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to interact with Coval's evaluation platform for launching and monitoring evaluation runs, managing agents and test sets, and retrieving evaluation metrics.188 npm2MIT- AlicenseNot gradedqualityCmaintenanceExposes the full Telnyx API as Model Context Protocol tools and enables deploying autonomous AI voice agents from a YAML spec.MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables AI agents to verify email addresses, clean lists, run bulk verification jobs, and manage a Verifly account through natural language, without writing HTTP calls.150MIT
- FlicenseNot gradedqualityBmaintenanceEnables SQL query execution and knowledge base search via RAG agent through two tools.-
TDQS
Scored across 12 tools
The set cleanly separates three resources (agents, scenarios, runs) plus usage, and list vs get vs delete verbs are clear. The only mild overlap is preview_run_cost vs evaluate_agent, but their descriptions distinguish 'estimate' from 'execute,' so an agent can pick correctly.
Every name is snake_case verb_noun (list_agents, register_agent, evaluate_agent, get_run_details, generate_scenario, etc.). The only stylistic variance is 'register_agent' instead of 'create_agent,' which is still a clear verb and consistent in form.
12 tools is well within the sweet spot for a multi-resource platform (agents, scenarios, runs, billing). Each tool maps to a distinct capability with no filler entries.
Core lifecycle is covered: agents (register/list/delete), scenarios (generate/list/delete), runs (list/get/evaluate), plus cost and usage. Minor gaps remain — no get_agent/get_scenario detail fetch, and no update operations for agents or scenarios — but agents can work around these.