Home / MCP registry index / com.vidarostudio/mcp

Vidaro Studio

com.vidarostudio/mcp in the official MCP registry. Endpoint https://api.vidarostudio.com/mcp.

The registry describes it as: Generate AI images and videos via OAuth; uses your Vidaro credits.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http vidarostudio https://api.vidarostudio.com/mcp

{
  "mcpServers": {
    "vidarostudio": {
      "url": "https://api.vidarostudio.com/mcp"
    }
  }
}

code --add-mcp '{"name":"vidarostudio","type":"http","url":"https://api.vidarostudio.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_models get_model get_credits claim_daily_credits import_media_from_url list_uploads estimate_cost generate_image generate_character_sheet generate_video list_genjutsu_templates get_genjutsu_template generate_from_genjutsu_template check_generation my_creations create_upload_link check_upload_link

Tool changes

This server changed its tools after we first read them. If you approved it before the latest change, what you approved is not what it serves now: read its tools again.

• Between 2026-11-06 and 2026-11-09 it changed what these tools say: estimate_cost, generate_video.

Fingerprint of its tools at our last full read (2026-11-09): a7ac810961505f27. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-vidarostudio-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-vidarostudio-mcp)

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. How tool poisoning works. What we found across the registry. Check another server.

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

YouTube and video MCP servers