io.github.chicogong/ffvoice
io.github.chicogong/ffvoice
Is the io.github.chicogong/ffvoice MCP server down? Yes. It has given no valid answer since 2026-10-16: install failed.
Offline speech-to-text & speaker diarization MCP server: transcribe audio on-device, no cloud
install failed down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-30
subprocess.CalledProcessError: Command '['cmake', '/root/.cache/uv/sdists-v10/pypi/ffvoice/0.8.3/9lTkTEuDqfBOjddG/src', '-DCMAKE_LIBRARY_OUTPUT_DIRECTO
- Run it
- uvx ffvoice@0.8.3 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/chicogong/ffvoice-engine
- Registry
- active, updated 2026-05-19 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- LegendKeeper io.github.chase-roohms/legendkeeper-mcp · alive
- io.github.chenxiaofie/memory-mcp · crashed on start
- io.github.chernistry/bernstein · timeout
- vibeMK io.github.chexma/vibemk · alive
- indiebiz-evidence io.github.chilayt/indiebiz-evidence · crashed on start
- io.github.chinwe/compound-memory · needs args
- Chipzen io.github.chipzen-ai/chipzen-mcp · needs env
- Korea Data Suite io.github.choiyounggi/korea-data-mcp · needs mcp<2
Servers that mention diarization or transcribe.
- QuillHub ai.quillhub/mcp · needs auth
- Uttera ai.uttera/uttera · needs auth
- Weftly ai.weftly/weftly · alive
- co.pepys/pepys-mcp · needs auth
- AI-Translators com.ai-translators.www/ai-translators · needs auth
- Shorty com.aishorty/shorty · needs auth
- FieldTranscript com.fieldtranscript/transcriber · alive
- Voibe com.getvoibe/transcription · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-16, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.