io.github.umakhanpro/vocalingo
VocaLingo
Is the VocaLingo MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-01.
Video summaries, voice message transcription and translation in the same voice, your own voice TTS
needs auth probed 2026-11-02 · unchanged since 2026-11-01 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Unauthorized: sign in via OAuth, or send your VocaLingo MCP- Endpoint
- https://nodejs.vocalingo.app/mcp (streamable-http)
- Host
- nodejs.vocalingo.app
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://nodejs.vocalingo.app/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server glsgoemxkhlyushacmcm.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Scopes email.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/umakhanpro/vocalingo-mcp
- Website
- https://vocalingo.app
- Registry
- active, updated 2026-11-01 · registry entry
Compare this server with others.
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
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.