Speak AI vs VocaLingo
Speak AI is an MCP server published by speakai. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). VocaLingo is an MCP server published by umakhanpro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.41.1 Downloads/month (npm): 4 341 Downloads/week (npm): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 1.19.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 1.41.1 Downloads/month (npm): 4 341 Downloads/week (npm): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Speak AI | VocaLingo |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-30 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (nodejs.vocalingo.app/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/speakai/speakai-mcp | github.com/umakhanpro/vocalingo-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-01 |
| Endpoint at the last check (differs) | Status out of date: last check 42 h ago returned HTTP 401 | Responded 6 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Speak AI
Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.
VocaLingo
Video summaries, voice message transcription and translation in the same voice, your own voice TTS
How to run each
Speak AI As a remote MCP server
claude mcp add --transport http speak-ai https://api.speakai.co/v1/mcp
Requires: SPEAK_API_KEY (secret)
VocaLingo As a remote MCP server
claude mcp add --transport http vocalingo https://nodejs.vocalingo.app/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of VocaLingo publish no settings it asks for, so we do not compare settings.
What it can do: Speak AI · What it can do: VocaLingo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.