VidFare

com.vidfare由 vidfare.com 发布官方发布者v1.0.0更新于 Nov 6, 2026

来自 VidFare 的只读 AI 视频价格、片段费用和优惠信息。

AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。

原文描述

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

已验证Streamable HTTP可网页运行

概览

VidFare 的托管 MCP 服务（mcp.vidfare.com），由 vidfare.com 发布；无需登录；Streamable HTTP；5 个工具。

暂无 AI 概览：以下信息来自注册中心条目和服务本身。

发布者
vidfare.com
端点
mcp.vidfare.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 VidFare，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.vidfare%2Fvidfare/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源：mcp-server/README.md，提交 f3260aa

工具

5

list_models

List models

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

无需输入参数。

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.

输入参数model必填providerresolution

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.

输入参数planusedaudioinputmodel必填seconds必填providerresolutionapply_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.

输入参数usedaudioinputseconds必填resolution必填apply_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.

输入参数status

版本历史

1
  1. v1.0.0最新Nov 6, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分