8-step hybrid-attention video + soundtrack, MiniMax-H3
- Remote endpoint
- 3 tools
Uptime
Checked · every day
100%from 10 days of checks
Up without downtime on 9 of 9 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1140 ms, slowest 5% 1281 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
3 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 9 Nov (today) | No verdict yet | 0 | – |
| 8 Nov | No downtime | 1of 1 | 1138 ms |
| 7 Nov | No downtime | 1of 1 | 1252 ms |
| 6 Nov | No downtime | 1of 1 | 1151 ms |
| 5 Nov | No downtime | 1of 1 | 1198 ms |
| 4 Nov | No downtime | 1of 1 | 1122 ms |
| 3 Nov | No downtime | 1of 1 | 1200 ms |
| 2 Nov | No downtime | 1of 1 | 1127 ms |
| 1 Nov | No downtime | 1of 1 | 1194 ms |
| 31 Oct | No downtime | 2 | 1192 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse vdn-h3 https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"vdn-h3": {
"type": "sse",
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"vdn-h3": {
"type": "sse",
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "vdn-h3"
type: sse
url: "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"vdn-h3":
type: streamable_http
name: "vdn-h3"
enabled: true
uri: "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add vdn-h3 --url https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server VDN-H3 (`co.huggingface.mrfakename/vdn-h3`)
Its page: https://plug.directory/servers/co.huggingface.mrfakename/vdn-h3
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse vdn-h3 https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"vdn-h3": {
"type": "sse",
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"vdn-h3": {
"type": "sse",
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "vdn-h3"
type: sse
url: "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"vdn-h3": {
"url": "https://mrfakename-vdn-h3.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 3
VDN_H3_generateGenerate a 1344x768 video with a synchronised soundtrack from a text prompt. Returns: A tuple of the path to the generated MP4 (H.264 video + AAC audio) and a Markdown, line reporting the measured GPU timings.VDN_H3_generate_conditionedGenerate from a Qwen3-VL conditioning file produced by the companion conditioner Space. This endpoint exists for browser clients that can authenticate both ZeroGPU calls as the signed-in visitor. It avoids making an anonymous server-to-server conditioner request, which otherwise receives only the Space owner's tiny unauthenticated quota and fails before VDN ever reaches its GPU worker. If a user passes a file as an input, use the upload_file_to_gradio tool, if present, to upload the file to the gradio app and create a Gradio File Input. Then use the returned path as the input to the toolVDN_H3_generate_conditioned_b64Generate from inline conditioning bytes, bypassing Gradio's remote-file downloader. Cross-Space FileData URLs can be scoped to the caller's browser identity. Gradio otherwise asks this Space to download that URL during input preprocessing, where it has no caller cookie and receives HTTP 403. An inline payload is small (only the prompt tokens), deterministic, and reaches the function without URL normalization.
From Hugging Face Spaces. Report a problem