A
licenseNot graded
qualityB
maintenanceEnables AI agents to submit and manage durable long-form audio transcription jobs, and read or export structured transcripts via MCP tools.
1
MIT
EarSay MCP
Related Servers
Alternatives to EarSay MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-aware agents to queue and run faster-whisper transcription jobs on a shared GPU, with tools to submit audio, poll job status, cancel jobs, and inspect queue status.-
- AlicenseNot gradedqualityBmaintenanceEnables voice-first interactions with AI agents and MCP tools, supporting speech input/output, STT/TTS, and a provider-independent agent core.1MIT
- AlicenseAqualityDmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to access OpenAI-compatible transcription, live ASR, text-to-speech, voice cloning, phoneme recognition, and server-side file staging through streamable HTTP MCP tools.6Do What The F*ck You Want To Public
- AlicenseNot gradedqualityAmaintenanceGive your AI agents the ability to listen. Microphone capture and speech-to-text tools for MCP-compatible agents.488 npm10Apache 2.0
TDQS
A4.4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct action on the transcription service: lifecycle (start/stop/pause/resume), retrieval (full vs. incremental), checkpointing, and status. The only potential overlap between voice_get_new and voice_get_text is clearly resolved by their descriptions (incremental since checkpoint vs. all text). No two tools perform the same operation.
Naming Consistency5/5
All tool names follow the voice_<action> pattern using snake_case consistently. Actions are clear verbs or verb-noun combinations (get_new, set_checkpoint, start, stop, pause, resume). This uniformity makes the set predictable and easy to navigate.
Tool Count5/5
With 8 tools, the set is well-scoped for a transcription server. Each tool fulfills a necessary role in the lifecycle, from initialization to text retrieval and checkpoint management. No tool is redundant or extraneous.
Completeness5/5
The tool surface covers the full lifecycle: start/stop, pause/resume, full and incremental text retrieval, checkpoint setting, and status monitoring. This provides all essential operations for interacting with the EarSay transcription server, with no obvious gaps that would hinder typical workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues