CustoVox MCP servers
Related Servers
Alternatives to CustoVox MCP servers
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables analysis of acoustic vocal emotion, prosodic valence, and customer frustration from audio inputs through a zero-dependency MCP server.1-
- AlicenseNot gradedqualityDmaintenanceA robust MCP server for real-time sentiment analysis with AI-powered insights, featuring multi-dimensional emotion detection, batch processing, and a Gradio web interface.3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables aspect-level sentiment mining of customer reviews, producing satisfaction radar breakdowns and structured sentiment analysis through MCP-compatible clients.-
- AlicenseNot gradedqualityBmaintenanceLocal 395M decision model as an MCP server: pick one option from a list or answer yes/no about text, or run a recipe over a CSV, XLSX or folder. Runs offline. Apache-2.0.1Apache 2.0
- AlicenseBqualityCmaintenanceContent moderation and profanity detection MCP server with 19 tools, 24 language support, leetspeak/Unicode obfuscation detection, context-aware analysis, batch processing, and user tracking for AI-powered content safety.22421 npm69MIT
- FlicenseNot gradedqualityBmaintenanceLocal GGUF vision-language models behind one MCP server: captioning, visual question answering, object detection/pointing, gaze estimation and video classification, all on-device with no cloud API. Bundles a 403 MB SmolVLM so it works with nothing mounted.4-
TDQS
Scored across 4 tools
Each tool has a distinct role: analyze_call writes/ingests, get_call_insights aggregates, search_feedback does sentence-level lookup, and suggest_actions derives recommendations for one call. The main soft spot is that suggest_actions implicitly requires a call already analyzed by analyze_call (and a call id), and get_call_insights vs search_feedback both report on past calls, though their granularity is clearly described.
All four names follow a clean verb_noun snake_case pattern: analyze_call, get_call_insights, search_feedback, suggest_actions. The verb choice also signals intent well (analyze=write, get=read aggregate, search=lookup, suggest=derive), with no style mixing.
Four tools is a tight, well-scoped surface for a local call-analytics server, and each tool earns its place. It sits at the low end of the ideal range, with no explicit list/get-calls tool to round it out.
Core flow (analyze → aggregate → search → suggest) is covered, but there is no way to fetch a single stored call's analysis by id, nor to delete/re-analyze a call, which matters for a local database-backed tool. Agents must rely on aggregate or search results to recover call ids.