peacelingo-stt-bench
Related Servers
Alternatives to peacelingo-stt-bench
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceProvides ten hosted audio AI tools — TTS, voice cloning, music generation, stem separation, speaker separation, transcription, denoising, media conversion, and job polling — over a single streamable-HTTP endpoint for any MCP-capable agent.MIT- AlicenseAqualityAmaintenanceEnables AI coding agents to synthesize and play concise spoken summaries of their work through multiple TTS providers, including Azure, OpenRouter, OpenAI, Gemini, ElevenLabs, and local OpenAI-compatible endpoints. It also lets agents stop playback on demand and check which provider, voice, and audio bridge are currently active.31MIT
- AlicenseAqualityBmaintenanceEnables AI agents to generate speech using Gemini TTS models, with tools for text-to-speech, task polling, and pricing checks.445 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables voice-first interactions with AI agents and MCP tools, supporting speech input/output, STT/TTS, and a provider-independent agent core.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check whether generated audio matches a prompt in any language, rank takes, run technical QC, judge fit against images or video, and search or dedupe a local sound library. Each tool returns the same JSON records as the matching CLI command, with the model loaded once and everything running locally.Apache 2.0

VoiceLab MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to use speech AI capabilities including LLM chat completions, text-to-speech in Uzbek, Russian, and English, speech-to-text transcription with speaker labels, voice isolation for noise removal, and realtime WebSocket streaming.MIT
TDQS
Scored across 3 tools
The three tools have largely distinct purposes: list_providers is introspection, estimate_cost is a pure price calculation, and compare_stt runs an actual benchmark. There is minor overlap since compare_stt also returns estimated cost per provider, but the descriptions make clear it requires a real clip while estimate_cost is a duration-only calculation.
All three names follow a clean verb_noun snake_case pattern (compare_stt, list_providers, estimate_cost) with no convention mixing. The abbreviation 'stt' is consistent with the server domain.
Three tools is on the lean side but each earns its place for a focused STT benchmarking server (run comparison, inspect providers, estimate cost). It is slightly thin but well-scoped rather than padded.
Core workflows are covered, but notable gaps exist: there is no tool to list available clips in the repo, no way to retrieve or persist past benchmark results, and no configuration/key management surface. Agents can work around these but the surface feels incomplete for a benchmark tool.