Home / MCP registry index / io.sudio/studio
Sudio
io.sudio/studio in the official MCP registry.
Endpoint https://sudio.io/mcp.
The registry describes it as: The AI video studio: records your web app, writes and voices the script, renders a tutorial MP4.
On 2026-10-21 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-sudio-studio)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| BlitzReels Video Editor com.blitzreels/blitzreels | 140 tools, nothing matched 2026-10-22 |
| ai.switchapp/switch ai.switchapp/switch | 113 tools, nothing matched 2026-10-22 |
| CueFrame ai.cueframe/cueframe | 92 tools, nothing matched 2026-10-21 |
| Dock ai.trydock/dock | 81 tools, nothing matched 2026-10-22 |
| Streamloop io.github.streamloop/mcp | 67 tools, nothing matched 2026-10-21 |