Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Viddler

REMOTE · MCP.VIDDLER.COM · SCANNED SEP 27

Official Viddler MCP: list videos, manage access control, pull proof-of-viewing analytics.

Available components

0 this week 74 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 868 tokens (~72/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "viddler_access_remove_password" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Viddler MCP server?

Viddler is a hosted endpoint at https://mcp.viddler.com/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 · mcp.viddler.com

# add to Claude Code
claude mcp add --transport http com-viddler-viddler-mcp 'https://mcp.viddler.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-viddler-viddler-mcp": {
      "url": "https://mcp.viddler.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-viddler-viddler-mcp": {
      "type": "http",
      "url": "https://mcp.viddler.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-viddler-viddler-mcp]
url = "https://mcp.viddler.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-viddler-viddler-mcp": {
      "type": "remote",
      "url": "https://mcp.viddler.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-viddler-viddler-mcp --url 'https://mcp.viddler.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-viddler-viddler-mcp:
    url: "https://mcp.viddler.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-viddler-viddler-mcp": {
      "Transport": "http",
      "Url": "https://mcp.viddler.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-viddler-viddler-mcp -t streamable-http -u 'https://mcp.viddler.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-viddler-viddler-mcp": {
      "type": "http",
      "url": "https://mcp.viddler.com/mcp"
    }
  }
}

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

Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Sept 26 0
    • Tool “viddler_videos_create_upload” rewrote its description, which is the text the model reads security
    • “viddler_videos_create_upload” added an optional parameter “file_size_bytes” cosmetic
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 27 Sept 2026 · Probed https://mcp.viddler.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=viddler.com CN=WE1,O=Google Trust Services,C=US 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA256 16b0a51ff2ee3f8c0e88eb94c0ca554e
SANs: viddler.com, mcp.viddler.com, *.mcp.viddler.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.viddler.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
viddler.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.viddler.com/mcp Verified 200
http (plaintext) http://mcp.viddler.com/mcp Inconclusive 405
MCP tools · 12 exposed · ~868 tokens

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 →

Tool Tokens
viddler_access_remove_password ~49

Turn off password protection for a video. Reverts to the public playback id so the video plays without a password again.

NameTypeReqDescription
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_access_set_custom_url ~61

Give a video a branded, human-friendly custom URL slug for sharing. Returns the updated video.

NameTypeReqDescription
custom_urlstringyesThe desired URL slug (must be unique).
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_access_set_password ~77

Gate a video behind a secret password. While protected, playback (including embeds) requires the password and Viddler swaps to a Mux signed-playback id. Returns the updated protection state.

NameTypeReqDescription
passwordstringyesThe secret password viewers must enter.
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_analytics_account_usage ~29

Return the authenticated account's plan, quota used/remaining, and video count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

viddler_analytics_get_views ~62

Return view counts and per-view records for a video: total views, remaining/available views, and the viewer log. The core 'who watched' proof-of-viewing data.

NameTypeReqDescription
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_feedback_submit ~125

File a feature request, bug report, or general feedback to the Viddler team from inside your MCP client. Goes into the same triage queue as the in-app feedback widget. Use category 'feature' for feature requests (the default intent), 'bug' for problems, 'general' otherwise.

NameTypeReqDescription
categorystringyesType of feedback. Use 'feature' for feature requests.
messagestringyesThe feedback text (1-2000 characters).
page_urlstring–Optional: the video or page URL this feedback is about.

No output schema declared.

No examples provided.

viddler_videos_create_upload ~161

Step 1 of uploading a video. Returns { uploadId, uploadUrl }. PUT the raw video file bytes to uploadUrl (e.g. `curl -X PUT --upload-file video.mp4 '<uploadUrl>'` — no auth header needed, the URL is pre-signed). Then call viddler_videos_register with the uploadId to create the video record. Files must be at most 1 GB (1073741824 bytes). Free videos must be at most 10 minutes. Requires a videos:write token.

NameTypeReqDescription
file_size_bytesinteger–Source file byte count for preflight validation. Send when known; omission supports older clients.
titlestring–Optional title to attach to the upload.

No output schema declared.

No examples provided.

viddler_videos_get ~62

Fetch the full record for one video: status, playback id, duration, moderation, storage state, protection. Poll this after create_upload until muxPlaybackId is no longer 'pending'.

NameTypeReqDescription
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_videos_list ~20

List videos owned by the authenticated account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

viddler_videos_register ~142

Step 2 of uploading a video: after the file has been PUT to the uploadUrl, call this with the uploadId to create the video record. Returns the video (muxPlaybackId will be 'pending'). Poll viddler_videos_get until muxPlaybackId resolves — processing usually takes under a minute. If title/description are omitted, AI generates them from the video content.

NameTypeReqDescription
custom_urlstring–Optional custom URL slug.
descriptionstring–Optional explicit description.
titlestring–Optional explicit title.
upload_idstringyesThe uploadId returned by viddler_videos_create_upload.

No output schema declared.

No examples provided.

viddler_videos_set_description ~40

Update a video's description.

NameTypeReqDescription
descriptionstringyesNew description.
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

viddler_videos_set_title ~40

Update a video's title.

NameTypeReqDescription
titlestringyesNew title.
video_idstringyesVideo id or uniqueId.

No output schema declared.

No examples provided.

Common questions

What is the Viddler MCP server?

Viddler is an MCP server listed in the public MCP registry as com.viddler/viddler-mcp. Official Viddler MCP: list videos, manage access control, pull proof-of-viewing analytics. This page covers its hosted endpoint (https://mcp.viddler.com/mcp).

Is the Viddler MCP server safe to use?

Viddler scores 74 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 Viddler MCP server expose?

Viddler exposes 12 tools: viddler_feedback_submit, viddler_access_set_password, viddler_access_remove_password, viddler_access_set_custom_url, viddler_analytics_get_views, and 7 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.

Does the Viddler MCP server require authentication?

No. We connected to Viddler without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Viddler MCP server still maintained?

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