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.

PageToVid

REMOTE · PAGETOVID.COM

Turn any web page into a narrated video: films the real site, writes, voices and captions it

Available components

+3 this week 85 Trust /100

Last scanned (6 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Design and Media

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 Security97
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 14950 tokens (~182/item across 82 items; 82 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 83 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
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.

  • 5 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 4 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 3 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 1 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 31 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 30 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 29 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day 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 5 Nov 2026 · Probed https://pagetovid.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pagetovid.com CN=WR3,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 RSA 2048 SHA256-RSA ea665844bb4a2fca10297a2ba0f4f24d
SANs: pagetovid.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pagetovid.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pagetovid.com. 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 tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://pagetovid.com/.well-known/oauth-protected-resource/mcp", scope="videos:read videos:write videos:delete account:read", error="unauthorized"

Bearer resource_metadata="https://pagetovid.com/.well-known/oauth-protected-resource/mcp", scope="videos:read videos:write videos:delete account:read", error="unauthorized"
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://apis.google.com https://www.gstatic.com https://js.stripe.com https://*.js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; media-src 'self' data: blob: https:; connect-src 'self' blob: data: https://storage.googleapis.com https://*.storage.googleapis.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.google.com https://stats.g.doubleclick.net https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://www.googleapis.com https://apis.google.com https://*.firebaseapp.com https://fonts.googleapis.com https://fonts.gstatic.com https://api.stripe.com https://link.com https://*.link.com; frame-src 'self' https://*.firebaseapp.com https://accounts.google.com https://checkout.stripe.com https://js.stripe.com https://*.js.stripe.com http
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Document https://pagetovid.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://pagetovid.com/mcp
Authorisation server https://pagetovid.com

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pagetovid.com/mcp Verified 200
http (plaintext) http://pagetovid.com/mcp HTTPS enforced 302 https://pagetovid.com/mcp
MCP tools · 82 exposed · ~14,133 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
update_storyboard ~171

[Free] Edits a video's storyboard in 22 operations, each described on its branch: words, captions, visuals (incl. "rushie" designed cards: data.rushie {template, props}), data, shots, scenes, transitions, fx, presenter, voice, music, look. Does not re-render — rerender_video makes the new film. Every call is snapshotted, so an edit can be undone (list_revisions).

NameTypeReqDescription
operationsarrayyesThe changes, in order, up to 20; all are validated before any is written, so a bad batch changes nothing. A wrong figure is set_data plus one rerender_video, not a new video.
video_idstringyesThe video to edit. Its scene ids come from get_storyboard.
NameTypeReqDescription
appliedarrayyes–
createdarray––
editor_urlstringyes–
needs_rerenderbooleanyes–
notesarray––
revision_idstringyes–
scene_countnumberyes–
video_idstringyes–

No examples provided.

upload_asset ~206

[Free] Puts a file in your bank from a public https url or small data_base64 (a bigger file you hold: create_upload). Picture or clip → data.asset_id in an image scene; audio → music "asset:<id>"; deck (PDF/PPTX) → every slide's text and pictures, to write the storyboard from. Identical bytes return the existing asset.

NameTypeReqDescription
data_base64string–The file, base64, ≤ 2 MB.
filenamestring–Its file name.
kindstring–Required with url. image ≤ 20 MB, video ≤ 200 MB/60 s, audio ≤ 50 MB, font ≤ 2 MB, deck (PDF/PPTX) ≤ 30 MB.
namestring–A label to find it again.
site_urlstring–Attach an image or clip to one of your sites.
urlstring–Public https URL.
NameTypeReqDescription
assetobject––
deckobject––
deduplicatedboolean––
usestring––

No examples provided.

validate_format ~297

[Free] Compiles the template against a sample item, touching no database or feed: the catalogue checks (voice, music, language, theme…), the scene templates filled and checked as an animation, and what the first episode's title, brief and scene count would be. Returns problems by field; nothing is created, rendered or charged.

NameTypeReqDescription
aspect_ratiostring–As create_format.
brand_namestring–As create_format.
focus_templatestring–As create_format.
goalstring–As create_format.
introboolean–As create_format.
kindstring–video or animation.
languagestring–As create_format.
musicstring–As create_format.
namestring–The format's name, for {{show}}.
outroboolean–As create_format.
programmeobject–As create_format.
routingobject–As create_format.
scenesarray–animation formats: the scene templates, as create_animation's scenes (not from_library), with the placeholders in any string.
subtitlesboolean–As create_format.
target_secondsinteger–As create_format.
themeobject–As create_video.
title_templatestring–As create_format.
tonestring–As create_format.
voicestring–As create_format.
NameTypeReqDescription
problemsarrayyes–
sampleobjectyes–
validbooleanyes–

No examples provided.

validate_motion_spec ~112

[Free] Dry-run a spec: deterministic repairs, schema, params, layout/legibility/contrast/timing on four frames and the motion doctrine. Returns ok, every problem with its path and fix, the repaired spec and the params schema. Nothing is saved.

NameTypeReqDescription
paramsobject–Param values to check it with (default: the declared defaults).
site_urlstring–Lint against this site's brand colours.
specobjectyesA motion spec (get_motion_grammar).
NameTypeReqDescription
errorsnumberyes–
example_sceneobject––
okbooleanyes–
params_schemaarrayyes–
problemsarrayyes–
repaired_specobject––
repairsarrayyes–
warningsnumberyes–

No examples provided.

verify_episode ~137

[Free] The proof behind a film: the format version that made it (template SHA-256), every resolver source and what it fetched, the integrity report, the claim ledger (which figures trace to the page, the brief or nothing), the Content Credentials (C2PA), and a check recompiling the stored data against the narration word for word.

NameTypeReqDescription
episode_idstring–The episode to verify, from run_show or a show's recent_episodes.
video_idstring–Or a video id: the episode is found through it when there is one; a plain video is verified on its claim ledger and credentials.
NameTypeReqDescription
claimsobjectyes–
credentials–yes–
episode_idstring|nullyes–
format–yes–
page_urlstring|nullyes–
provenance–yessources (per id: kind, target, fetched_at, cached), calls[], report {ok, words, estimated_seconds, issues[]}, dropped[].
recompiled_matchesboolean|nullyes–
verdictstringyes–
video_idstring|nullyes–
video_statusstring|nullyes–

No examples provided.

Install

How do I install the PageToVid MCP server?

PageToVid is a hosted endpoint at https://pagetovid.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 · pagetovid.com

# add to Claude Code
claude mcp add --transport http com-pagetovid-pagetovid 'https://pagetovid.com/mcp'
Common questions

What is the PageToVid MCP server?

PageToVid is an MCP server listed in the public MCP registry as com.pagetovid/pagetovid. Turn any web page into a narrated video: films the real site, writes, voices and captions it. This page covers its hosted endpoint (https://pagetovid.com/mcp).

Is the PageToVid MCP server safe to use?

PageToVid scores 85 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 PageToVid MCP server expose?

PageToVid exposes 82 tools: create_video, create_animation, cancel_video, get_video, release_video, and 77 more. Their descriptions and schemas cost roughly 14,133 tokens of context every time the server is loaded.

Does the PageToVid MCP server require authentication?

Yes. PageToVid 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 PageToVid MCP server still maintained?

PageToVid 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.