io.github.zsthimself/open-video-generator-mcp
OpenVideoGenerator MCP Server
Is the OpenVideoGenerator MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
AI video generation MCP server for Kling, MiniMax, Luma & Hunyuan with prompt blueprints.
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32002,"message":"Authorization required. Provide Bearer API key in header: \- Endpoint
- https://openvideogenerator.com/api/mcp (streamable-http)
- Host
- openvideogenerator.com
- Getting access
- A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://openvideogenerator.com/api/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/zsthimself/open-video-generator-mcp
- Website
- https://openvideogenerator.com
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention generator.
- ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/elasticsearch-redis-mysql-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- ai.getvda/kafka-minio-redis-stack-generator · newer protocol
- ai.getvda/kafka-redis-minio-stack-generator · newer protocol
- ai.getvda/memcached-mongodb-redis-compose-generator · newer protocol
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.