# VidFare (remote · mcp.vidfare.com)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.vidfare.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-vidfare-vidfare/mcp.md), [page](https://verifymcp.io/servers/com-vidfare-vidfare/mcp)

## Channel facts

- Endpoint: `https://mcp.vidfare.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-vidfare-vidfare 'https://mcp.vidfare.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vidfare-vidfare": {
      "url": "https://mcp.vidfare.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vidfare-vidfare": {
      "type": "http",
      "url": "https://mcp.vidfare.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vidfare-vidfare]
url = "https://mcp.vidfare.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vidfare-vidfare": {
      "type": "remote",
      "url": "https://mcp.vidfare.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-vidfare-vidfare --url 'https://mcp.vidfare.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vidfare-vidfare:
    url: "https://mcp.vidfare.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vidfare-vidfare": {
      "Transport": "http",
      "Url": "https://mcp.vidfare.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vidfare-vidfare -t streamable-http -u 'https://mcp.vidfare.com/mcp'
```

### Other

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

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +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.

### 2026-11-18 (score 71, +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.

### 2026-11-16 (score 70, +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.

### 2026-11-13 (score 69, +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.

### 2026-11-11 (score 68, +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.

### 2026-11-09 (score 67, +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.

### 2026-11-07 (score 66, +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.

### 2026-11-06 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `list_models` (~27 tokens)

List models

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

### `get_model_prices` (~148 tokens)

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.

Input parameters:

- `model` (string, required): Model slug, such as wan-3-0 or kling-3-0, or the model name.
- `provider` (string): 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.
- `resolution` (string): Resolution such as 480p, 720p, 1080p, or 4K. Use 'not listed' when the vendor page does not list one.

### `estimate_cost` (~368 tokens)

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.

Input parameters:

- `apply_deals` (boolean): When true, apply today's credit-plan deals the way the calculator toggle does. Defaults to false.
- `audio` (string): with or without audio. on and off are accepted. Omit to leave audio unset.
- `input` (string): Input mode: t2v, i2v, ref2v, v2v, extend, or lip-sync. Omit to leave input unset.
- `model` (string, required): Model slug, such as wan-3-0 or kling-3-0, or the model name.
- `plan` (string): Credit-plan id, such as hf-starter. Optional.
- `provider` (string): 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.
- `resolution` (string): Resolution such as 480p, 720p, 1080p, or 4K. Use 'not listed' when the vendor page does not list one.
- `seconds` (integer, required): Clip length in whole seconds, at least 1.
- `used` (integer): Percent of plan credits actually used, from 1 to 100. Defaults to 100.
- `window_seconds` (integer): Seconds made during an unlimited window. Defaults to 60. Used only for the break-even note, which is not $0 per second.

### `cheapest_options` (~202 tokens)

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.

Input parameters:

- `apply_deals` (boolean): When true, apply today's credit-plan deals the way the calculator toggle does. Defaults to false.
- `audio` (string): with or without audio. on and off are accepted. Omit to leave audio unset.
- `input` (string): Input mode: t2v, i2v, ref2v, v2v, extend, or lip-sync. Omit to leave input unset.
- `resolution` (string, required): Resolution such as 480p, 720p, 1080p, or 4K, or 'not listed'.
- `seconds` (integer, required): Clip length in whole seconds, at least 1.
- `used` (integer): Percent of plan credits actually used, from 1 to 100. Defaults to 100.

### `list_deals` (~63 tokens)

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.

Input parameters:

- `status` (string): Which deals to return. Defaults to live.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-vidfare-vidfare/mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 69
- 2026-11-14: 69
- 2026-11-13: 69
- 2026-11-12: 68
- 2026-11-11: 68
- 2026-11-10: 67
- 2026-11-09: 67
- 2026-11-08: 66
- 2026-11-07: 66
- 2026-11-06: 65
- 2026-11-05: 65

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

## Links

- Remote endpoint: https://mcp.vidfare.com/mcp
- Repository: https://github.com/SheepinBoots/clipcost
- Website: https://vidfare.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-vidfare-vidfare/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vidfare-vidfare/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vidfare-vidfare/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-vidfare-vidfare/mcp
