VIDIA
REMOTE · VIDIA.KR · 2 COMPONENTS
VIDIA AI video production: get quotes, start videos, track progress and download results
Available components
Last scanned (22 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- 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. functional
- 2 Nov 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- 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. security
- 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. functional
- 11 Oct 26 −30
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +1
- Tool “vidia_start_run” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.10 ▲ functional
- “vidia_start_run” reworded the description of “confirm” cosmetic
- 6 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://vidia.kr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vidia.kr | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6492e6cd975c318f1a97e7e92c1bbcaa903 |
| SANs: vidia.kr | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vidia.kr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| kr. | present | 64641 | 13 | Verified |
| vidia.kr. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="vidia", resource_metadata="https://vidia.kr/.well-known/oauth-protected-resource"
Bearer realm="vidia", resource_metadata="https://vidia.kr/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self' https://pay.nicepay.co.kr; object-src 'none'; frame-ancestors 'self'; img-src 'self' data: blob: https://cdn.jsdelivr.net https://www.google.com https://www.google.co.kr https://googleads.g.doubleclick.net https://ad.doubleclick.net https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; media-src 'self' blob:; font-src 'self' data: https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://accounts.google.com/gsi/style; script-src 'nonce-DLZwUPCw+u4cpK4PngWrpA==' 'self' https://cdn.jsdelivr.net https://accounts.google.com https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pay.nicepay.co.kr; connect-src 'self' https://accounts.google.com https://www.google.com https://www.google.co.kr https://www.googleadservices.com https://googleads.g.doubleclick.net https://ad.doubleclick.net https://www.googletagmanager.com https://*.goo |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer realm="vidia", resource_metadata="https://vidia.kr/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://vidia.kr/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://vidia.kr/mcp |
| Authorisation server | https://vidia.kr |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vidia.kr/mcp | Auth required | 401 | |
| http (plaintext) | http://vidia.kr/mcp | HTTPS enforced | 308 | https://vidia.kr/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vidia_account 내 계정 ~31
내 비디아 포인트 잔액·쿠폰·요금제를 확인합니다. 무료입니다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vidia_cancel_run 제작 취소 ~99
진행 중이거나 대기 중인 제작을 취소합니다. 되돌릴 수 없으니 사용자에게 확인을 받은 뒤 부르세요. "제작 시작 허용" 권한 키가 필요합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | 오류로 멈춘 제작을 전액 돌려받고 취소할 때(만든 파일이 지워짐) true |
| run_id | integer | yes | 제작 번호 |
No output schema declared.
No examples provided.
vidia_get_downloads 결과물 다운로드 링크 ~66
완성된 제작의 결과물(완성 영상·썸네일·자막 등)과 1시간 동안 쓸 수 있는 다운로드 링크, 게시용 제목·설명을 받습니다. 무료입니다.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | 제작 번호 |
No output schema declared.
No examples provided.
vidia_get_package 패키지 입력 칸 ~64
패키지 한 개의 설명과 입력 칸(inputs)을 봅니다. 견적·제작의 input 은 이 칸의 key 로 채웁니다. 무료입니다.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 패키지 slug(vidia_list_packages 결과) |
No output schema declared.
No examples provided.
vidia_get_run 제작 진행 확인 ~90
제작 한 건의 상태(대기·제작 중·완성·실패)·진행 단계·예상 남은 시간을 봅니다. 완성되면 vidia_get_downloads 로 받습니다. 무료입니다. 너무 자주 부르지 말고 30초 이상 간격으로 확인하세요.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | 제작(프로젝트) 번호 |
No output schema declared.
No examples provided.
vidia_list_assets 내 자료실 파일 ~110
내 자료실 파일(이미지·영상·소리)의 id 를 봅니다. 패키지 입력 칸 중 type 이 asset 인 칸에는 이 id 를 넣습니다(여러 장이면 배열). 파일 올리기는 웹 자료실이나 REST·SDK(POST /api/v1/assets)로 합니다. 무료입니다.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | image | video | audio |
| limit | integer | – | 최대 200 |
| q | string | – | 이름 검색 |
No output schema declared.
No examples provided.
vidia_list_packages 패키지 찾기 ~134
영상을 만들 수 있는 발행된 패키지(영상 제작 템플릿)를 찾습니다. 각 패키지의 예상 포인트·작업 시간이 함께 나옵니다. 무료입니다.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | shorts | longform |
| limit | integer | – | 최대 50 |
| mix | string | – | 결과물 구성: ai-video | mixed | ai-image |
| offset | integer | – | 건너뛸 수 |
| q | string | – | 검색어(제목·설명·태그) |
| sort | string | – | popular | recent | completed |
No output schema declared.
No examples provided.
vidia_list_runs 내 제작 목록 ~62
내 제작(프로젝트) 목록을 최근 순으로 봅니다. 무료입니다.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 최대 50 |
| offset | integer | – | 건너뛸 수 |
| state | string | – | 상태로 거르기 |
No output schema declared.
No examples provided.
vidia_quote 견적 받기 ~203
입력값으로 제작 견적(최소·권장 예산 포인트, 예상 비용·장면 계획)을 받습니다. 포인트가 차감되지 않습니다. 견적은 10분 동안 유효하고, 제작은 이 견적의 id 로만 시작할 수 있습니다.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | 입력 칸 key → 값(vidia_get_package 의 inputs) |
| loop_policy | string | – | 품질 미달 처리: ACCEPT(기본) | ASK |
| loop_retries | integer | – | 품질 미달 시 다시 만들기 횟수(0~5) |
| mode | string | – | 진행 방식: AUTO(기본, 끝까지 자동) | MANUAL |
| package | string | yes | 패키지 slug |
| problem_policy | string | – | 오류 처리: SKIP(기본) | ASK |
| title | string | – | 프로젝트 이름(선택, 160자 이내) |
No output schema declared.
No examples provided.
vidia_start_run 영상 제작 시작 ~427
견적(금액과 rights 의 권리 확인과 책임 안내)을 사용자에게 보여 주고 동의를 받은 뒤에만 부르세요. budget 만큼 포인트를 먼저 잡아 두고 제작을 시작합니다(쓰지 않은 포인트는 끝나면 돌아옵니다). 견적 때와 같은 package·input·설정을 보내야 합니다. "제작 시작 허용" 권한 키가 필요합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | yes | 예산 포인트(견적 minimum 이상, 보통 recommended) |
| confirm | boolean | yes | 사용자가 견적 금액과 견적의 rights(권리 확인과 책임 — 권리 문제는 제작 중에 막지 않고, 완성 뒤 확인과 공개·사용의 책임은 사용자에게 있음)를 확인하고 동의했으면 true |
| external_consent | boolean | – | 패키지가 외부 서비스로 요청을 보내는 경우(견적의 external), 사용자가 그 전송에 동의했으면 true |
| idempotency_key | string | yes | 같은 요청 재시도 때 중복 제작을 막는 키(영숫자·_·- 8~96자). 요청마다 새로 만들고 재시도 때는 그대로 씁니다. |
| input | object | yes | 견적 때와 같은 입력값 |
| loop_policy | string | – | 품질 미달 처리: ACCEPT(기본) | ASK |
| loop_retries | integer | – | 품질 미달 시 다시 만들기 횟수(0~5) |
| mode | string | – | 진행 방식: AUTO(기본, 끝까지 자동) | MANUAL |
| package | string | yes | 패키지 slug |
| problem_policy | string | – | 오류 처리: SKIP(기본) | ASK |
| quote_id | string | yes | vidia_quote 결과의 id |
| title | string | – | 프로젝트 이름(선택, 160자 이내) |
| use_coupon | boolean | – | 제작 쿠폰을 쓸지(선택) |
No output schema declared.
No examples provided.
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.
remote · vidia.kr
claude mcp add --transport http kr-vidia-vidia 'https://vidia.kr/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.