VidFare

com.vidfarePublished by vidfare.comOfficial publisherv1.0.0Updated Nov 6, 2026

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

VerifiedStreamable HTTPWeb executable

Overview

VidFare's hosted MCP server (mcp.vidfare.com), published by vidfare.com; no sign-in required; Streamable HTTP; 5 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
vidfare.com
Endpoint
mcp.vidfare.com
Last checked

Installation

In SourceWeft

  1. Open VidFare in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.vidfare%2Fvidfare/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vidfare": {
      "type": "http",
      "url": "https://mcp.vidfare.com/mcp"
    }
  }
}

README

VidFare MCP server

Public, read-only Model Context Protocol server for the VidFare price catalog. It speaks Streamable HTTP at /mcp, with no authentication. A client such as ChatGPT, Claude, or Cursor can list models, read prices, estimate a clip, and list deals. Every result includes the VidFare source URL, the last-checked date, and a vidfare.com page link. Those vidfare.com links also carry utm_source=mcp&utm_medium=tool&utm_campaign=vidfare_mcp.

The Worker is live at https://mcp.vidfare.com/mcp. Do not run wrangler login or wrangler deploy from this repository.

Data

The Worker fetches only:

  • https://vidfare.com/data/prices.json
  • https://vidfare.com/deals.json (the same JSON is also published at /data/deals.json)

Responses are cached for 5 minutes. If a fetch fails, or the catalog does not state a price for the request, the tool says so and does not fill in a number.

Tools

ToolArguments
list_modelsnone
get_model_pricesmodel (required), provider, resolution
estimate_costmodel, seconds (required). Optional: resolution, audio (with, without, on, off), input (t2v, i2v, ref2v, v2v, extend, lip-sync), plan, provider, used (1–100, default 100), apply_deals (default false), window_seconds (default 60)
cheapest_optionsseconds, resolution (both required). Optional: audio, input, used, apply_deals
list_dealsstatus: live (default), upcoming, ended, or all

estimate_cost uses the same row filter as the credit calculator (scripts/variations.py) and the same plan math as the calculator script: plan price ÷ credits × credits per clip, divided again by the share of credits actually used. API rows are billed seconds times the stated dollars per second. scripts/test_mcp_parity.py checks that against the site code.

Usage counts

A tools/call writes one Workers Analytics Engine point: blob1 is the tool name (unknown if it is not one of the five tools), blob2 is success or error, and double1 is 1. The engine stores the time. The UTC day is that timestamp. The read script also prints when that UTC midnight falls in Pacific Time. Nothing else is stored: no arguments, prompt, IP address, user agent, session id, or country. There is no public stats URL.

Counts are tool requests, not unique people, visits, or sponsor impressions. A retry, a second call from the same person, and a client that does not send the test header each add one. Requests with X-VidFare-Test: 1, and POSTs to localhost or 127.0.0.1 (wrangler dev), are not written. initialize, tools/list, notifications, OPTIONS, and GET are not written. A crawler or someone else's test client that calls a tool is counted.

The write is not awaited and a failure is ignored, so a counter error does not change the tool response.

wrangler.jsonc binds USAGE to the dataset vidfare_mcp_usage. The dataset is created on the first write. Deploying that binding uses the existing Worker deploy token (Workers Scripts Edit or Workers Admin, Workers Routes Edit, and Zone Read). It does not need Analytics Read. Reading the counts does. Create a separate token with Account → Account Analytics → Read, scoped to the VidFare account, and run:

bash
CLOUDFLARE_ACCOUNT_ID=... CLOUDFLARE_API_TOKEN=... python3 scripts/mcp_usage.py

Do not put that token in the repo.

Local

bash
cd mcp-servernpm installnpm testnpx wrangler dev

wrangler dev stays on this machine. It does not deploy.

Cursor can use mcp-server/.mcp.json. Put the same JSON in a project's .cursor/mcp.json. The URL is https://mcp.vidfare.com/mcp.

Registry

server.json is the MCP Registry document. The name is com.vidfare/vidfare. The remote is streamable-http at https://mcp.vidfare.com/mcp.

Namespace verification for com.vidfare is HTTP. The site serves the published proof record at https://vidfare.com/.well-known/mcp-registry-auth. The file is one line, v=MCPv1; k=ed25519; p=<public key>. The private key is not in this repo.

The site build copies the file into dist/.well-known/ and writes dist/.nojekyll. actions/upload-pages-artifact leaves dot paths out unless include-hidden-files is true. Both deploy workflows set that, so the URL answers 200 with no redirect.

Deploy later

Token, one Cloudflare account (the account that owns vidfare.com) and one zone (vidfare.com only):

ScopePermissionWhy
Account, Workers productWorkers AdminThe first wrangler deploy creates the Worker. A token that can only edit an existing Worker cannot create this one. In the legacy token form this permission is still labeled Account → Workers Scripts → Edit; that legacy permission also creates scripts. If the new role picker is shown, choose Workers Admin on the Workers product, not Editor.
Zone vidfare.comWorkers Routes → EditAttaches the custom domain mcp.vidfare.com. Current docs call this Workers Routes Write.
Zone vidfare.comZone → ReadWrangler looks up the zone id for vidfare.com.

Do not add Workers KV, R2, Tail, Account Settings, DNS, or user membership permissions. The Worker has no bindings.

DNS record on vidfare.com, created in the dashboard (the token above does not edit DNS):

TypeNameContentProxy
AAAAmcp100::Proxied

That is the proxied hostname a Worker custom domain uses. wrangler.jsonc sets the route to custom domain mcp.vidfare.com. After the record exists, npx wrangler deploy from this directory publishes the Worker. It still needs CLOUDFLARE_API_TOKEN in the environment, not in the repo.

Source: mcp-server/README.md at commit f3260aa

Tools

5

list_models

List models

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

Takes no parameters.

get_model_prices

Get model prices

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

Parametersmodelrequiredproviderresolution

estimate_cost

Estimate clip cost

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.

Parametersplanusedaudioinputmodelrequiredsecondsrequiredproviderresolutionapply_dealswindow_seconds

cheapest_options

Cheapest options

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.

Parametersusedaudioinputsecondsrequiredresolutionrequiredapply_deals

list_deals

List deals

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.

Parametersstatus

Version history

1
  1. v1.0.0LatestNov 6, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts