CTM VoiceAI MCP
Related Servers
Alternatives to CTM VoiceAI MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables crash-testing chatbots and AI agents from MCP clients by running multi-level audits and returning actionable reports with exact prompt improvements.434 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to perform authorized web security assessments through MCP tools and a guided review prompt, including passive and full scans, WAF detection, remediation fixes, report export, triage, scan comparison, and proof-of-control verification.1266 PyPI5MIT
- AlicenseNot gradedqualityCmaintenanceLets any MCP client, such as Claude, browse attack suites and probes, run a full assurance assessment with all reports written out, send custom prompts or multi-turn histories and get leak, PII and refusal checks back for adaptive attacks, and read findings from an earlier assessment. This enables agent-driven red-teaming of a chatbot, RAG app or AI agent without leaving the chat client.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to inspect AI search visibility across ChatGPT, Perplexity, Gemini, Copilot, and Google AI Overviews, including prompt rankings, citation and missing-source data, brand snippets, competitor benchmarks, and scan status.MIT
- AlicenseAqualityBmaintenanceLets an MCP client check whether an ecommerce store can be read by AI assistants, auditing robots.txt to see which AI search versus training crawlers are blocked and sampling product pages to confirm structured data and facts survive in raw HTML without JavaScript. It can also generate a training-only opt-out robots.txt that leaves answer-engine crawlers allowed, all inside the conversation the user is already in.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT-compatible MCP clients and OpenAI agents to run static HTML audits, analyze Search Console exports, and perform opt-in bounded same-origin crawling with explicit review queues and portable reports.MIT
TDQS
Scored across 11 tools
The read/fetch tools (get_calls, get_voice_bots, list_runs, run_status, write_report) each map to a distinct step of the review flow, and step numbering in descriptions helps. The weak spot is the six auth tools: ctm_voiceai_configured vs ctm_voiceai_auth_status both report storage/state, and auth_login (device flow) vs auth_url+auth_exchange (web flow) are two paths to the same goal, which invites misselection.
All names share the ctm_voiceai_ prefix and snake_case, but the internal ordering mixes conventions: verb-first (list_runs, get_calls, write_report) alongside resource-first (auth_status, auth_exchange, auth_url, run_status). ctm_voiceai_configured breaks the pattern further by using a past-tense adjective with no verb.
11 tools is a sensible size for an OAuth plus review-and-report workflow, and each tool does earn a slot. It is slightly top-heavy, though, with 6 of 11 tools devoted to authentication while the actual analysis flow gets 5.
The surface covers the full auth lifecycle (url/exchange/login/logout/status/configured) plus run listing, run status, agent and call retrieval, and report writing, so an agent can complete the review loop end to end. Minor gaps: no explicit run-start trigger or date-range filtering on get_calls, but these are workable around via the batch plan.