# FPV-DB (remote · fpv-db.com)

Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff

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

## Components

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

## Channel facts

- Endpoint: `https://fpv-db.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 738 tokens (~147/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**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% 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 FPV-DB MCP server?

FPV-DB is a hosted endpoint at https://fpv-db.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-fpv-db-fpv-db 'https://fpv-db.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-fpv-db-fpv-db": {
      "type": "http",
      "url": "https://fpv-db.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-04 (score 72, +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-02 (score 71, +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-10-31 (score 70, +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-10-30 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 69)

First indexed and scored.

## MCP tools (5)

### `fw_param` (~133 tokens)

Betaflight / INAV CLI setting

One CLI setting of a firmware release: type, allowed range or values, firmware default (with no board config), the source line (settings.c or settings.yaml), and its history across releases (renames, range and default changes). Old names are followed through sourced renames.

Input parameters:

- `firmware` (string): Firmware (fw_check_cli: default is the one the paste's header names)
- `name` (string, required): Setting name, as in `set <name> = ...`
- `version` (string): Release, e.g. 2026.6.2 or 4.5 (default: latest)

### `fw_diff` (~93 tokens)

Betaflight / INAV settings diff

What changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings.

Input parameters:

- `firmware` (string): Firmware (fw_check_cli: default is the one the paste's header names)
- `from` (string, required): Older release, e.g. 4.5
- `to` (string): Newer release (default: latest)

### `fw_check_cli` (~175 tokens)

Check a Betaflight or INAV diff

Checks a pasted `diff all` / `dump` against a release: every `set` line whose setting does not exist, was renamed or removed, or whose value is out of range or not in the value list, plus lines that only repeat the firmware default. The release of the paste is read from its `# Betaflight / ... X.Y.Z` or `# INAV/<target> X.Y.Z` header, which also picks the firmware when none is given. Other commands (aux, serial, resource) are counted, not checked.

Input parameters:

- `firmware` (string): Firmware (fw_check_cli: default is the one the paste's header names)
- `text` (string, required): The CLI text, up to 100 KB
- `version` (string): Release to check against (default: latest)

### `part_specs` (~101 tokens)

FPV part spec sheet

The full spec sheet of one part by its slug (the last segment of its fpv-db.com URL, e.g. iflight-xing2-2207 for /motors/iflight-xing2-2207/): specs, bench thrust table where measured, VTX table where published, the sources the specs were verified against, and caveats.

Input parameters:

- `slug` (string, required)
- `type` (string): Part type, if known

### `search_parts` (~135 tokens)

Search FPV parts

Finds published parts of one type by spec. `filters` maps a spec field to a number (equals, or any element of a list), a string (case-insensitive substring) or {min, max} (numeric range). `query` matches brand and model. An unknown field returns the type's field list. Example: type=motor, filters={"stator": "2207", "weight_g": {"max": 33}}.

Input parameters:

- `filters` (object)
- `limit` (integer)
- `query` (string): Words that must appear in brand + model
- `type` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69

## Common questions

### What is the FPV-DB MCP server?

FPV-DB is an MCP server listed in the public MCP registry as com.fpv-db/fpv-db. Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff. This page covers its hosted endpoint (https://fpv-db.com/mcp).

### Is the FPV-DB MCP server safe to use?

FPV-DB 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 FPV-DB MCP server expose?

FPV-DB exposes 5 tools: fw_param, fw_diff, fw_check_cli, part_specs, search_parts. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.

### Does the FPV-DB MCP server require authentication?

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

### Is the FPV-DB MCP server still maintained?

FPV-DB 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.

## Links

- Remote endpoint: https://fpv-db.com/mcp
- Website: https://fpv-db.com/about/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-fpv-db-fpv-db/fpv-db.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fpv-db-fpv-db/fpv-db.json
- HTML version of this page: https://verifymcp.io/servers/com-fpv-db-fpv-db/fpv-db