# VIDIA (remote · vidia.kr)

VIDIA AI video production: get quotes, start videos, track progress and download results

- Trust score: 38/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `vidia.kr`: 38/100 (this document), [markdown](https://verifymcp.io/servers/kr-vidia-vidia/vidia.md), [page](https://verifymcp.io/servers/kr-vidia-vidia/vidia)
- npm · `vidia-mcp`: 39/100, [markdown](https://verifymcp.io/servers/kr-vidia-vidia/vidia-mcp.md), [page](https://verifymcp.io/servers/kr-vidia-vidia/vidia-mcp)

## Channel facts

- Endpoint: `https://vidia.kr/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the VIDIA MCP server?

VIDIA is a hosted endpoint at https://vidia.kr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http kr-vidia-vidia 'https://vidia.kr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kr-vidia-vidia": {
      "url": "https://vidia.kr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kr-vidia-vidia": {
      "type": "http",
      "url": "https://vidia.kr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kr-vidia-vidia]
url = "https://vidia.kr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kr-vidia-vidia": {
      "type": "remote",
      "url": "https://vidia.kr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kr-vidia-vidia --url 'https://vidia.kr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kr-vidia-vidia:
    url: "https://vidia.kr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kr-vidia-vidia": {
      "Transport": "http",
      "Url": "https://vidia.kr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kr-vidia-vidia -t streamable-http -u 'https://vidia.kr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kr-vidia-vidia": {
      "type": "http",
      "url": "https://vidia.kr/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 38, 0)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] Transport: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-11-02 (score 38, 0)

- [security regression] Endpoint reachability: behind authorisation → unreachable
- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-10-11 (score 38, −30)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.10 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-09 (score 68, +1)

- [security] Tool “vidia_start_run” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.10
- [cosmetic] “vidia_start_run” reworded the description of “confirm”

### 2026-10-06 (score 67)

First indexed and scored.

## MCP tools (10)

### `vidia_account` (~31 tokens)

내 계정

내 비디아 포인트 잔액·쿠폰·요금제를 확인합니다. 무료입니다.

### `vidia_list_packages` (~134 tokens)

패키지 찾기

영상을 만들 수 있는 발행된 패키지(영상 제작 템플릿)를 찾습니다. 각 패키지의 예상 포인트·작업 시간이 함께 나옵니다. 무료입니다.

Input parameters:

- `format` (string): shorts | longform
- `limit` (integer): 최대 50
- `mix` (string): 결과물 구성: ai-video | mixed | ai-image
- `offset` (integer): 건너뛸 수
- `q` (string): 검색어(제목·설명·태그)
- `sort` (string): popular | recent | completed

### `vidia_get_package` (~64 tokens)

패키지 입력 칸

패키지 한 개의 설명과 입력 칸(inputs)을 봅니다. 견적·제작의 input 은 이 칸의 key 로 채웁니다. 무료입니다.

Input parameters:

- `slug` (string, required): 패키지 slug(vidia_list_packages 결과)

### `vidia_quote` (~203 tokens)

견적 받기

입력값으로 제작 견적(최소·권장 예산 포인트, 예상 비용·장면 계획)을 받습니다. 포인트가 차감되지 않습니다. 견적은 10분 동안 유효하고, 제작은 이 견적의 id 로만 시작할 수 있습니다.

Input parameters:

- `input` (object, required): 입력 칸 key → 값(vidia_get_package 의 inputs)
- `loop_policy` (string): 품질 미달 처리: ACCEPT(기본) | ASK
- `loop_retries` (integer): 품질 미달 시 다시 만들기 횟수(0~5)
- `mode` (string): 진행 방식: AUTO(기본, 끝까지 자동) | MANUAL
- `package` (string, required): 패키지 slug
- `problem_policy` (string): 오류 처리: SKIP(기본) | ASK
- `title` (string): 프로젝트 이름(선택, 160자 이내)

### `vidia_start_run` (~427 tokens)

영상 제작 시작

견적(금액과 rights 의 권리 확인과 책임 안내)을 사용자에게 보여 주고 동의를 받은 뒤에만 부르세요. budget 만큼 포인트를 먼저 잡아 두고 제작을 시작합니다(쓰지 않은 포인트는 끝나면 돌아옵니다). 견적 때와 같은 package·input·설정을 보내야 합니다. "제작 시작 허용" 권한 키가 필요합니다.

Input parameters:

- `budget` (integer, required): 예산 포인트(견적 minimum 이상, 보통 recommended)
- `confirm` (boolean, required): 사용자가 견적 금액과 견적의 rights(권리 확인과 책임 — 권리 문제는 제작 중에 막지 않고, 완성 뒤 확인과 공개·사용의 책임은 사용자에게 있음)를 확인하고 동의했으면 true
- `external_consent` (boolean): 패키지가 외부 서비스로 요청을 보내는 경우(견적의 external), 사용자가 그 전송에 동의했으면 true
- `idempotency_key` (string, required): 같은 요청 재시도 때 중복 제작을 막는 키(영숫자·_·- 8~96자). 요청마다 새로 만들고 재시도 때는 그대로 씁니다.
- `input` (object, required): 견적 때와 같은 입력값
- `loop_policy` (string): 품질 미달 처리: ACCEPT(기본) | ASK
- `loop_retries` (integer): 품질 미달 시 다시 만들기 횟수(0~5)
- `mode` (string): 진행 방식: AUTO(기본, 끝까지 자동) | MANUAL
- `package` (string, required): 패키지 slug
- `problem_policy` (string): 오류 처리: SKIP(기본) | ASK
- `quote_id` (string, required): vidia_quote 결과의 id
- `title` (string): 프로젝트 이름(선택, 160자 이내)
- `use_coupon` (boolean): 제작 쿠폰을 쓸지(선택)

### `vidia_get_run` (~90 tokens)

제작 진행 확인

제작 한 건의 상태(대기·제작 중·완성·실패)·진행 단계·예상 남은 시간을 봅니다. 완성되면 vidia_get_downloads 로 받습니다. 무료입니다. 너무 자주 부르지 말고 30초 이상 간격으로 확인하세요.

Input parameters:

- `run_id` (integer, required): 제작(프로젝트) 번호

### `vidia_list_runs` (~62 tokens)

내 제작 목록

내 제작(프로젝트) 목록을 최근 순으로 봅니다. 무료입니다.

Input parameters:

- `limit` (integer): 최대 50
- `offset` (integer): 건너뛸 수
- `state` (string): 상태로 거르기

### `vidia_cancel_run` (~99 tokens)

제작 취소

진행 중이거나 대기 중인 제작을 취소합니다. 되돌릴 수 없으니 사용자에게 확인을 받은 뒤 부르세요. "제작 시작 허용" 권한 키가 필요합니다.

Input parameters:

- `confirmed` (boolean): 오류로 멈춘 제작을 전액 돌려받고 취소할 때(만든 파일이 지워짐) true
- `run_id` (integer, required): 제작 번호

### `vidia_list_assets` (~110 tokens)

내 자료실 파일

내 자료실 파일(이미지·영상·소리)의 id 를 봅니다. 패키지 입력 칸 중 type 이 asset 인 칸에는 이 id 를 넣습니다(여러 장이면 배열). 파일 올리기는 웹 자료실이나 REST·SDK(POST /api/v1/assets)로 합니다. 무료입니다.

Input parameters:

- `kind` (string): image | video | audio
- `limit` (integer): 최대 200
- `q` (string): 이름 검색

### `vidia_get_downloads` (~66 tokens)

결과물 다운로드 링크

완성된 제작의 결과물(완성 영상·썸네일·자막 등)과 1시간 동안 쓸 수 있는 다운로드 링크, 게시용 제목·설명을 받습니다. 무료입니다.

Input parameters:

- `run_id` (integer, required): 제작 번호

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kr-vidia-vidia/vidia#diagnostics

## Score history

- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 38
- 2026-11-02: 38
- 2026-11-01: 38
- 2026-10-31: 38
- 2026-10-30: 38
- 2026-10-29: 38
- 2026-10-28: 38
- 2026-10-27: 38
- 2026-10-26: 38
- 2026-10-25: 38
- 2026-10-24: 38
- 2026-10-23: 38
- 2026-10-22: 38
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 38
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 38
- 2026-10-15: 38
- 2026-10-14: 38
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-11: 38
- 2026-10-09: 68
- 2026-10-06: 67

## Common questions

### What is the VIDIA MCP server?

VIDIA is an MCP server listed in the public MCP registry as kr.vidia/vidia. VIDIA AI video production: get quotes, start videos, track progress and download results. This page covers its hosted endpoint (https://vidia.kr/mcp).

### Is the VIDIA MCP server safe to use?

VIDIA scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VIDIA MCP server expose?

VIDIA exposes 10 tools: vidia_account, vidia_list_packages, vidia_get_package, vidia_quote, vidia_start_run, and 5 more. Their descriptions and schemas cost roughly 1,286 tokens of context every time the server is loaded.

### Does the VIDIA MCP server require authentication?

Yes. VIDIA asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the VIDIA MCP server still maintained?

VIDIA is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vidia.kr/mcp
- Repository: https://github.com/lead788/vidia-mcp
- Website: https://vidia.kr/help/guide/developer
- Changelog RSS feed: https://verifymcp.io/servers/kr-vidia-vidia/vidia.xml
- Changelog JSON feed: https://verifymcp.io/servers/kr-vidia-vidia/vidia.json
- HTML version of this page: https://verifymcp.io/servers/kr-vidia-vidia/vidia