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.

VidFare

REMOTE · MCP.VIDFARE.COM

Read-only AI video prices, clip costs, and deals from VidFare.

Available components

+3 this week 72 Trust /100

Last scanned (22 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 929 tokens (~185/item across 5 items; 5 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • Stability: unverified → 0.03 ▲ 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 21 Nov 2026 · Probed https://mcp.vidfare.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vidfare.com CN=WE1,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 ECDSA 256 ECDSA-SHA256 4f545a24689b851a13614f97da249b9f
SANs: vidfare.com, mcp.vidfare.com, *.mcp.vidfare.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.vidfare.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
vidfare.com. No DS 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.vidfare.com/mcp Verified 200
http (plaintext) http://mcp.vidfare.com/mcp Inconclusive 406
MCP tools · 5 exposed · ~808 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
cheapest_options ~202

Cheapest stated VidFare price for a clip length and resolution, overall and per model. Rows the vendor does not state for that length or resolution are omitted.

NameTypeReqDescription
apply_dealsboolean–When true, apply today's credit-plan deals the way the calculator toggle does. Defaults to false.
audiostring–with or without audio. on and off are accepted. Omit to leave audio unset.
inputstring–Input mode: t2v, i2v, ref2v, v2v, extend, or lip-sync. Omit to leave input unset.
resolutionstringyesResolution such as 480p, 720p, 1080p, or 4K, or 'not listed'.
secondsintegeryesClip length in whole seconds, at least 1.
usedinteger–Percent of plan credits actually used, from 1 to 100. Defaults to 100.

No output schema declared.

No examples provided.

estimate_cost ~368

Cost of one clip from the VidFare calculator. Credit-plan rows use plan price ÷ credits × credits per clip, then the percent of credits used. API rows are billed seconds times the stated dollars per second. A length, resolution, audio value, or input the vendor page does not state is returned without a price.

NameTypeReqDescription
apply_dealsboolean–When true, apply today's credit-plan deals the way the calculator toggle does. Defaults to false.
audiostring–with or without audio. on and off are accepted. Omit to leave audio unset.
inputstring–Input mode: t2v, i2v, ref2v, v2v, extend, or lip-sync. Omit to leave input unset.
modelstringyesModel slug, such as wan-3-0 or kling-3-0, or the model name.
planstring–Credit-plan id, such as hf-starter. Optional.
providerstring–Platform name, such as fal, Higgsfield, Krea, or Magnific. A credit-plan platform selects that platform's first plan, the same way the calculator does.
resolutionstring–Resolution such as 480p, 720p, 1080p, or 4K. Use 'not listed' when the vendor page does not list one.
secondsintegeryesClip length in whole seconds, at least 1.
usedinteger–Percent of plan credits actually used, from 1 to 100. Defaults to 100.
window_secondsinteger–Seconds made during an unlimited window. Defaults to 60. Used only for the break-even note, which is not $0 per second.

No output schema declared.

No examples provided.

get_model_prices ~148

List current VidFare prices for one model. provider and resolution are optional filters. Prices the catalog does not contain are omitted rather than guessed.

NameTypeReqDescription
modelstringyesModel slug, such as wan-3-0 or kling-3-0, or the model name.
providerstring–Platform name, such as fal, Higgsfield, Krea, or Magnific. A credit-plan platform selects that platform's first plan, the same way the calculator does.
resolutionstring–Resolution such as 480p, 720p, 1080p, or 4K. Use 'not listed' when the vendor page does not list one.

No output schema declared.

No examples provided.

list_deals ~63

List VidFare deals copied from vendor pages and official accounts. status is live, upcoming, ended, or all. Defaults to live. An end date is included only when the source stated one.

NameTypeReqDescription
statusstring–Which deals to return. Defaults to live.

No output schema declared.

No examples provided.

list_models ~27

List the AI video models VidFare tracks, with the cheapest current dollars per second for each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the VidFare MCP server?

VidFare is a hosted endpoint at https://mcp.vidfare.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.vidfare.com

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

What is the VidFare MCP server?

VidFare is an MCP server listed in the public MCP registry as com.vidfare/vidfare. Read-only AI video prices, clip costs, and deals from VidFare. This page covers its hosted endpoint (https://mcp.vidfare.com/mcp).

Is the VidFare MCP server safe to use?

VidFare scores 72 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 VidFare MCP server expose?

VidFare exposes 5 tools: list_models, get_model_prices, estimate_cost, cheapest_options, list_deals. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.

Does the VidFare MCP server require authentication?

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

Is the VidFare MCP server still maintained?

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

What did VerifyMCP test on the VidFare MCP server?

VerifyMCP ran 12 checks on VidFare, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VidFare: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.